Sandbox Integration
PayIn Cloud sandbox is the safe environment for merchant development, QA, demos, and integration testing.
Use sandbox before production so your team can verify API calls, hosted payment pages, blockchain monitoring, webhook delivery, and business-system updates without real funds.
What to test
A complete sandbox test should cover:
- Creating a payment order from your backend.
- Opening the hosted payment page or rendering payment instructions.
- Paying with a supported testnet asset or test flow.
- Receiving payment status updates.
- Verifying webhook signature handling.
- Updating your internal order, invoice, or account balance.
- Handling duplicate webhook delivery safely.
- Handling expired, underpaid, or failed payment scenarios.
Environment separation
Sandbox and production must be separate:
| Item | Sandbox | Production |
|---|---|---|
| API keys | Sandbox-only | Production-only |
| Webhook URL | Test endpoint | Production endpoint |
| Chain/network | Testnet or mock | Mainnet |
| Data | Disposable test data | Real merchant/customer data |
| Monitoring | Development visibility | Operational alerts |
Never point sandbox traffic at production databases, production webhook handlers, or production customer workflows unless you have explicitly designed a safe test path.
Sandbox success criteria
Before requesting production access, confirm:
- Test orders can be created reliably.
- Customers can understand the payment instructions.
- Payment status changes arrive in your system.
- Webhooks are verified and idempotent.
- Your support team can look up a payment and explain its status.
- Your engineering team knows how to inspect failed API or webhook events.