Skip to main content
Beta access for sandbox functionality is targeted for October 9, 2026.

​
What exists

Your sandbox program has core accounts, core balances, and core transactions you can list and retrieve the same way as in production:

​
How balances and transactions behave

Sandbox returns a static response for core balances and core transactions. The figures and entries you read are fixed sample data. New activity in sandbox does not reach the core objects. Simulated ACH, wires, instant payments, and internal transfers do not create core transactions and do not change any core balance. Use the sandbox core endpoints to test how your integration reads these objects, not to reconcile simulated payments.

​
What you can test

  • Requesting the core_account/read, core_balance/read, and core_transaction/read scopes and calling each endpoint with them.
  • Parsing every field on the three objects, including amounts, overdraft, and interest on a balance.
  • List filters and cursor pagination: type on accounts, core_account_id on balances, core_balance_id, type, and the created_at window on transactions.
  • Error handling.

​
What you cannot test

  • A balance changing in response to a simulated payment.
  • A core transaction appearing for a simulated payment, or joining a payment’s core transaction ID to a core transaction.
  • Status changes. Core accounts and balances stay active in sandbox, and there is no simulate endpoint to deactivate or close one.
Sandbox Environment · ACH Sandbox Testing · The Core Balance Object · The Core Transaction Object