To ensure your integration functions correctly for payouts across various methods—such as cards, bank accounts, and other payment options—simulate transactions in the staging environment using special values without moving real money. This allows you to validate your setup thoroughly.

We provide payout details for successful transactions (the "happy path"). Additionally, in supported countries and for eligible services, we offer specific details designed to simulate various validation failures, helping you test and handle different error scenarios.

How to use the test data

The data should be submitted to the Store Attributes Endpoint. Upon successful submission, the endpoint will return an attr_set_token. This token must then be passed to the Initiate Payout Endpoint. Depending on the credentials provided, the response will either indicate a successful transaction or return a validation error. These test details will only work on the staging environment. They will not be processed properly on the production environment.

Account Verification Service (AVS) test data is the exception: those account numbers are submitted directly to the Validate Bank Account Endpoint and do not require an attr_set_token. See AVS Details below.

Banking Details

Happy Path details:

Declined payout details:

Account Verification Service (AVS) Details

Submit these account numbers to the Validate Bank Account Endpoint to simulate each possible verification outcome. Each test account number is mapped to a fixed response, so you can exercise your match-handling logic end to end without triggering a real verification or incurring a fee.

Verification result details:

Testing the asynchronous flow

Account number 8880000004 is the test case for the asynchronous verification flow. Use it to confirm your integration correctly handles a verification that does not resolve inline.

The request returns 202 PROCESSING with no verification result in the body. The result is delivered separately to your avs.completed webhook, where it arrives as UNSUPPORTED. Because the account could not be verified, no fee is charged.

Two things to validate with this case:

1. Your integration treats 202 PROCESSING as a pending state and waits for the webhook, rather than reading the response body for a result or timing out.
2. Your reconciliation logic does not assume every verification request produces a billable event.

Configure your webhook listener in the staging environment before running this case, otherwise the result will have nowhere to be delivered.

As with all test data on this page, these account numbers only work on the staging environment. They will not be processed properly on the production environment.

Crypto Details

Happy Path details:

Declined payout details: