Skip to main content
The sandbox will let you run the full deposit flow end to end with no real funds - success, pending, failure, and expiry paths - so you build against Rheon before going live.
Coming soon. The design below is the intended shape - a plan, not a live spec. Test keys, the sandbox URL, and test values are documented here once the environment is built.

​
Testing against providers’ own sandboxes

Until the Rheon sandbox exists, card and bank flows run against the underlying providers’ test environments. Two limits are worth knowing before you interpret a result as a bug:
  • A card payment never reaches completed on the provider’s sandbox. It settles the card leg and then stops at processing, because no chain transfer is ever broadcast there. Purchases sit that way indefinitely. Use it to exercise the flow, not to assert a terminal state.
  • The card sandbox may settle a different asset than production. Read cryptoCurrency off the quote and the status rather than assuming USDC; a test environment that cannot settle USDC will hand you ETH with a correct amount.

​
How it will work

The sandbox will let you select each path by changing one value instead of reading config - a magic test value (e.g. an amount or a test wallet) that maps to a specific outcome. One canonical happy-path value covers most testing.
A test clock will let you fast-forward the expiry deadline so you can exercise the expiry / refund path without waiting.
Do not build pricing or calculation logic on sandbox responses - they are mock values.