Build against the sandbox
Every account gets test keys (test_sk_… for Payments, rach_sk_test_… for
CaaS). They hit the same API as live keys, but on testnets — no real funds move.
Create a checkout, open its hosted page, receive a webhook, and wire your
integration end to end.
What the sandbox covers, network by network, is in
Environments. Base, Arbitrum, Avalanche, Celo and XRP
have no testnet in the sandbox; their behaviour is identical to the networks
that do.
Book a guided demo
For a tour before you integrate, ask for a demo through Contact sales on rach.finance. A Rach team member walks you through a live, fully populated workspace:1
The dashboard
One overview across products — collections, balances in USDT, USDC and local
currency, and activity over time.
2
Taking a payment
A checkout created from the API, the hosted pay page with its network choice,
and a payment moving from detected to confirmed.
3
Getting paid out
Balances, settlement accounts and a withdrawal from start to finish.
4
Running it as a team
Roles and permissions — what an owner can do that a viewer cannot — API keys
and webhooks.
Then go live
When you are ready: complete verification in the dashboard, switch to yourlive_sk_ key, and point your webhook URL at production. Nothing else in your
integration changes.
