Payouts & transfers
Pay anyone, checked first.
Single transfers with name enquiry and approvals, bulk payouts with a maker and a checker, payroll on a schedule, instant settlement to your account, and splits to every party on a payment.
Read the transfers API (opens docs site)POST /v1/transfers
Authorization: Bearer sk_test_…
Idempotency-Key: 5b1f0c9e-2a7d-4c43-9e1a-0d6f3b8a4c21
PediWave-Version: 2026-10-01
{
"amount": 2500000,
"currency": "NGN",
"destination": "rec_01J9ZQ1K4M",
"source": "balance",
"reason": "Supplier INV-77",
"reference": "TRF-10021"
}// 201 Created
{
"id": "tr_01J9ZQ4T7Y",
"object": "transfer",
"amount": 2500000,
"currency": "NGN",
"destination": "rec_01J9ZQ1K4M",
"status": "pending_approval",
"name_match": "exact",
"reference": "TRF-10021",
"livemode": false,
"created": "2026-10-10T09:14:02Z"
}POST https://acme.example/webhooks/pediwave
PediWave-Event-Type: transfer.paid
PediWave-Signature: t=1760087646,v1=5257a869e7…
{
"type": "transfer.paid",
"data": { "object": {
"id": "tr_01J9ZQ4T7Y",
"status": "paid",
"provider_reference": "NIP-58321",
"session_id": "000013…4821"
} }
}Single transfers
Pay one person, checked first.
Add a bank account and PediWave runs a name enquiry before you can send to it, so you see the account holder's name
and how well it matches. Send from your balance with a reference and a reason. Above your approval threshold, the
transfer waits for a second key. You get transfer.paid with the bank's session id when the money lands,
and if the bank fails after the debit, your balance is restored automatically.
Bulk payouts
Pay hundreds of people in one approval.
Upload a CSV or send JSON. PediWave validates every row before anything moves: names are enquired, missing or mismatched accounts are marked invalid, and you see them before you approve. The maker submits, a different person approves, and each item is dispatched on its own lane with its own outcome: settled, failed or returned. Returned money comes back to your balance.
Recurring payouts
Payroll that runs on the 25th, with a check on the 24th.
Schedule payroll, vendor runs or commissions once. The day before each run, PediWave tells you how much the run needs and whether your balance covers it, so you can top up in time. On the day, the run becomes a batch that waits for approval, then pays each item and reports what settled, failed or was returned. Pause, resume, skip the next run or end the schedule whenever you need to.
Standing orders from a customer's wallet, managed in your app. Coming soon
Read about recurring payouts (opens docs site)Your balance
Your money on T+1, or right now.
By default your balance settles to your verified bank account the next business day. When you need it sooner, request an instant payout and it goes out over NIP straight away; instant payouts are priced and limited. Or set a sweep: pay out everything above a threshold, or on a schedule, and always keep a minimum behind. Every settlement comes with a report you can download as CSV or JSON.
Choose per currency whether foreign receipts settle in kind or convert to naira. Coming soon
See instant payout pricingSplits
One payment, every party paid.
Define a split once as a profile, by percentage or fixed amount, and apply it by code to payments, payment links and subscriptions. Override a share on a single payment when you need to. At settlement each party's share lands in its own balance, and you choose who bears the fees. If the payment is refunded, each share is pulled back in proportion, unless you choose to carry the refund yourself.
Wallets and mobile money
Send to a bank or a wallet today. Mobile money is next.
A recipient can be a bank account, a wallet, or another PediWave merchant. Each is checked when you add it, so later transfers go straight out. Mobile money recipients and claimable payouts, for people who do not have an account yet and claim by link, are on the way.
- Bank account
- Wallet
- PediWave merchant
- Mobile moneyComing soon
- ClaimableComing soon
Where your money can go
Every destination is checked before the first transfer to it.
| Destination | Checked by | Sent over | Availability |
|---|---|---|---|
| Bank account in Nigeria (NUBAN) | Name enquiry when the recipient is added; a mismatch is refused | NIP | Available |
| Your own settlement account | Name enquiry when the account is added | NIP, on T+1, instantly on request, or by sweep | Available |
| Another PediWave merchant or sub-merchant | Must be active on PediWave | A transfer between PediWave balances | Available |
| Wallet | The wallet identifier | Wallet transfer | Available |
| Mobile money | Network and phone number | Mobile network operator | Coming |
| Claimable payout | Claimed by the recipient by link or USSD | Paid when claimed | Coming |
Refunds on rails with no return path, such as agent cash and, once it launches, USSD, are paid to a bank account you supply, using the same checks.
Built so a payout cannot go quietly wrong.
Never retried blind
If a bank does not answer, the transfer stays in transit while PediWave asks the bank for the outcome at set intervals. It is only sent again, on another route, once the first attempt is known to have failed in a way that is safe to retry. A timeout is never treated as a failure.
Approvals above your threshold
Set an approval threshold and any transfer above it, or any batch that needs approval, waits for a second key. The approver cannot be the person who created it, and every approval is recorded with who, when and from where.
Reversed automatically
When a rail fails after your balance was debited, the debit is reversed and your balance is restored. You receive transfer.failed with the reason, such as a closed account or an unavailable bank.
Questions about payouts
How fast does a bank transfer arrive?
Bank transfers go over NIP, Nigeria's instant interbank rail, and the receiving bank normally confirms within seconds. PediWave marks the transfer in_transit as soon as the rail accepts it and paid the moment the bank confirms, then sends you transfer.paid with the bank's session id. If a bank is slow to answer, PediWave keeps asking for the outcome rather than guessing.
What happens if the name does not match?
Every bank recipient is checked with a name enquiry when you add it, and you see the account holder's name and the strength of the match. A mismatch is refused. A weaker match can still be sent, but it waits for a second person to approve it.
Can I pay to mobile money?
Not yet. Today you can pay bank accounts, wallets and other PediWave merchants. Mobile money recipients and claimable payouts are coming, and the API already has a recipient type for them so your integration will not change. Talk to sales if mobile money is central to your plans.
How do approvals work?
You set an approval threshold. A transfer above it is created with the status pending_approval and waits until someone with a second key approves or rejects it, in the dashboard or through the API. Payout batches can require approval in the same way. The approver can never be the person who made the request.
When does my own balance reach my bank?
On T+1 by default: the next business day, to the bank account you verified. You can request an instant payout at any time, or set a sweep that pays out above a threshold or on a schedule. The fees for instant payouts are on the pricing page.
Related products
Start paying out.
A test key in five minutes. Live payouts after verification.