Skip to main content
This page covers sandbox-specific testing details. If you haven’t set up your sandbox account yet, start with the Initial Setup.

​
Sandbox KYC & Bank Accounts

The sandbox environment accepts fake data for both KYC verification and bank account linking. You can submit any test identity information, documents, and bank details to complete the onboarding flow without providing real personal data.
Optional: Test with a real bank accountIf you want to verify that a real Mexican bank account can be correctly wired up with our SPEI provider, you can optionally link your real bank account in sandbox. No real funds will be moved or charged — all transactions in sandbox are simulated, even when using a real bank account. This is entirely optional — fake bank details work for standard testing.

​
Testnet Tokens

You’ll need testnet tokens to test offramps and swaps. Contact Etherfuse for information on obtaining testnet CETES, USDC, and other supported tokens on the relevant testnets.
Stellar: Trust lines for onramps are handled automaticallyWhen onramping to a Stellar wallet that doesn’t have a trustline (or doesn’t exist on-chain yet), Etherfuse handles the setup automatically. Pass walletAddress in your quote request — the quote fee will include a one-time onboarding cost. After the order completes, sign the stellarClaimTransaction from the order response to add the trustline and claim your tokens. See Testing Onramps for the full flow.For offramps and swaps, your wallet must still have trust lines established beforehand. Use GET /ramp/assets?blockchain=stellar to discover available assets and their identifiers in CODE:ISSUER format, then use the issuer address to create trust lines on your Stellar wallet.

​
Webhooks in Sandbox

Webhooks work the same in sandbox as in production. Make sure your webhook endpoint is publicly accessible (or use a tool like ngrok for local development) and register it via POST /ramp/webhook.