Identical contract
Sandbox and production share the same base paths, payloads and error envelope. Only the key prefix changes.
Developers
Test keys the same day you ask, pre-funded virtual pools and a way to force every edge case before a rupee is ever at risk.
Tell us your entity and use case. We provision a sandbox workspace with test keys the same day.
Sandbox pools are pre-funded with virtual rupees so you can exercise payout and verification flows freely.
Trigger success, rail failure, reversal, manual review or dispute states from the dashboard or API.
Complete onboarding checks, swap the key prefix and your integration runs unchanged in production.
Use these identifiers to force a specific outcome. They never touch a real rail and always return the same decision.
acc_test_successacc_test_reversalacc_test_mismatchAAAAA1111AAAAAA2222B4111 1111 1111 1111curl https://sandbox.rubixpe.in/v1/payouts \
-H "Authorization: Bearer sk_test_xxx" \
-H "Idempotency-Key: po_test_01" \
-d '{
"beneficiary": "acc_test_reversal",
"amount": 100000,
"rail": "IMPS"
}'
# → payout.created, then payout.reversed
# delivered to your webhook endpointTail sandbox webhooks on your laptop with rubix listen.
Sandbox and production share the same base paths, payloads and error envelope. Only the key prefix changes.
Load-test freely. Sandbox limits are deliberately generous so you can rehearse peak-day volumes.
Reserved test identifiers always resolve to the same result, which keeps your CI suite stable.
Tell us what you are building and we will provision test keys, a Postman collection and a shared channel with our integration engineers.