3DS Test Cards

You may use the following test card numbers with your sandbox account to test your integration.

You should only use your sandbox API Key to send requests using these test cards. Requests sent using your live API Key will be sent to live directory servers.

You should ensure you handle each of the different responses correctly. Some test cards require a challenge to be completed.

Luhn check validation

The Luhn check is a commonly used algorithm to check the card number appears to be valid. This is to help prevent keying errors but there is no guarantee it is a genuine card.

Types of test card

We have test cards for different purposes:

• If you are concerned about having cards which appear “real” in your test code for auditing purposes, use these test cards that fail the Luhn check.
• If you have your own Luhn check implemented in your client-side code, use these test cards that pass the Luhn check and therefore will be valid in your client app or website.
• If you would like to test the different types of challenges within our SDK, use these test cards.

See our 3DS Test Cards API for details of how to load our test cards from our API.

3DS 2 test cards (fails Luhn check)

These test cards can be used for both the browser flow and app flow authentications. The card numbers do NOT pass the Luhn check.

3DS 2 Test Cards (passes Luhn check)

These test cards can be used for both the browser flow and app flow authentications. The card numbers DO pass the Luhn check.

3DS 2 SDK Challenge Test Cards

These are test cards used to test SDK challenge methods during the app flow. The card numbers do NOT pass the Luhn check.

Feedback

Was this page helpful?

Thanks for the feedback. If you'd like to provide more detail, please email support@ravelin.com.