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: Add Trust Lines FirstOn Stellar testnet, your wallet must have trust lines established for any assets you want to ramp into (e.g., CETES, USDC) before tokens can be received. Use the GET /ramp/assets?blockchain=stellar endpoint to discover available assets and their identifiers in CODE:ISSUER format, then use the issuer address to create trust lines on your Stellar wallet.Without trust lines, onramp orders may complete on Etherfuse’s side but tokens won’t arrive in the 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.