Environments

Revenue Guard separates every organization’s data into two environments: sandbox and live. Payers, rules, orders, webhooks, and logs are all scoped to one environment, so test traffic never mixes with production data.

How the environment is chosen

The environment is decided by the credential, not by a request parameter.

• API callers — the API key is authoritative. A sandbox key reads and writes sandbox data; a live key reads and writes live data. There is no environment header, and there is no way for a key to reach the other environment.
• Dashboard users — a live/sandbox switcher at the top of the app sets the active environment for your session. Every page (Orders, Payers, Rules, API Keys, Webhooks, Logs) reflects the environment you have selected.

Key prefixes

Every API key is bound to a single environment when it is created, and its prefix tells you which one:

Confirming which environment processed a request

Responses that create or update environment-owned resources include two fields you can assert on:

• environment — sandbox or live.
• livemode — true only when the request used a live key.

For example, an order submitted with a sandbox key returns:

1
{
2
  "environment": "sandbox",
3
  "livemode": false
4
}

Recommended workflow