Transfers Sandbox Experience

Simulating transfer statuses in the sandbox

๐Ÿ“˜

Ensure you test transfers with verified customers (persons or businesses) and external accounts.

While in the sandbox environment, you can replicate some of the potential transfer failures that may occur in production. In this environment, transfer failures are simulated as returned ACH transfers, which means that the transfer will initially transition to a "completed" status before transitioning to a "failed" status. For a complete list of status reasons, you can refer to the here.

To simulate a transfer failure caused by a specific reason in either the source or destination account, you can pass an amount that ends in one of the examples provided in the table below. It is important to note that only the cents in the amount will impact the outcome, not the dollars. For instance, an amount of "101" would produce the same result as "10001".

Example amountResults in statusTransfer failure reason
"100""completed"N/A
"101""failed"Insufficient funds in the source account
"102""failed"Closed destination account
"103""failed"Insufficient funds in the source account and a closed destination account
"126""failed"ACH rejection on the source account
"127""failed"ACH rejection on the destination account
  • For direct debits and credits (payouts), transfers will cycle directly from "pending" to the status requested from the table above within ~5 minutes
  • For Deposits, Account-to-Account, Pay by Bank, or Disbursements use cases, transfers will mimic the settlement timeframe that your enterprise is configured for in production (e.g. 2 days)

๐Ÿ“˜

You will have to configure webhooks in order to receive the expected status update events.