Home
Customer Care
BINK · Developers

Build financial products
on BINK.

The same regulated rail behind wallets, cards, payments and payouts, exposed as a REST API — with one error model, one idempotency contract and signed webhooks. Build against a sandbox, follow the documentation, ship.

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

The developer probe — the one endpoint that accepts an API key today. Display and copy only; no live request is sent.

Developer portal

Everything, one click away.

The reference, the tooling and the operational surfaces — each one a real route in the portal.

API Reference

REST resources and the request/response contract.

SDKs

Typed clients for the API.

Sandbox

Test keys and simulated events, isolated from production.

Webhooks

Signed event delivery, retries and replay.

Documentation

Guides, quickstarts and integration patterns.

API Status

Live system health.

Changelog

Release notes and breaking changes.

Base URL/api/v1
Start here

From zero to your first event.

  1. Get access

    Create sandbox keys to build against, with no production data at risk.

  2. Authenticate

    Send your key as a Bearer token. Every response carries a requestId.

  3. Make your first request

    Call the developer probe to confirm the key and see your environment.

  4. Handle events

    Verify the signature on each webhook and react — no polling required.

  5. Move to production

    Promote from test to live when your integration is ready.

The API

Predictable REST resources.

REST over HTTPS, JSON in and out, one prefix. Every resource shares the same request shape, the same error envelope and the same idempotency contract — learn it once.

Authentication

BINK authorises by session + API key. An sk_ key works on the developer probe today; the resource endpoints authorise by your dashboard session. Send the key as a Bearer token — full detail in Authentication.

PaymentsPOST

Create, list, retrieve and cancel payments.

Reference
PayoutsGET

Available balance and off-cycle payouts.

Reference
RefundsPOST

Issue and list refunds against paid payments.

Reference
CardsPOST

Issue, list, fund, freeze and control cards.

Reference
CustomersGET

Records derived from payment activity.

Reference
InvoicesPOST

Line-itemized bills for out-of-band payment.

Reference
WebhooksGET

Signed event delivery and the event catalog.

Reference
ErrorsGET

The shared error envelope and status codes.

Reference
Rate LimitsGET

Request limits, Idempotency-Key and 429s.

Reference
Built to integrate against

Behaviour you can rely on in production.

Not promises — the contract. These are engineering behaviours the API documents, so an integration behaves the same on the day you ship and every day after.

Signed webhooks

Every event signed with HMAC-SHA256 and a timestamp — verify it, no polling.

Idempotency

Pass Idempotency-Key on POST /merchant/payments to make retries safe.

Request IDs

Every response — success or error — carries a requestId to reference in support.

One error model

{ ok, statusCode, message } across validation, auth and server faults alike.

Rate limits

A 600 req/min default per-user ceiling, tighter on sensitive endpoints.

Authentication

Session + API key. An sk_ key works on the developer probe today.

WebhooksAPI status
Directory

Everything for developers.

API ReferenceREST resources and the request/response contract.SDKsTyped clients for the API.SandboxTest keys and simulated events, isolated from production.WebhooksSigned event delivery, retries and replay.DocumentationGuides, quickstarts and integration patterns.API StatusLive system health.ChangelogRelease notes and breaking changes.
Developers

Start building with BINK.

Read the reference, test against a sandbox, and put the same regulated rail under your own product.

Read the API ReferenceOpen the Sandbox