About PediWave
Payments that keep working.
PediWave is one API to collect, pay out and be settled on every rail your customers use, online or offline, with the best provider chosen for each payment.
Why we exist
One provider's bad day becomes yours.
A business that wants to be paid online today usually chooses one payment provider, and inherits its outages, its decline rates, its settlement calendar and its API.
If it wants a second provider for resilience, it builds the switch-over itself, under pressure, in the week the first one goes down. If its customers are offline, in a market, on a bus, or caught in month-end USSD failures, it takes cash or loses the sale. If it runs a platform with sellers, it stitches identity checks, sub-accounts and splits together from three vendors.
Nothing on the market combined local rails such as Verve, bank transfer, USSD and mobile money with a developer experience built for engineers, routing across several providers, and a way to be paid when the network is gone.
PediWave combines them, in one API. Bank transfer, QR, wallets, vouchers and offline taps come first; cards, USSD and mobile money are coming.
What we built
A gateway, an orchestrator and an offline edge, over one ledger.
Most providers sell one of these layers. PediWave is all three, and every payment through any of them settles on the same ledger.
The gateway Cards coming
Keys, one payment object, hosted Checkout, Payment Links and invoices, refunds and disputes, settlement, payouts, splits and billing, with a card vault for when cards arrive. This is what any good payment provider sells, and we treat it as the minimum.
Accept paymentsThe orchestrator
Connections to several acquirers and banks, with mobile money operators coming, and rules, scoring and a cascade that retries only when it is safe. This is where a merchant gains resilience when one provider has a bad day.
OrchestrationThe offline edge
Enrolled terminals with hardware keys, signed acceptance policies, taps signed by both devices and settled later, exposure limits and a loss policy chosen in advance. It works because the ledger holds the payer's offline balance and checks hardware-bound signatures at settlement.
Offline paymentsWhat we believe
Three rules for moving other people's money.
Every rail is first-class.
A customer paying from a feature phone deserves the same certainty as one paying from a banking app. Bank transfer, QR, wallet, voucher and offline tap use one payment object, one status machine and one event feed, and card, USSD, mobile money and agent cash join the same object as they arrive.
In practice: one payment_intent, one next_action, whatever the rail.
Offline is part of the product.
When the network goes, the sale should not. Offline acceptance is bounded by a signed policy before the tap, verified by signatures after it, and paid for by a party chosen in advance when it fails.
In practice: a per-tap limit, an outstanding ceiling and a loss policy on every terminal.
Money is never moved twice.
A timeout is treated as unknown and checked before any retry. Every money-moving request is idempotent from end to end, and a cascade to a second provider never happens on an unknown.
In practice: an Idempotency-Key on every money call, and 409 on a reused key with a different body.
Built on Bridge
PediWave decides where. Bridge decides whether.
PediWave runs on the Bridge ledger. Bridge holds the balances and the rules: fees, limits, identity tiers, fraud checks, approvals and settlement. PediWave is the product merchants integrate: keys, one payment object, the choice of provider for each payment, the card vault, hosted pages, events, and the merchant side of offline.
The split is deliberate. When a payment is refused for a limit, a tier, a fraud check or a reserve, that decision is Bridge's, and PediWave relays it to you with a code. PediWave never keeps its own copy of a business rule, so the two can never disagree.
It is also why offline works. Bridge already holds the payer's offline balance on the ledger and verifies the hardware-bound signatures on every tap at settlement, so a balance cannot be spent twice.
| PediWave builds | The Bridge ledger provides |
|---|---|
| Merchant keys, scopes and the merchant record | Collector accounts, settlement accounts, pricing and reserves |
One payment object across every rail, with next_action | Collection requests, attempts, authorisation and capture, receipts, partial refunds |
| The card vault, tokeniser and hosted fields (cards coming) | Card collection through provider connections, using tokens only (cards coming) |
| Connectors, routing rules, scoring, cascade and simulation | The transport to providers once PediWave has chosen one |
| Terminal lifecycle, signed policies, batches, exposure and the loss policy | Device keys, identity assertions, verification at settlement and the device balance |
| Settlement views, payouts, transfers and payout batches | Withdrawals, transfers, disbursements with approvals, name enquiry |
| Plans, subscriptions, invoices and Smart Dunning | Mandates and recurring pulls |
| Merchant-scoped, signed events and request logs | A signed event stream, retries and replay |
| Hosted onboarding for sellers | Identity: BVN, NIN and CAC verification, tiers and limits |
| Routing-level velocity caps for offline and payouts | Fraud checks on every posting, screening, limits and approvals |
Merchants integrate with PediWave only. Bridge stays behind it.
Boundaries
What PediWave is not.
- A second ledger
- PediWave keeps no second fee engine, fraud engine or set of balance rules. The ledger behind it is the one source of truth
- An acquirer, at launch
- PediWave does not hold its own acquiring licence at launch. It orchestrates licensed acquirers, banks and switches
- A place your customers keep money
- PediWave holds funds for merchants only. Your customers never fund a PediWave balance; at most they hold a purse you issue, funded from your float
- A consumer wallet app
- We do not run a wallet app for the public. Your own app can host your customers' wallets with our SDK
- A cross-principal agent network
- Agent cash runs only under your own principal. We will not route cash across principals until the law and the licence allow it
Company facts
The details, for your records.
- Product
- PediWave
- Operating company
- PediWave is a product of Pedistack Solutions Inc., United States
- Payment licences
- PediWave operates through licensed acquirers, banks and switches. Our own licence position is published on the Security page when granted.
- Built on
- The Bridge ledger
- Markets
- Nigeria, in naira, at launch. Other countries coming soon Coming
- Card data security
- Cards are coming. See Security & compliance for PCI DSS status
- Data protection
- PediWave is processor for your customers' data. See the DPA
- Sales
- Talk to sales
- Security reports
- [email protected]
Bring us the payment problem you have today.
Offline acceptance, several providers, sellers to pay out: tell us what you need.