Check before you ask
- Your code reads
livemodeon responses and webhooks rather than assuming an environment. - Your webhook receiver verifies signatures on the raw body, deduplicates by the envelope
id, and acceptslivemode,environment_id, andreset_epochin the envelope. - Nothing on your live path calls
/v1/test_helpers/*. With a live key those endpoints answer404(not a sandbox environment). - API keys are never logged or sent to a browser.
Request live access
A workspace owner with an authenticator app on their account asks to go live from the dashboard: choose Go live in the Sandbox mode banner, add an optional note, and choose Request a call. Stridge gets in touch to set up live with you, then switches it on. See Going live in the dashboard guides for the steps.
Your sandbox stays as it is, beside the new live environment.
Switch to live
Once live is on:
Switch to live from the workspace menu at the top of the sidebar, then choose Developer → API Keys → Create API key. Only owners can create live keys, and a key that can move money asks for your authenticator code. The secret starts with sk_live_ and is shown once: store it before you close the dialog. See API keys.
Endpoints belong to one environment, so your sandbox endpoints do not receive live events. Add your live endpoint while in live, and store its own signing secret. See Subscribe to webhooks.
Routing policies and treasuries belong to each environment too. Create the ones you need in live; nothing is copied from the sandbox.
Keep the base URL, https://api.stridge.com, and send the live key in X-API-Key.
curl 'https://api.stridge.com/v1/uda' \
-H 'X-API-Key: sk_live_...'Once live, you can also use the gateway (Gateway Kit, Gateway SDK, and onramp), which takes a live gateway key only.
Keep using the sandbox after you go live: run your tests there, and try changes before they reach real money.