Test cards

Physical cards for terminal testing, and sandbox card numbers for every online scenario: approvals, declines, and 3D Secure.

Physical test cards for Card Present transactions

For in-person payment terminal testing, physical EMV and contactless test cards are essential for Card Present integration. These specialized cards contain real chips, magnetic stripes, and contactless antennas that simulate actual card behavior, allowing you to thoroughly test terminal workflows and payment scenarios before going live.

If you already have a set of B2 test cards for EMV and contactless testing, you are all set for Card Present testing. If you don't have physical test cards, please contact support@doura.ca to request a set of test cards.

Virtual test cards for Card Not Present transactions

The following test cards can be used for online payment testing (Card Not Present transactions) in the sandbox.

Every card below needs a CVV and an expiry date. Any valid value is accepted: use any 3-digit CVV (4 digits for American Express) and any future expiry date.

The issuer country is the two-letter ISO 3166-1 code of the card's issuing country. It matters when you test AVS behaviour or cross-border decline handling.

The Approved and Declined tables below are for non-3DS tests. Set formConfig.enable3DSecure: false explicitly when creating the session; omitting it can inherit a payment method default that enables 3DS. Include billingInfoCaptureLevel whenever you supply formConfig. See Form configuration. For authentication tests, use the 3D Secure test cards.

Approved

Declined

Use these cards to exercise your decline and error handling. The reason column identifies the intended test scenario; it does not prescribe an exact resultText or responseCode. Inspect the returned resultCode, resultText, and transactionResponses to handle the outcome. Processing errors can differ from issuer declines. See SDK error codes and Certification.

3D Secure test cards

These cards run through the 3D Secure authentication flow before the authorization. Use them with formConfig.enable3DSecure: true.

Selecting the 3D Secure scenario by cardholder name

With the 3D Secure cards above, the cardholder name entered on the Hosted Payment Form or Payment SDK selects the browser authentication scenario: frictionless, challenge, or error.

Selecting the 3D Secure scenario by amount

These cards select the authentication scenario from the transaction amount instead of the cardholder name.

Related

• Card not present
• 3D Secure
• SDK error codes - handling 3DS failures, hosted payment declines, and processing errors
• Errors and rate limits
• Certification