Sandbox
Transfers
Sandbox Experience
Simulating Transfer Statuses In Sandbox
Be sure to test transfers with
verified customers (persons or businesses) and external accounts.Simulating Successful Transfers in Sandbox
When you are simulating successful transfers in sandbox, the transfer statuses that you see will depend on whether you initiate a debit, a credit or an account-to-account transfer. In the case of a successful debit, the final transfer status will be"settled". In the case of a successful credit or account-to-account transfer, the final transfer status will be "completed". As displayed in the table below, in both cases, you will use an amount of "100" to simulate a successful transfer.
Exampleamount | Direction | Results instatus | Payment Rail | Transfer failure reason |
|---|---|---|---|---|
"100" | Debit | "settled" | ACH | N/A |
"100" | Credit or Account-to-Account transfer | "completed" | ACH or RTP | N/A |
Simulating Failed Transfers in Sandbox
Use the table below to simulate some of the potential transfer failures that may occur in Production. For ACH transfers the transfer will initially transition to a"completed" status before transitioning to a "settled" or "failed" status. For a complete list of status reasons, as well as a status workflow diagram, refer to Transfers
To simulate a transfer failure caused by a specific payment rail 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".
To simulate insufficient funds in your enterprise balance, you can initiate a transfer request for an amount greater than your available balance.
In an effort to make testing as easy as possible, all transfers in sandbox will cycle to the final state chosen above (completed, settled or failed) within ~5 minutes. This timeline is accelerated relative to the production experience.
Exampleamount | Results instatus | Payment Rail | Transfer failure reason |
|---|---|---|---|
"101" | "failed" | ACH | Insufficient funds in the source account |
"102" | "failed" | ACH | Closed destination account |
"103" | "failed" | ACH | Insufficient funds in the source account and a closed destination account |
"126" | "failed" | ACH | ACH rejection on the source account |
"127" | "failed" | ACH | ACH rejection on the destination account |
"151" | "failed" | RTP | RTP rejection |
Simulating NOCs in Sandbox
Use the table below to simulate an NOC (Notification of Change). An NOC is an alert used to notify the sender of an ACH payment to update details related to a customer’s bank account that have changed or are incorrect.Exampleamount | Payment Rail | NOC Experience |
|---|---|---|
"105" | ACH | An NOC will occur after the transfer status is "completed"(status will stay in "completed") |
"109" | ACH | An NOC will occur after the transfer status cycles from "completed"—> "failed"and a return occurs (status will stay in "failed") |
There will be no change in transfer status, as an NOC can exist on a transfer of any status and will not trigger the transfer to fail.
Configure webhooks in order to receive the expected status update events.