Sandbox

HIFI’s sandbox environment provides a safe testing space to integrate and test our APIs without real charges or affecting production systems. All transactions, tokens, and balances in the sandbox are simulated and hold no real-world value.

Getting started

Generate a sandbox API key

1. Request Access - Visit dashboard.hifibridge.com/request-access to schedule a call with our team and get onboarded.
2. Navigate to API Keys - Once approved, go to the Developer Dashboard
3. Create New Key - Click the “New API Key” button under Sandbox

Keep your sandbox API key secure and never commit it to version control. Use environment variables to store API keys in your applications.

Sandbox Base URL

All sandbox API requests should be made to:

https://sandbox.hifibridge.com/v2/

Example request:

curl -X GET "https://sandbox.hifibridge.com/v2/ping" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY"

---

Sandbox vs Production

The sandbox environment is designed to simulate production behavior while providing a safe testing environment:

Feature	Sandbox	Production
API Base URL	https://sandbox.hifibridge.com	https://production.hifibridge.com
Money Movement	Simulated	Real
KYC Processing	Typically auto-approved (may be blocked by compliance checks)	Manual review (1-3 business days)
Blockchain	Testnet	Mainnet
Tokens	No real value	Real cryptocurrency

Automated KYC Approval

In sandbox, the KYC process is streamlined for testing:

• Typically Auto-Approved - KYC submissions are usually approved within minutes
• Compliance Checks Still Apply - Some compliance checks (like PEP screening) may still block approval even in sandbox
• Dummy Data - Use any test personal information and documents

While KYC is typically auto-approved in sandbox, certain compliance checks may still block approval. For example, PEP (Politically Exposed Person) screening can prevent sandbox users from unlocking rails even in the test environment.

In production, KYC applications undergo real compliance review and typically take 1-3 business days to process.

Simulated Transactions

All money movement in sandbox is simulated:

• Virtual Deposits - Use an endpoint to mimic bank deposits
• Instant Processing - Transfers complete immediately for testing
• No Real Funds - No actual money or cryptocurrency moves
• Testnet Wallets - All wallet addresses are on blockchain testnets

---

Transitioning to production

When you’re ready to move from sandbox to production:

1. Generate production API keys in the dashboard
2. Update your base URL from sandbox.hifibridge.com to production.hifibridge.com
3. Update API keys in your environment variables
4. Remove simulation calls - Delete any simulate-deposit endpoint usage
5. Enable real KYC - Provide real user information and documents
6. Test thoroughly - Start with small transactions before scaling

Never use sandbox API keys in production or production keys in sandbox. They are environment-specific and won’t work cross-environment.

---

Getting help

If you encounter issues or have suggestions for improving the sandbox experience:

• 📧 Email: [e-mail]
• 💬 Slack: Message us in our shared Slack channel

The sandbox environment is continuously updated to reflect production changes. If you notice discrepancies between sandbox and production behavior, please let us know.