Adyen provides generic test card numbers, but you can also generate your own. On the Adyen test platform, you can use the generated test payment cards and request/response messages to simulate real-life traffic scenarios, and to verify the correct integration of your systems with Adyen's platform and services. Transactions carried out with these test cards do not result in actual credits/debits to live accounts.
Generated test cards should meet the following requirements:
- Test card numbers should be between 6-19 digits long.
- All test card numbers in a generated test card range need to have the same number of digits.
- The first six digits of the test card numbers in any generated range need to be valid BIN numbers.
- Test card numbers should comply with standard payment card number constraints. For example, to test a system with Visa you should create a test card range with a valid Visa BIN.
- Although the created test card start and end range numbers are not checked for Luhn compliance, if you carry out a test payment the test card is handled like a standard payment card. It undergoes the standard card checks that take place in live environments, including Luhn verification.
- The billing address details you define for a test card range need to be AVS (Address Verification Service) compliant, i.e. you always need to include at least the street address. Zip code is optional.
The billing address check verifies only the numeric characters in the street address and Zip code (if available).
Generating test cards
Adyen also offers an easy and simple way to add test cards:
- Sign in to the Customer Area and go to Account > Test Cards.
- Click Add New Range.
- Enter the necessary details in the Test Card Range form.
- Click Save.
Contact the Support Team to request access to use this. Send a request to the
/createTestCardRanges endpoint containing the information required to create a test card range.
/createTestCardRanges to generate one or more ranges of test cards.
Response with an error
If the operation does not complete successfully, a service exception is thrown. See Error handling for more details.