Skip to main content
The Partner API financial endpoints let you manage the full money lifecycle for your users: fund accounts, transfer between accounts, initiate payouts to external destinations, and retrieve transaction history — all from your own backend using your API credentials.

​
Base URL

​
Authentication

All financial endpoints require the user’s own QASH access token, obtained from Verify login code:
This is the same session token the QASH app itself uses. The token identifies both the user and your partner account — there is no userId field to pass and no X-Api-Key header on these calls. If you haven’t logged the user in yet, see the Partner Integration Guide.

​
Endpoints

​
Currency and amount format

QASH currently supports a single account currency: USDC, pegged 1:1 to USD. Amounts are decimal values, not smallest-unit integers — send 100 for USDC 100.00, not 10000000.
Never use floating point arithmetic to compute an amount before sending it — construct the decimal value directly and send it as a JSON number with at most the currency’s precision.
Payout and exchange endpoints may involve other fiat currencies (e.g. COP) on the receiving side — see Payout and Exchange rate quote for their specific amount conventions.

​
Account auto-provisioning

Every user gets a USDC account automatically the first time they log in — it’s a side effect of wallet provisioning, not something you request. There is no endpoint to create an account manually. Call GET /api/v1/user/accounts after login to retrieve the account id before depositing.

​
Common errors