Developers · Sandbox

Test before you
move money.

Every account has a test key pair. Authenticate with an sk_test_ key and you are in the sandbox — the same endpoints and payloads as production, with no real money moving.

Request · Sandbox
curl https://binkpay.net/api/v1/developer/ping \
  -H "Authorization: Bearer sk_test_51H..."
Response200 · livemode false
{
  "ok": true,
  "companyId": "co_4b7e21",
  "livemode": false,
  "scopes": ["analytics:read", "payments:read"]
}

A test key returns livemode: false. Display and copy only; no live request is sent.

Two keys, one surface

Sandbox and production, side by side.

The environments model — region and mode — is documented in Environments.

Sandbox
Authorization: Bearer sk_test_…

No real money moves. Accepts the documented test card and wallet numbers.

Production
Authorization: Bearer sk_live_…

Real balances and bank rails. Same endpoints, same payloads, same signatures.

No real money moves

Sandbox requests are made with a test key and never touch a real balance or bank rail.

The same surface

The same endpoints, payloads, error envelope and signatures as production — only the key differs.

Mode is the key

The key encodes region and mode. There is no separate base URL to switch when you go live.

The path

From test key to production.

  1. Create test credentials

    Every account carries a test key pair alongside its live one.

  2. Make a test request

    Call any endpoint with your sk_test_ key. Same URL, same payloads.

  3. Inspect the response

    A test key returns livemode: false — proof no real money was touched.

  4. Test webhook behaviour

    Point an endpoint at your server and verify the signed events you get.

  5. Move to production

    Swap the sk_test_ key for sk_live_. No base URL to change.

Developer portal

Continue the journey.

Sandbox

Build it safely first.

Everything you ship to production, tested first against a key that never moves real money.