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

EventTriggerPrimary use
ORDER_STATUS_UPDATEOrder changes statusTrack buy/sell conversion lifecycle
WITHDRAW_STATUS_UPDATEWithdraw changes statusTrack fiat and crypto payouts
DEPOSIT_DETECTEDDeposit credited to the userReflect the credited balance
USER_ONBOARDING_UPDATEOnboarding task changes statusDrive KYC/onboarding UX
SYNTHETIC_STATUS_UPDATESynthetic operation changes statusTrack Ramp-on/Ramp-off flows
SYSTEM_NOTICERecoverable operational incidentOperational monitoring and alerting
COMPLIANCE_NOTICEUser compliance data changedLimit 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:

  1. On receipt, check whether you have already processed this id + status combination.
  2. If yes, acknowledge the webhook (2xx) and discard.
  3. 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:

EndpointPurpose
GET /crypto/v2/syntheticsAll payment activities
GET /crypto/v2/ordersAll orders
GET /crypto/v2/depositsAll deposits
GET /crypto/v2/withdrawsAll withdrawals
GET /crypto/v2/stats/balance-snapshotsDaily balance at midnight GMT-3
GET /crypto/v2/stats/balance-activitiesFull debit/credit ledger
GET /crypto/v2/user-balances/USERANYIDReal-time user balance

The same lifecycle handling approach applies to Ramps operation lifecycle statuses and QR payment lifecycle.


Endpoint references


Did this page help you?