Use staging credentials and the staging base URL for integration testing. Do not test real user wallets, withdrawals, payouts, or production credentials until Rivo has approved your test plan.

​
Use sandbox first

Confirm test credentials with the Rivo team before running client-facing tests.

​
Test with preview endpoints

For value-moving flows, use preview endpoints first and low-value sandbox amounts.

​
Test virtual account webhooks

Register a webhook URL, then create virtual accounts on staging:
  • A normal reference such as ref_test_001 gives an account and a virtual-account.created webhook.
  • A reference containing reject, such as ref_reject_001, gives a virtual-account.rejected webhook.
Sandbox account numbers cannot receive real money. See Webhooks for payload examples.

​
Protect credentials

Never expose Rivo credentials, API keys, signatures, or authorization values in frontend logs, analytics tools, crash reports, or public support tickets.

​
Rotate safely

For production-like testing, create a second key before revoking the old one. Do not regenerate or revoke a key that is still deployed by your backend.
  • Use staging credentials.
  • Use low-value test amounts.
  • Confirm every user-facing money movement flow before sharing it with real users.
  • Log returned Rivo IDs so your support team can trace issues.