Bridge
Contact us
CollectionsLive

Get paid on every rail, from one integration.

Bank transfer to account numbers, wallet, agent cash and offline devices, with split settlement and refunds.

Talk to us about collectionsAPI reference →
Illustrative
Why it matters

What it changes for you.

Your customers pay in different ways: a transfer from a bank app, a wallet balance, cash at an agent, a tap with no network. Each one usually means its own provider, its own contract and its own reconciliation.

Collections puts them behind one request. You ask to be paid; Bridge works out which rails can take it, tells the payer how to pay, and confirms when it happened. Matching, splitting between parties, refunds and disputes work the same whichever rail was used.

Every rail is described by how long the payer can take the money back. Transfers, wallets, cash and offline taps are push payments: once they land, they stay. That's why they need no reserve.

How it works

Step by step.

  1. Create a collection request

    An amount, a reference and the rails you accept. Bridge checks which rails can take it for this payer and amount.

  2. The payer is told how to pay

    An account number, a wallet prompt or an agent reference, whichever they pick.

  3. Bridge confirms it happened

    By the bank's notice, the wallet posting, the agent's confirmation or a signed offline payment.

  4. Matched, split and settled

    Matched to the request, split between the parties you named, and settled to each.

  5. Refunds and disputes

    Refund in part or in full, on the same request, whichever rail paid it.

What you can switch on

Built in, not bolted on.

Many rails, one request

Bank transfer, wallet, agent cash and offline taps, behind one object. QR and USSD aren't rails yet.

Split settlement

Name the parties and their shares; each is settled their part when the money arrives.

Refunds on any rail

Partial or full, recorded against the original request.

Escrow-backed collection

Send the money straight into an escrow agreement when the buyer and seller need protection.

Agent cash

Customers pay cash at an agent with a reference; the agent's confirmation completes the request.

Fees from your tariff

The pricing engine quotes fees per rail, from your own tariffs, before the payer pays.

  • Collect by bank transfer to account numbers, wallet, agent cash and offline devices
  • Split settlement between parties you name
  • Refunds, disputes and reserves
  • Escrow-backed collection for marketplaces
Use cases

How businesses use it.

Illustrative businesses, not customers. Figures are made up to show the flow.

A food delivery platform in Lagos · Marketplaces

Splitting every order at the source

The platform collects from customers, then pays restaurants and riders by hand every Friday. Restaurants complain about waiting a week, and finance spends Thursday on a spreadsheet.

  1. Each order is one collection request with three parties
  2. The customer pays by transfer or wallet
  3. On confirmation, the restaurant, rider and platform shares are split
  4. Each party is settled to their own account

Restaurants and riders are paid per order, and Friday's spreadsheet is gone.

Illustrative

An electricity prepaid vendor serving estates in Benin City · Merchants & e-commerce

Cash customers, without a cashier

Many customers pay in cash. The vendor's office collects it, which means queues, cash in transit and errors in the count.

  1. Customers get a payment reference for their meter
  2. They pay cash at a nearby agent, quoting the reference
  3. The agent confirms in their app; the request completes
  4. The token is issued and sent by SMS

Cash customers pay near home, and the vendor never handles the cash.

Illustrative

A traders' association in Aba · Cooperatives & groups

Dues from every member, however they pay

Members pay monthly dues by transfer, in cash at meetings, or not at all. The treasurer keeps a notebook, and nobody trusts it.

  1. Each member gets a monthly dues request
  2. They pay by transfer, wallet or cash at an agent
  3. Payments match to the member and the month
  4. The treasurer sees who has paid, live

One list everyone can trust, whichever way members paid.

Illustrative
What it won't do

Honest limits.

  • Hosted checkout and payment links are not offered yet.
  • QR and USSD aren't collection rails yet.
  • Card and mobile-money acceptance need a connected processor (see Card acceptance).
Bridge Payments

Accept every rail at checkout with Bridge Payments

See Bridge Payments
Who uses it

Built into these products.

Marketplaces

Collect, hold and split, so buyers and sellers both trust you.

Marketplaces

Lenders & BNPL

Score, lend and collect on one ledger.

Lenders & BNPL

Cooperatives & groups

Group money with signatures, dues and payouts.

Cooperatives & groups
For developers

Create a collection request.

Endpoints in the Collections API reference, with every parameter and response.

State changes arrive as signed webhooks. How webhooks work

POST /collection/request

curl -X POST "https://api.bridgemoni.com/collection/request" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV" \
  -H "Content-Type: application/json" \
  -d '{
  "form": "string",
  "collectorOwnReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
  "currencyCode": "string",
  "countryCode": "string",
  "amountMode": "string",
  "amount": "string",
  "minAmount": "string",
  "maxAmount": "string",
  "requestDescription": "string",
  "usageMode": "string",
  "payerBinding": "string",
  "boundPayerReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
  "underpaymentPolicy": "string",
  "overpaymentPolicy": "string",
  "allowedRails": [
    "string"
  ],
  "returnUrl": "string",
  "expiresAt": "string",
  "metadata": "string",
  "splits": [
    {
      "recipientCollectorReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
      "splitType": "string",
      "splitRole": "string",
      "percentage": "string",
      "fixedAmount": "string",
      "narrative": "string"
    }
  ]
}'

Questions about collections

Which rails are live?

Bank transfer to account numbers, wallet, agent cash and offline payments. QR and USSD aren't rails yet. Card and mobile-money acceptance need a connected processor; direct debit too.

Is there a hosted checkout page?

Not yet. Collections is an API: you show the payer how to pay in your own app or site.

How do refunds work?

Against the original request, in part or in full. The refund is recorded with the collection it belongs to.

Do push rails need a reserve?

No. Transfers, wallets, cash and offline taps can't be pulled back by the payer once they land.

Related capabilities

Virtual accounts

Live

Dedicated account numbers per customer or per invoice, credited as transfers land.

Direct debit

Partner required

Mandates and scheduled pulls. Moves money once a processor is connected.

Card acceptance

Partner required

Card and mobile-money acceptance. Moves money once a processor is connected.

Bridge for Business

Tell us what you're building.

We'll come back with what's live for you today, and what's next.

Talk to usRead the docs