Test Mode

How test mode works

Test mode is determined by the key you use — there is no separate flag or environment to select. A request made with a _sandbox_ key runs in test mode. A request made with a _live_ key runs in live mode.

# Test mode
Authorization: Bearer sk_sandbox_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

# Live mode
Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Sandbox vs live keys

Both key types exist for both modes:

Mode	Secret key	Publishable key
Sandbox	`sk_sandbox_...`	`pk_sandbox_...`
Live	`sk_live_...`	`pk_live_...`

Find your keys under Developer → API keys in the dashboard, or go straight to dashboard.elasticpay.co/developers.

Test cards

Use test card numbers to simulate payment outcomes. See Test Cards for all accepted values.

For BECS direct debit testing, use BSB 062-000 with any account number.

Simulating time

Sandbox mode includes test clocks — fast-forward time for a set of test customers to watch payment plans renew, retries fire, and links expire in seconds instead of weeks.

Behavior in test mode

PSP calls are mocked — no real card processing occurs
Webhook events fire identically to live mode
API request and response shapes are identical
Data is isolated — test records are not visible in live mode

Moving to live

Replace all _sandbox_ keys with _live_ keys
Ensure your live account has been activated. There is no compliance settings screen — while the account is awaiting activation, the dashboard shows a Continue onboarding banner that opens the onboarding application, and that application shows the current review status. When the banner is gone, the account is active
Ask support to register your production webhook endpoint against the live account — sandbox subscriptions do not carry over

See Test vs Live for the full switchover checklist.