This guide takes you from zero to a working deposit in four steps. You’ll need your API key and API secret from the AssetPay dashboard before you start.
You can pass this token to your frontend. The client token is safe to expose to users because AssetPay protects your balance through callbacks, not through token restrictions. For withdrawals, we always check with your backend (via callback) before purchasing anything.
Your API key (ap_...) should stay on your backend. The client token is the one that can be used from the frontend.
The signature is delivered in the X-AssetPay-Signature header (not in the body) and is computed over <deliveryId>.<timestamp>.<rawBody> with HMAC-SHA256.Your callback handler should:
See Callbacks for the full verifyAssetPaySignature implementation.That’s it. You now have a working deposit flow. Head to the individual guides for full details on each part of the integration:
Authentication
Token generation, local signing, and security best practices.
Deposits
Single and multi-item deposits, instant credit, and hold periods.
Withdrawals
Market purchases and the withdrawal callback flow.
Callbacks
Signature verification, event handling, and retry behavior.