Accounts & ledgerLive

One customer, several pockets, each with its own rules.

Nested wallets on one customer, each with its own limits.

Illustrative
Why it matters

What it changes for you.

Customers rarely want one undivided balance. They want money for rent that they won't touch, money for the children's school fees, money for the driver's fuel, capped each day.

Wallets lets you open several wallets on one customer, each with a purpose and its own limits: how much can leave per payment or per day, and the least or most it can hold. A wallet can be frozen so nothing leaves it. Moving money between a customer's own wallets is a ledger entry, with no fees you didn't set.

How it works

Step by step.

  1. Open wallets on a customer

    Name each one and give it a purpose. They all sit under the same customer and identity.

  2. Set the limits

    Per payment, per day, and the least or most the wallet can hold. Freeze it when nothing should leave.

  3. Move between them

    The customer moves money between their own wallets as a ledger entry, without fees you didn't set.

  4. Spend within the limits

    Payments that break a wallet's limits are refused before anything posts, with the reason.

What you can switch on

Built in, not bolted on.

Several wallets, one customer

No second sign-up, no second KYC: every wallet belongs to the customer you already know.

Limits per wallet

Daily and per-payment limits, and a floor or ceiling on the balance, set wallet by wallet.

Freeze and unfreeze

Freeze a wallet so nothing leaves it, and unfreeze it when the money is needed.

Moves without fees

Moving between a customer's own wallets is a ledger entry; you choose whether it carries a fee.

Refused before it posts

A payment that breaks a limit is stopped with a reason the customer can read.

One view of the money

The customer sees every wallet and the total, from the same ledger.

  • Several wallets per customer, each with a purpose
  • Limits per wallet: per payment, per day and on the balance, with freeze and unfreeze
  • Moves between a customer's own wallets without fees you didn't set
Use cases

How businesses use it.

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

A logistics company with 40 vans in Port Harcourt · Fintechs & neobanks

Fuel money for drivers

Drivers are given cash for fuel each morning and receipts don't add up. The company wants drivers to pay for fuel themselves, but only so much a day.

  1. Each driver gets a fuel wallet in the company's app
  2. The wallet can pay out up to ₦10,000 a day
  3. The company tops up all wallets each Monday
  4. Spending is visible per driver, per day

No more cash floats, and fuel spending the finance team can see line by line.

Illustrative

A savings-first money app in Lagos · Fintechs & neobanks

Saving for rent without temptation

Users say they save for rent and then dip into it. The app wants a rent wallet that's hard to raid but still the customer's own money.

  1. A rent wallet is opened and frozen until rent day
  2. Each payday the customer moves ₦40,000 into it
  3. They see it growing, but nothing can leave it while it's frozen
  4. On rent day they unfreeze it and pay the rent

Rent is ready on the day, and the money was the customer's all along.

Illustrative

A family app serving parents abroad · Fintechs & neobanks

School fees kept apart until they're due

Parents abroad keep school-fees money in the same balance they spend from, and by the start of term some of it has gone on other things. They want it kept apart until the school is paid.

  1. The parent opens a school-fees wallet and tops it up each month
  2. They freeze it between terms so nothing leaves it
  3. When fees fall due, they unfreeze it and pay the school's account
  4. The payment and the receipt sit against that wallet

Money meant for fees is still there when the fees are due.

Illustrative
What it won't do

Honest limits.

  • A wallet is not a bank account number: add Virtual accounts for that.
For developers

Open a wallet.

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

State changes arrive as signed webhooks. How webhooks work

POST /wallet

curl -X POST "https://api.bridgemoni.com/wallet" \
  -H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
  -H "X-Tenant: $BRIDGEMONI_TENANT" \
  -H "X-Environment: $BRIDGEMONI_ENV" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Ada Obi",
    "description": "March payroll",
    "walletType": "main",
    "currencyCode": "NGN"
  }'

Questions about wallets

Is a wallet a separate account number?

No. Wallets are pockets inside a customer's money on Bridge. Add Virtual accounts if a wallet needs its own number to receive transfers.

Can a wallet be frozen?

Yes. Nothing can leave a frozen wallet until it's unfrozen, and the money stays in it.

What happens when a payment breaks a limit?

It's refused before anything posts, and the reason is returned so your app can show it.

Bridge for Business

Tell us what you're building.

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