Skip to main content
EasyOnRamp runs separate sandbox and production environments. They do not share data, credentials, or configuration. Integrate against sandbox first, then go live with production credentials after KYB approval.

How environments work

Sandbox runs on testnet. Production runs on mainnet. That applies to card issuance and spend, and to treasury deposits (fiat in, USDC credited to your business wallet). Production-only features such as dual card branding are not available in sandbox. Never use a sandbox JWT against production, or the reverse. Each environment is a separate business account with its own keys and resources.

Base URL

All API paths in this documentation are relative to the environment base URL. Production:
Sandbox:
Example:

Credentials

During onboarding you receive credentials for each environment: Store sandbox and production credentials in separate secret stores.

What differs in practice

Sandbox:
  • Safe for automated tests and manual QA
  • KYB must be approved before sub-accounts, users, treasury, cards, or reports (same gate as production)
  • Cards and treasury deposits use testnet configuration
  • Treasury and card funding may use test balances - confirm limits with your EasyOnRamp contact
Production:
  • Business KYB must be approved before sub-accounts, users, treasury, cards, or reports
  • Cards and treasury deposits use mainnet
  • Real fiat deposits, USDC treasury, and card spend
  • Stricter verification and operational review on deposits

Webhooks

Register webhook subscriptions in each environment with the URL you want for that environment. Signing secrets are not shared across environments. See Webhooks.

Getting access

Contact support@easyonramp.com for sandbox credentials, KYB onboarding, and production go-live.