Sandbox & Testing
Exercise the full digital-banking lifecycle against synthetic data before you go live.
Synthetic data only
The sandbox never moves real funds or stores real customer data. All example values in this documentation are illustrative and safe to copy.
Test Credentials
| Header | Sandbox value |
|---|---|
X-Client-Id | your-sandbox-client-id |
X-Client-Secret | $CLIENT_SECRET (from your onboarding pack) |
partnerId | QWIKLIVE |
Scenario Coverage
| Scenario | Endpoints exercised |
|---|---|
| Onboarding | institutions (submit/get/update) · users (register/activate/update/get) |
| Open a digital asset account | digital-asset-accounts (create/get/update) |
| Issue a tokenized deposit | tokenized-deposits |
| Balance inquiry | accounts/balance-inquiry |
| Token redemption | token-redemptions |
| Interbank transfer | interbank-transfers/validate → interbank-transfers |
| Account validation | account-validations |
| Platform search | institution · accounts · transactions |
Testing Tips
- Send a unique
X-Correlation-Idper request so you can trace it end-to-end in logs and support tickets. - Assert on the returned resource state, not just the HTTP status.
- Validate your error handling against every code in Error Handling (400–500).