Sandbox Testing


Triggering specific scenarios and building mock vendors to end-to-end test can be time consuming. Synctera's sandbox provides a few tools to help speed up testing so you can build resilient, polished apps. We provide some capabilities described here to make sure that your sandbox experience is realistic and productive. Leveraging these tools enables integrators to run end-to-end tests against the Synctera sandbox environment.

Funding your Sandbox Accounts

There are a few options available to provide "fake funds" for your sandbox accounts.

  1. You can transfer funds via an account-to-account transfer from the "New Funding Account" internal account. This account exists in Sandbox for this purpose and so that you can also track your sandbox fund flows from this originating internal account. For example:
curl \
  -X POST \
  -H "Authorization: Bearer $apikey" \
  -H "Content-Type: application/json" \ \
  --data-binary '
      "amount": 1025,
      "currency": "USD",
      "originating_account_id": "35c1a55e-4510-458d-9345-fe08121b5654",
      "receiving_account_id": "c8ddc14b-33be-447a-820d-3fe59ad49028",
      "type": "ACCOUNT_TO_ACCOUNT"

(in this example, the originating_account_id is the account id of the New Funding Account, and the receiving account is the account which you want to fund)

  1. Funding through an externally linked account. If you link an external account in the Sandbox you can then do an ACH transfer from this account to the receiving account in the sandbox. This option requires a few more steps to get to funding but does test a more realistic customer facing flow to load funds into an account.


Our platform allows you to test various types of real world scenarios in the sandbox to help you see realistic patterns and activities before going live.

Simulating Risk Events

Testing positive and negative flows for risk is important. Triggers for specific flows such as KYC failure or a Watchlist can be found in the sandbox KYC test case document.

Simulating Card Transactions

You can trigger typical card activities in our platform. Triggers to simulate inbound transactions can be found in our simulations api reference.

Sandbox Wipe

Testing different scenarios and flows may require a periodic reset of your sandbox data. We offer this as a feature to make it easier to manage your sandbox environment.

Wiping Sandbox Data

Customer data can be reset using the sandbox wipe feature described below.

The following request will programmatically wipe sandbox:

curl \
  -X POST \ \
  -H "Authorization: Bearer $apikey"

The curl example mentioned above assumes that you have set up apikey environment variables. See Authentication for instructions. Currently, this only runs in sandbox and cannot run in PROD.

Data That Will Be Wiped

Sandbox wipe will delete customer data but keep configuration data.

The following resources will be wiped:

  • Accounts
  • Account applications
  • Account products (interest)
  • ACH
  • Businesses
  • Cards
  • Card images
  • Cases
  • Customers
  • Disclosures
  • External Accounts
  • Internal Accounts
  • Payment schedules and history
  • Persons
  • RDC
  • Relationships
  • Transactions (including for Internal Accounts)
  • Verifications
  • Waitlist
  • Webhook events

The following data will be retained

  • Account Templates
  • API Keys
  • Bank/Partner data
  • Card product
  • Disclosure document records
  • Groups
  • Roles
  • Users
  • Viral loop waitlist
  • Webhook registration and secrets