Triple-A Developer DocsTriple-A Developer Docs
Triple-A dashboard

Error codes

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

Triple-A APIs return standard HTTP status codes. Error responses are JSON with code, message, and status fields, so your code can branch on code and log message.

Authentication errors

These errors come from the token request and from requests that send a bad token. For how to get and cache a token, see Authentication.

StatusCodeMeaningWhat to do
400The token request failed because the client credentials could not be read.Check your Client ID and Client Secret.
401The access token is missing, invalid, or expired.Request a new token.
403no_permissionThe access token is invalid for this action. For payouts, the payout was already confirmed or cancelled.Request a new token, or check the payout status.
429The rate limit was exceeded, for example when a one-time token is reused.Slow down and retry.

Payment errors

The table below lists the errors a payment request can return. Use it when you create a payment with Make a payment request.

StatusCodeMeaningWhat to do
400existing_pending_transactionA pending transaction for this payment is already on the blockchain.Wait for it to confirm before you retry.
400payer_is_blockedThe payer is blocked.Don’t retry. Contact your Triple-A account manager.
409cannot_processThe payment has unfulfilled requirements, such as KYC.See Choose your solution.
409no_selectThe payer has not selected a digital currency.Send the customer back to the payment form.
422validation_errorThe request has invalid parameters.Check the parameters against the endpoint’s reference page.

Related content

These pages cover related topics.