Sandbox testing

Sandbox credentials, accounts, balances, corridors, and payouts are isolated from production and have no monetary value.

Run the workflow separately for every operating model you support. A funded partner sandbox account does not automatically contain a usable balance.

What to validate

• OAuth authentication and network allowlisting;
• partner and client resource separation;
• corridor discovery and destination requirement handling;
• Party Data Map storage and version selection, when used;
• field mapping, controlled-value normalization, destination validation, and supporting-document encoding through Payout Test;
• quote expiry, amount basis, and invalid-quote handling;
• prepared-payout review and confirmation reservation behavior;
• idempotent retries after timeouts or ambiguous responses;
• asynchronous success and unsuccessful outcomes;
• webhook signature verification and event de-duplication; and
• payout-to-account-statement reconciliation.

Recommended sequence

1. List the active funded account you will use.
2. Retrieve an available corridor and its detailed requirements.
3. Store the Party Data Map used by your integration, if applicable.
4. Run Payout Test and inspect normalized data, warnings, and field errors.
5. Request a quote and record expiresAt.
6. Create and review the final prepared payout.
7. Confirm it and verify that totalPayable is reserved.
8. Poll the payout while also processing signed webhook events.
9. Exercise the failure scenarios available in your sandbox.
10. Reconcile the settled debit to the funding account statement.

Never place real personal data, production documents, or real funds into the sandbox environment. Use the fixtures and scenarios issued for your partnership.

Payout Test is safe for repeated representative-data checks because it creates no quote or payout, reserves no balance, and does not persist the submitted payload. It is not a substitute for exercising the quote, confirmation, reservation, asynchronous status, and settlement workflow.

Before production, repeat all environment-specific setup with production credentials, allowlists, accounts, corridors, webhook endpoints, and controls.