Skip to main content
In staging, two calls make a deposit arrive in a virtual account and end the way you choose. No bank transfer is sent. From there the deposit follows the real path: one order, the same checks, statuses, fields, and webhooks, and the stablecoins delivered on the staging chain of the account. Both calls work in staging only. In production they answer 403 payments:virtual-account.staging-only and change nothing.

Prerequisites

  • Account: a virtual account in a staging project, opened as in Open a Virtual Account.
  • API Key: a staging server API key with the virtual-accounts.create scope. In staging, all scopes are included by default.

Simulate a Deposit

The call answers 202 at once:
Response
Follow the deposit through its webhooks, or read the order. The order carries the same simulationId, so concurrent tests can match each webhook to its simulation. Every check runs on the real state of the account, and outcome makes one check give the chosen result. A deposit into an account that is not active goes back with virtual-account-not-active, whatever the outcome.

Outcomes

Every outcome starts with orders.quote.created. The events column lists what follows. See Deposit States for the phase, payment.status, and payment.returnStatus of each end state.

End a Review

A deposit simulated with in-review stays in review until you end it. The call works on any deposit in review on the account.
Response

Errors

Next Steps

Track Deposits

The states, events, and fields of each deposit

Handle Virtual Account Webhooks

Every event and its payload