Private preview

Error handling Private preview

Handle errors that occur during onramp sessions.

For general error handling, see the Stripe error handling guide.

For error codes specific to the crypto onramp, see Crypto onramp error codes.

Web

React Native

Android

iOS

API errors

Transaction blocked errors

Transactions can be blocked to meet compliance or risk requirements. For compliance reasons, Stripe can’t provide additional details about why a specific transaction was blocked. If you believe a transaction was blocked incorrectly, contact Stripe.

Error code	Description	How to handle
`crypto_onramp_transaction_blocked`	The transaction was blocked to meet compliance or risk requirements.	Show a generic error message. If you believe the transaction was blocked incorrectly, contact Stripe.

Note

When testing, use the test values to avoid triggering compliance or risk checks.

Wallet ownership verification errors

The getWalletOwnershipChallenge and submitWalletOwnershipSignature EU Travel Rule wallet ownership methods resolve with an error whose stripeErrorCode is one of the following:

stripeErrorCode	Description	How to handle
`crypto_onramp_wallet_not_found`	The wallet isn’t registered on the authenticated user.	Register the wallet with `registerWalletAddress`, then request a new challenge.
`crypto_onramp_unsupported_network`	The network doesn’t support wallet ownership verification. It only supports EVM-compatible networks and Solana.	Don’t retry with this network.
`crypto_onramp_wallet_ownership_challenge_expired`	The challenge expired.	Request a new challenge, collect a new signature, then submit again.
`crypto_onramp_invalid_wallet_ownership_challenge`	The challenge is invalid or was already used.	Request a new challenge, then submit again.
`crypto_onramp_invalid_wallet_ownership_signature`	The signature doesn’t prove control of the wallet.	Restart the full challenge and signing flow. Don’t resubmit the same signature.