Environments

Every OAuth application belongs to exactly one environment: TEST or LIVE. There's no separate host or base URL for each — the same API endpoints serve both — isolation happens per-record: your application, every token it issues, and every payment it touches all carry an environment field.

TEST

• The default for a newly registered application. No business verification required, so you can start integrating the moment you sign up.
• Your business's TEST settlement wallet opens with a simulated balance, so you can exercise refunds and cancellations without first simulating enough captures to fund them.
• Money here isn't real. Use TEST for all development and integration testing.

LIVE

• Requesting environment: LIVE on an application that asks for payment scopes (payments:*) requires your business to have completed verification first. A TEST application can always be created regardless of verification status — only LIVE is gated.
• If your business isn't verified yet, registering a LIVE client with payment scopes returns a 403 telling you so; a TEST client can still be created in the same request.
• One client_id/client_secret pair per environment — if you need both, register two separate applications (one TEST, one LIVE).

Practical implications

• Keep your TEST and LIVE credentials in separate configuration — they are genuinely different applications, not a mode flag on one set of keys.
• A token issued to a TEST client can only touch TEST-environment data; it cannot see or move LIVE money, and vice versa.