Bank payouts with a name check first, scheduled transfers, safe retries.
A payout to the wrong account is slow to recover and expensive to explain. A payout that times out and is sent again is worse: now you've paid twice.
Transfers checks the account holder's name before money moves, so your customer confirms who they're paying. Every transfer carries an idempotency key, so a retry after a timeout never sends the money twice. Scheduled and recurring transfers run on the date you set.
Name enquiry returns the account holder's name, so the sender can confirm before paying.
The pricing engine returns every fee and tax before money moves.
Each transfer carries an idempotency key; a retry with the same key returns the original result.
Paid, failed or reversed, as a signed webhook. A timeout is checked, never retried blind.
The account holder's name is returned before money moves.
A retry after a timeout returns the original result instead of sending again.
Pay on a date, or every week or month.
Every fee and tax quoted from your tariffs before the sender confirms.
A failed transfer's reversal posts automatically, with the reason.
Each state change arrives as a signed webhook.
Illustrative businesses, not customers. Figures are made up to show the flow.
An online fashion marketplace in Lagos · Marketplaces
Sellers want their money the same day. The ops team pays them from the bank's portal, one by one, and sometimes to the wrong account.
Sellers are paid daily, to the right account, without anyone typing account numbers.
A property management company in Abuja · Fintechs & neobanks
Landlords expect their rent share on the 1st, and staff forget or send late.
Landlords are paid on the day, every month.
An airline ticketing agent in Kano · Merchants & e-commerce
Refunds are sent from a script. When the bank times out, the script retries, and some customers are refunded twice.
Every customer is refunded once.
Endpoints in the Transfers API reference, with every parameter and response.
State changes arrive as signed webhooks. How webhooks work
POST /transfer
Bridgecurl -X POST "https://api.bridgemoni.com/transfer" \
-H "Authorization: Bearer $BRIDGEMONI_TOKEN" \
-H "X-Tenant: $BRIDGEMONI_TENANT" \
-H "X-Environment: $BRIDGEMONI_ENV" \
-H "Idempotency-Key: a-unique-key-per-intent" \
-H "Content-Type: application/json" \
-d '{
"sourceAccountNumber": "0123456789",
"instrumentReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"destinationAccountNumber": "0123456789",
"beneficiaryReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"organizationReference": "b3f1c2d4-5e6a-4b7c-8d9e-0f1a2b3c4d5e",
"receiverType": "ACCOUNT_NUMBER",
"receiverValue": "text",
"amount": 250000.0,
"saveBeneficiary": true,
"beneficiaryAlias": "Ada Obi",
"currencyCode": "NGN",
"narration": "March payroll",
"executionMode": "SYNCHRONOUS",
"schedule": {
"startDateTime": "2027-03-14T14:30:01",
"frequency": "HOURLY",
"endDateTime": "2027-03-14T14:30:01",
"maxOccurrences": 1
}
}'Not yet. Transfers go to bank accounts.
The transfer's outcome is checked. Retrying with the same idempotency key returns the original result; it never sends again.
It runs before the transfer; your app shows the name so the sender can confirm.
We'll come back with what's live for you today, and what's next.