PayoutsLive

Save recipients once. Pay them again in one call.

Saved recipients with bulk import and validation.

Illustrative
Why it matters

What it changes for you.

The riskiest moment in a payout is typing an account number. Saving recipients means it only happens once, and that once can be checked.

Beneficiaries saves the people and businesses you pay, with the name confirmed when they're added. Bulk import validates every line before anything is saved, and identifiers are masked everywhere except the moment they were saved.

How it works

Step by step.

  1. Add a recipient

    Bank and account number, with the name confirmed by name enquiry.

  2. Or import a list

    A file of recipients, every line validated before anything is saved.

  3. Pay by reference

    Pay a saved beneficiary in one call, without sending the account number again.

  4. Keep it tidy

    Mark favourites, group recipients, and remove old ones.

What you can switch on

Built in, not bolted on.

Names confirmed

Each recipient's name is checked when they're added.

Bulk import

Every line validated; errors returned per line.

Masked identifiers

Account numbers are masked everywhere except the save that created them.

Cooling-off for new recipients

Newly added recipients can be held for a period before large payments.

Groups

Group recipients, such as suppliers or staff, for runs and reports.

Favourites

Pin the people paid most often.

  • Save recipients once, pay them again in one call
  • Bulk import with every line validated
  • Masked identifiers everywhere except where they were saved
Use cases

How businesses use it.

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

An agro-aggregator buying from farmers in Kaduna · NGOs & government

Paying farmers at harvest

Hundreds of farmers are paid at harvest. Account numbers arrive on paper, and errors mean farmers wait weeks.

  1. Field officers collect details into a spreadsheet
  2. The file is imported; every line is checked
  3. Errors are fixed before harvest day
  4. Farmers are paid by beneficiary reference

Harvest payments go out on the day, to the right people.

Illustrative

A supermarket chain in Ibadan · Merchants & e-commerce

Suppliers paid without retyping

Accounts payable retypes supplier details every week. Twice this year a supplier was paid to the wrong account.

  1. Suppliers are saved once, name-confirmed
  2. Weekly invoices are paid by beneficiary reference
  3. New suppliers wait out a cooling-off before large payments

Account numbers are typed once, and checked that once.

Illustrative

A security services company in Lagos · Payroll & HR platforms

Staff lists that stay current

Guards change often; payroll lists go stale and some pay goes to people who've left.

  1. Staff are grouped as a beneficiary group
  2. HR adds and removes people as they join and leave
  3. Each payroll run pays the current group

Pay goes only to people who still work there.

Illustrative
For developers

Save a beneficiary.

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

State changes arrive as signed webhooks. How webhooks work

POST /beneficiary

curl -X POST "https://api.bridgemoni.com/beneficiary" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "BRIDGE_USER",
    "alias": "Ada Obi",
    "favourite": true,
    "groupReferences": [
      "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e"
    ],
    "organizationReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
    "identifierType": "ACCOUNT_NUMBER",
    "identifier": "March payroll",
    "communityReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
    "accountNumber": "March payroll",
    "msisdn": "March payroll",
    "providerCode": "provider code",
    "providerName": "Ada Obi",
    "countryCode": "NG",
    "currencyCode": "NGN",
    "productCode": "Ada Obi",
    "customerIdentifier": "March payroll",
    "cardToken": "March payroll",
    "cardScheme": "Ada Obi",
    "cardLast4": "Ada Obi",
    "cardExpiryMonth": 1,
    "cardExpiryYear": 1,
    "cryptoAddress": "March payroll",
    "cryptoNetwork": "Ada Obi"
  }'

Questions about beneficiaries

Can we import recipients?

Yes. Every line is validated, and errors are returned line by line before anything is saved.

Why are account numbers masked?

So they can't be copied from lists. They're shown in full only on the save that created them.

What's a cooling-off period?

An optional wait after a recipient is added before large payments to them, which slows down fraud.

Bridge for Business

Tell us what you're building.

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