Collections · for businesses

Get paid the way
your customers pay.

A permanent account number for bank transfers. Pay-ins by bank and mobile money. Payment links that open a hosted checkout page. You know the moment it lands.

Request
1POST /v1/payins
2Idempotency-Key: 2c9e-…-f4
3
4{
5 "currency": "NGN",
6 "amount": 2500000,
7 "method": "bank_transfer",
8 "customer": {
9 "name": "Ngozi Eze",
10 "email": "ngozi@example.com"
11 },
12 "merchantReference": "INV-0918",
13 "metadata": { "order": "7712" }
14}
Response
1202 Accepted
2
3{
4 "publicId": "pin_4t7e…",
5 "status": "pending",
6 "currency": "NGN",
7 "amount": "2500000",
8 "method": "bank_transfer",
9 "authorization": {
10 "mode": "virtual_account",
11 "bankName": "Wema Bank",
12 "accountNumber": "0123456789",
13 "accountName": "Acme Ltd"
14 },
15 "merchantReference": "INV-0918"
16}

Amounts in minor units.

What a collection goes through

Four words your customer sees. The same four your dashboard and your webhooks use.

  1. pending

    On request

    Your customer gets somewhere to pay: a dedicated account number or a hosted payment-link page. Nothing is credited yet.

  2. processing

    When they pay

    The bank confirms the funds. The collection stays processing until it does.

  3. successful

    It landed

    Your wallet is credited net of fee, the ledger entry balances, and your webhook fires — and says if they paid more or less than asked.

    → payin.successful · payin.overpaid · payin.underpaid

  4. failed

    Rarely

    The payer did not complete, or the window closed. Nothing is credited, and your webhook says which.

    → payin.failed · payin.expired

Why it arrives

Three mechanics make the promise true. All three are in the engine.

Route

One call, whichever way your customer pays.

Name the method in the request. A business gets one dedicated account, provisioned once and reused for every transfer. The engine picks the channel for that currency and method — never your code.

Price

The fee is a line, not a mystery.

Our fee posts as its own ledger line beside your credit. If a customer underpays, we charge nothing and return what arrived. If they overpay, we keep the amount you asked for, return the rest and charge only on what you keep.

Books

Every collection is a balanced entry.

Channel asset debited, your wallet and our fee credited — or the ledger refuses the entry. An overpaid or underpaid collection is named as such on the entry, on the dashboard and in the webhook.

Or share a link and write no code

Create a link once. Every payment through it is a normal collection: same statuses, same webhooks, same ledger entry.

Leave amount out and the customer names the sum. Set an expiry so old invoices stop taking money. Tolerances are in minor units; the example allows ₦100 over and nothing under.

Payment link
1POST /v1/payment-links
2
3{
4 "title": "Invoice 0918",
5 "description": "Sept retainer",
6 "amount": 2500000,
7 "currency": "NGN",
8 "expiresAt": "2026-09-30",
9 "redirectUrl": "https://acme.co/ty",
10 "allowedMethods": ["bank_transfer"],
11 "overpaymentTolerance": 10000,
12 "underpaymentTolerance": 0
13}
14
15→ customer pays at /{slug}/pay

As your finance team sees it

Every collection, what was asked, what arrived, what it cost — filter, export, drill to the ledger.

CollectionsBusiness dashboard
ReferencePayerMethodAskedReceivedFeeStatus
INV-2026-0918Ngozi Ezebank_transfer₦25,000.00₦25,000.00₦100.00successful
INV-2026-0917Kofi Mensahbank_transfer₵1,200.00₵1,200.00₵4.80successful
INV-2026-0916Wanjiku Kamaubank_transferKSh 8,000.00KSh 8,050.00KSh 32.00successful
INV-2026-0915Tunde Bellobank_transfer₦480,000.00——pending

INV-2026-0916 arrived KSh 50 over: it reads successful with the note overpaid, and the excess is returned to the payer.

The entry behind it

What the ledger records when a ₦25,000 collection settles.

INV-2026-0918 · settlementLedger entry
AccountDebitCredit
channel_settled_asset₦25,000.00
merchant_wallet₦24,900.00
revenue_fees₦100.00

Debits equal credits — or the ledger refuses the entry.

Account names are the real ledger families.

Also on the road

The rest of what ships with collections today.

  • Virtual accountsA dedicated account per business. Provisioned once after KYC, reused for every bank-transfer collection, and matched to your reference when the transfer lands.Live
  • Payment linksA URL you share. Title, amount (or leave it open), expiry and redirect. The customer pays on a hosted checkout page.Live
  • TolerancesSet how far a payment may miss the asked amount, in minor units. Outside the band, the difference is returned and the collection is named overpaid or underpaid.Live
  • IdempotencyIdempotency-Key is required on POST /v1/payins. Send the same key twice and you get the same collection back — never a second one.Always on

See where it works →

Your first collection is a sandbox call away.

No setup fee. Sandbox keys on signup. A balanced entry for every payment that lands.