Environments

Test and live modes, and how sandbox access works.

Modes

Every programme spans two modes, test and live, as a single identity — the same programme, not two separate ones. Every API client belongs to one mode, and every token it mints is locked to that mode: an endpoint that requires live mode rejects a test-mode token with 403, and vice versa. Client secrets, cards, cardholders and transactions are likewise scoped to the mode they were created in.

Sandbox

Test mode is a full simulation surface, not a set of canned fixtures. Driving POST /v1/simulated-spends against a card you've issued runs the real authorization pipeline end to end — the same decisioning, the same ledger movements, and the same webhook deliveries a live transaction would produce. See the Quickstart for a complete walkthrough from API client to a settled test-mode transaction.

Getting access

Access to sandbox and live environments is provisioned per design partner — request access at rigid.fi/demo.