Skip to main content
SeerBit accounts operate in one of two modes. Which mode a request runs in is determined entirely by which API keys you send — the base URL is the same for both. Because the base URL does not change, swapping keys is what takes you live. There is no separate sandbox host to point at. Both key pairs live in the dashboard under Settings > API Keys. New accounts start in test mode, so you can build a full integration before submitting business documents; live keys appear once your business is approved.

​
Test cards

Use the expiry, CVC and PIN exactly as shown — these cards are only valid with the values above.

​
Test bank accounts

Test credentials for bank account and transfer payments are issued per merchant account. Request yours from your SeerBit account team or via support.

​
Test mobile money

Test MSISDNs for mobile money differ by operator and country. Request the set for your markets from your SeerBit account team or via support.

​
Confirming which mode a transaction ran in

The payment status response includes a mode field:
It reads test for simulated transactions and live for real ones. Check it if you are ever unsure which key pair a call used — most commonly when a payment appears to succeed but never shows up in your live dashboard.

​
What carries over, and what doesn’t

  • Transactions do not carry over. A payment made with test keys never appears in your live transaction history.
  • Webhook subscriptions do not carry over. Configure your notification URL separately in each mode — a test-mode subscription will not fire for live traffic.
  • Webhooks do fire in test mode, so you can verify your handler end to end before going live.

​
Next steps

Quickstart

Take a test payment end to end with one of the cards above.

Go live

KYC, swapping keys, and the final production check.