Test Scenarios

Important Tips

• Ensure the transactions have a unique transaction reference. This reference must not contain personal information such as Names / Card identification / Number Plates / expiry dates or card numbers.

• The testing will be relevant to direct integrations to dna Payments and when using CMS Plugins.

Standard Sales

• Your integrated solution should handle a standard sale. The transaction should authorise, and the result clearly displayed.

• Your integrated solution should handle a standard sale The transaction should decline, and the result clearly displayed.

• Your integrated solution should handle the result of a Voice Referral. This transaction should decline, and the result clearly displayed.

• Your integrated solution should handle a declined transaction. This transaction should decline, and the result clearly displayed. The cardholder should be given the option to retry and redirect after three failed attempts.

Payer Authentication (3DSecure2)

• Your integrated solution should handle a transaction which results in a 3DS2 challenge. Th cardholder should be prompted to authenticate via a One Time Passcode (OTP). This should authorise and have the PA result as C/Y.

• Your integrated solution should handle a transaction which results in a 3DS2 challenge. Th cardholder should be prompted to authenticate via a One Time Passcode (OTP). This should decline and display the PA result as C/N.

• Your integrated solution should handle a PA response of N/-.

• Your integrated solution should handle a PA response of Y/A.

Recurring Transactions

• Your integrated solution can process a successful Customer Initiated transaction (CIT).

• Your integrated solution can process a successful Merchant Initiated transaction (MIT).

MOTO transactions

• Your integrated solution can process a MOTO transaction. The entry mode should be passed as a Telephone order or a Mail order. The integrated solution should correctly interpret the CSC result as a minimum according to the acceptance criteria. This should authorise.

• Your integrated solution can process a MOTO transaction. The entry mode should be passed a Telephone order or a Mail order. The integrated solution should correctly interpret the CSC result as a minimum according to the acceptance criteria. This should decline.

Charitable Donation (Pennies)

• Your integrated solution can correctly process a transaction where Charitable donation has been made. The donation amount should be separated from the Sale and referenced as a Charitable donation.

Refunds

• Your integrated solution can handle and correctly process a refund. The transactionType should equal to ‘REFUND’. The refund should be linked to a transaction ID and authorise.

Tokenization/ Verification

• Your integrated solution can correctly tokenise a card. The transactionType should equal to ‘TOKENIZATION’.

• Your integrated solution can correctly process a successful verification and tokenisation. The transactionType should equal to ‘VERIFICATION’.

Token Wallet/ Stored Cards

• Your integrated solution allows the cardholder to choose from a stored card form the Token Wallet and correctly process a transaction. This must authorise.

Pre-Authorisation

• Your integrated solution can correctly process an authorisation only. The transactionType should equal to ‘AUTH’.

• Your integrated solution can correctly process a successful Pre-Authorisation. The transactionType should equal to ‘PRE-AUTH’.

• Your integrated solution can correctly process a Settlement only. This should authorise.

Summary

This testing is not mandatory. However, we strongly recommend you complete the testing to ensure you future proof your integration and can be comfortable when you begin taking live payments.