Skip to main content
KemyCard provides two completely separate environments, controlled by your API key prefix.

Comparison

How it works

When you use a sk_test_ key, the API:
  1. Validates your request — required fields, email format, country code, etc. You get the same validation errors as in live mode.
  2. Returns simulated data — realistic fake responses with generated UUIDs, consistent fields, and proper structure.
  3. Does NOT touch the database — no customers, cards, or transactions are created.
  4. Does NOT call external providers — no identity verification call, no card issuance, no wallet creation.
Test mode is perfect for building and testing your integration. When you’re ready, simply switch to your sk_live_ key — the API contract is identical.

Identifying the mode

Every response includes a meta.mode field:

Test mode responses by endpoint

Customers

Fees in test mode are your live fees. Every fee returned in test mode (card creation, load, top-up and withdrawal, Ops deposits, wallet deposits and withdrawals, payouts, virtual accounts) is computed with the fees of your current plan, exactly like in live mode. Only the demo balances and amounts are fixed.

Cards

KYC, Balance, Wallets, Gift Cards

Virtual Accounts

No account is opened and no money moves in test mode.

Payouts

Limitations

  • UUIDs are generated on the fly and are not persistent
  • No uniqueness check on external_reference
  • Webhooks are not triggered in test mode
  • Simulated data is static — it does not reflect previous API calls