Three calls. One coffee.

# Base URL (test and live keys share it)
https://api.bitripay.com/v1

# 1. Create an intent
curl -X POST https://api.bitripay.com/v1/payment_intents \
  -H "Authorization: Bearer sk_test_…" -H "Idempotency-Key: order-1042" -H "Content-Type: application/json" \
  -d '{"amount_minor":250000,"currency":"CDF","description":"Order 1042","allowed_operators":["orange_cd","mpesa_cd","airtel_cd","africell_cd"]}'

# 2. Send the customer to checkout_url (or render qr_payload), then
# 3. Verify the webhook: BitriPay-Signature (HMAC of the endpoint secret) and the platform Ed25519 key from /v1/keys

Endpoints you will use first

Every operation, every schema and every error code: OpenAPI 3.1 document · platform signing keys · operating status.

Scopes

A restricted key holds only the scopes you choose; a scope that is missing returns scope_denied.

Drop-in checkout: pay by mobile money, automatically

Add “Pay with BitriPay” to any website or marketplace. The customer picks the operator, pays to the collection number, and BitriPay matches the operator's confirmation; the order moves forward on its own. Two integration paths:

Platforms and aggregators: onboard your customers by API

Marketplaces, SaaS, billing systems, cooperatives, schools, institutions: create each customer's merchant account with one call, take their payments with your own key, keep your fee, and hand the account over when they are ready. BitriPay holds the aggregator licence and remains the regulated party; each customer is the merchant of record with its own wallets, settlement profile, statements and verification.

# 1. Create the customer's account (they get a claim link to own it)
curl -X POST https://api.bitripay.com/v1/accounts -H "Authorization: Bearer sk_live_…" -H "Content-Type: application/json"   -d '{"business_name":"Pharmacie Lumière","type":"merchant","email":"owner@pharmacie.example","country":"CD","application_fee_bps":150}'
# → {"id":"acct_…","status":"active","kyb_status":"none","onboarding":{"claimed":false}, …}

# 2. Take a payment for that customer with YOUR key: add the account header (works on every operation)
curl -X POST https://api.bitripay.com/v1/payment_intents -H "Authorization: Bearer sk_live_…" -H "BitriPay-Account: acct_…"   -H "Idempotency-Key: inv-88" -H "Content-Type: application/json"   -d '{"amount_minor":250000,"currency":"CDF","description":"Invoice 88","application_fee_minor":3750}'

# 3. Their events reach your webhooks with "account":"acct_…"; send them a claim link when they should sign in themselves
curl -X POST https://api.bitripay.com/v1/accounts/acct_…/account_links -H "Authorization: Bearer sk_live_…"

Install BitriPay for your clients

BitriPay holds the aggregator licence; you integrate it into your clients' websites, apps, billing and institutional systems. Each client is the merchant of record: their money settles to their own account, their statements are theirs, and you never hold their funds or their password.

Sandbox magic numbers

With a test key, these MSISDNs drive an intent through the real attempt machine so you can test every outcome without an operator.

Everything else in the catalogue