Execution Tracking
CaaS operations are asynchronous by design. Order execution, withdraw processing, and deposit confirmation all complete outside the request/response cycle.
Persist operation IDs at creation time, consume webhooks idempotently, and periodically reconcile with GET endpoints.
Webhook event catalog
| Event | Trigger | Primary use |
|---|---|---|
ORDER_STATUS_UPDATE | Order changes status | Track buy/sell conversion lifecycle |
WITHDRAW_STATUS_UPDATE | Withdraw changes status | Track fiat and crypto payouts |
DEPOSIT_DETECTED | Deposit credited to the user | Reflect the credited balance |
USER_ONBOARDING_UPDATE | Onboarding task changes status | Drive KYC/onboarding UX |
SYNTHETIC_STATUS_UPDATE | Synthetic operation changes status | Track Ramp-on/Ramp-off flows |
SYSTEM_NOTICE | Recoverable operational incident | Operational monitoring and alerting |
COMPLIANCE_NOTICE | User compliance data changed | Limit recalculation, PEP status changes |
See Webhooks for delivery configuration, signature verification, and the full retry schedule.
Recommended tracking strategy
Primary: webhooks
Webhooks are the most efficient tracking mechanism. Configure your endpoint once and receive push notifications on every status change. Design your handler to be idempotent: the same event may be delivered more than once due to retries.
Idempotent processing
Every CaaS operation includes a stable id (internal) and optionally an externalId (your reference). Use these to deduplicate webhook deliveries:
- On receipt, check whether you have already processed this
id+statuscombination. - If yes, acknowledge the webhook (
2xx) and discard. - If no, apply the state transition and then acknowledge.
Processing the same event twice must not change the final state. Store the last-seen status per operation ID.
Reconciliation
For periodic reconciliation outside the webhook stream:
| Endpoint | Purpose |
|---|---|
GET /crypto/v2/synthetics | All payment activities |
GET /crypto/v2/orders | All orders |
GET /crypto/v2/deposits | All deposits |
GET /crypto/v2/withdraws | All withdrawals |
GET /crypto/v2/stats/balance-snapshots | Daily balance at midnight GMT-3 |
GET /crypto/v2/stats/balance-activities | Full debit/credit ledger |
GET /crypto/v2/user-balances/USERANYID | Real-time user balance |
The same lifecycle handling approach applies to Ramps operation lifecycle statuses and QR payment lifecycle.
Endpoint references
| Action | Endpoint |
|---|---|
| Get synthetic list | GET /crypto/v2/synthetics |
| Get synthetic by ID | GET /crypto/v2/synthetics/{syntheticAnyId} |
| Get order by ID | GET /crypto/v2/orders/{orderAnyId} |
| Get deposit by ID | GET /crypto/v2/deposits/{depositAnyId} |
| Get withdraw by ID | GET /crypto/v2/withdraws/{withdrawAnyId} |
Updated 27 days ago