Test cards API

To communicate with the Adyen API you should submit HTTP POST requests to corresponding endpoints. These endpoints differ for test and live accounts, and also depend on the data format (SOAP, JSON, or FORM) you use to submit data to the Adyen payments platform.

This document lists all endpoints available for you to integrate with the test platform and run QA checks.

Endpoints

SOAP

For the SOAP messaging protocol, all test payment requests must be posted to the following endpoint:

The data schema for corresponding SOAP objects is available at:

JSON and FORM

This is an overview of the test URL endpoints to communicate with our API using JSON or FORM (key-value parameters passed in an Http POST URL).

After you are ready to go live, you should switch to either generic or custom live endpoints. For more information, refer to Live endpoints.

AvsAddress

 

Field Type Required Description
streetAddress  String (tick)

Billing address of the card holder.

Example: 1 Infinite Loop, Cupertino

zip  String (error)

Zip code associated to the billing address of the card holder.

Example: CA 95014

CreateTestCardRangesRequest

 

Field Type Required Description
accountCode String (tick) The merchant account details used to log in and access the account.
accountTypeCode String (tick)

The type of account used to make the call.

Possible values:

  • Company
  • MerchantAccount

These values are case-sensitive.

testCardRanges Array of TestCardRange (tick) Contains one or more test card range objects.

CreateTestCardRangesResult

Field Type Required Description
rangeCreationResults Array of TestCardRangeCreationResult (tick)

Contains one or more test card range result outputs.

ExpiryDate

Expiry date on the card.

Field Type Required Description
expiryMonth  String (tick)

Expiry month for the test card range.

Allowed values: 

  • JANUARY
  • FEBRUARY
  • MARCH
  • APRIL
  • MAY
  • JUNE
  • JULY
  • AUGUST
  • SEPTEMBER
  • OCTOBER
  • NOVEMBER
  • DECEMBER
expiryYear  String  (tick)

Expiry year for the test card range.

Example: 2020

TestCardRange

Defines the properties of a test card range. 

Field Type Required Description
address AvsAddress (tick) Contains the billing address of the card holder. The address details need to be AVS (Address Verification Service) compliant, i.e. you need to define at least streetAddress.
cardHolderName String (tick)

The name of the card holder, as it appears on the card, for the test card range.

Example: S Hopper

cvc String (tick)

The test card range security code.

Example: 123

expiryDates Array of ExpiryDate (tick) An array of expiry dates on the card.
rangeEnd String (tick)

The last test card number in the test card range: 

  • Min 6, max 19 digits
  • BIN compliant

Example: 5432 1234 1234 4321

rangeStart String (tick)

 The first test card number in the test card range:

  • Min 6, max 19 digits
  • BIN compliant

Example: 5432 1234 1234 1234

threeDUserName String (error)

3D Secure user name details of the card holder.

Example: simonhopper

threeDPassword String (error)

3D Secure password details of the card holder.

Example: myPa$$w0rd

threeDDirectoryServerResponse String (error)

3D Secure server response. It notifies whether the specified card holder is enrolled in a 3D Secure service. Possible values:

  • Y (Authentication available)
  • N (Card holder not enrolled/not participating)
  • U (Unable to authenticate)

TestCardRangeCreationResult

Contains a test card range result output.

Field Type Required Description
 cardNumberRangeStart  String (tick)

The first test card number in the generated test card range.

Example: 5432 1234 1234 1234

 cardNumberRangeEnd  String (tick)

The last test card number in the generated test card range.

Example: 5432 1234 1234 4321

 creationResultCode  String (tick)

Notification message. It informs about the outcome of the operation. Possible values:

  • CREATED
  • ALREADY_EXISTS
  • ERROR