Getting a sandbox key
Generate one in the dashboard on the Sandbox tab of your merchant. It looks like this:sk_sandbox_ is routed to the
sandbox. Everything else stays the same — same host, same paths, same request
and response shapes:
What works in the sandbox
Anything that moves or reports real money is refused outright rather than
answered with misleading empty data.
Simulating a payment
A live invoice’s status is decided by the chain. In the sandbox you decide it:Parameters
Amount paid, in the invoice’s
fiat_currency. Defaults to the full amount for
success, half for partially_paid and 125% for paid_over.Override the webhook destination for this call only — handy for pointing at a
local tunnel while you develop.
Sandbox webhooks
Sandbox webhooks are byte-for-byte the same as live ones, with two additions that let you assert you are not in production:- the payload carries
"sandbox": true - the request carries an
X-Paw-Sandbox: trueheader
X-Paw-Signature header is computed with your sandbox key, so a
receiver that verifies against the live key will correctly reject a sandbox
webhook. Verify exactly as you do in production, using whichever key the
environment is configured with — see Webhooks.
Deliveries are logged and readable through GET /api/v2/notifications with your
sandbox key, and on the Sandbox tab in the dashboard.
Going live
- Verify your domain and finish onboarding.
- Generate a live API key in the dashboard.
- Swap
sk_sandbox_…for the live key in your configuration.

