Test scenarios

Test your integration.

This page is for classic Adyen for Platforms integrations. If you are just starting your implementation, refer to our new integration guide instead.

Adyen for Platforms provides you with a set of predefined test scenarios to test your integration. To test the scenarios, you need to create certain account holder states. This page explain how to:

Create account holders in the states you need.
Use the predefined test scenarios.

Create an account holder in the payout state

Select the account holder type to see the relevant examples below:

Make a POST /createAccountHolder request to create an account holder. In your request, specify:
- address.city: PASSED
- bankAccountDetails.ownerCity: PASSED for all banks accounts. At least one bank account must be defined.
- bankAccountDetails.ownerName: TestData
- individualDetails.name.lastName: TestData
- legalEntity: Individual
Upload a photo ID on a Hosted Onboarding Page (HOP) or through an API request.
- Hosted Onboarding Page
  - Upload a document with a PASSED file name. For example, PASSED.jpg.
- API
  - Make a POST /uploadDocument request to upload a passport. In your request, specify:
    - documentContent: A Base64-encoded image larger than 1000 bytes.
    - documentType: PASSPORT
    - description: PASSED
  When uploading photo ID, the account holder is set to the limitless state. This means the account holder requires the highest level of KYC checks.
Upload a bank statement on a Hosted Onboarding Page (HOP) or through an API request.
- Hosted Onboarding Page
  - Upload a document with a PASSED file name. For example, PASSED.pdf.
- API
  - Make another POST /uploadDocument request to upload a bank statement:
The individual account holder now has its identity, document and bank statement verified.

An account holder with one of KYC checks set to FAILED

Select the account holder type to see the relevant examples below:

Make a POST /createAccountHolder request to create an account holder. In your request, specify:

address.city: FRAUD
bankAccountDetails.ownerCity: FRAUD for all banks accounts. At least one bank account must be defined.
bankAccountDetails.ownerName: TestData
individualDetails.name.lastName: TestData
legalEntity: Individual

Here is an example of creating a suspended Individual legal entity account holder with its payouts blocked:

An account holder with one of KYC checks set to INVALID_DATA

Set address.city to INVALIDDATA.
Set bankAccount.ownerCity to INVALIDDATA for all banks accounts, which should be marked as Failed.
Set description to INVALIDDATA for a passport, if you need its KYC check to be marked as Failed.

An account holder with a PASSPORT_VERIFICATION KYC check set to INVALID_DATA

You can do this on a Hosted Onboarding Page (HOP) or through an API request.

Hosted Onboarding Page
- Upload a document with INVALIDDATA in the file name. For example, INVALIDDATA.jpg.
API
- Make a POST /uploadDocument request with:
  - documentContent: A Base64-encoded image larger than 1000 bytes.
  - documentType: PASSPORT
  - description: INVALIDDATA

Inactivate an account holder and schedule a refund

Set address.city to INACTIVEDEADLINECITY.

The /refundNotPaidOutTransfers call is scheduled to be performed in 6 weeks.

Inactivate an account holder and make a refund

Set address.city to REFUNDDEADLINECITY.

In this case the /refundNotPaidOutTransfers call is performed immediately.