Sandbox Testing

Triggering specific scenarios and building mock vendors to end to end test can be time consuming. Synctera sandbox provides a few tools to help speed up testing so you can build resilient, polished apps.

  1. Triggers for specific flows such as KYC failure or a Watchlist can be found in the sandbox KYC test case document.
  2. Triggers to simulate inbound transactions can be found in our simulations api reference.
  3. Customer data can be reset using the sandbox wipe feature described below.

Leveraging these three tools enables integrators to run end to end tests against the Synctera sandbox environment.
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