Everything BitriPay does
One account, one API and one ledger behind every way money can reach a business in the markets we serve.
25 of 41 are switched on for this deployment. Where a capability is built but waiting on an authorisation, the page says so plainly rather than selling it — this list is generated from the platform’s own state, not written by hand.
Take the money
Every way a customer can hand money to a business, from a printed code on a wall to a hosted checkout.
BitriQR payments
One printed code that works for a customer with the app, a customer with only a camera, and a customer whose bank has never heard of BitriPay — because the code is EMVCo underneath and signed on top.
Payment links
A link you can paste into WhatsApp that behaves like a full checkout — reusable or single-use, with an expiry, a reference and a webhook when it is paid.
Money requests
A request that arrives as a notification the other person can approve with a fingerprint, instead of a message they have to act on from memory.
Hosted checkout
A checkout that offers the payer only the rails that can actually complete their payment, decided at the moment they arrive rather than listed hopefully on a page.
Point of sale
A till that runs on the phone already in the shopkeeper’s hand, with line items and VAT, and no hardware to buy, charge or replace.
Build on BitriPay
The API, the webhooks, the SDKs and the plugins that put payments inside somebody else’s product.
The gateway API
A payments API whose documentation is generated from the same table that serves the requests, so the reference can never describe an endpoint the platform does not have.
Signed webhooks
Deliveries you can verify two independent ways, replay yourself from the dashboard, and receive on a built-in inbox if you have nowhere to host an endpoint yet.
Connected accounts
Create your customers’ merchant accounts by API, take payments for them with your own key, keep your fee — and hand the account over whenever they are ready, keys and history intact.
Smart Route
Routing scored from measured success rates, cost and latency per connector, with a circuit breaker that takes a failing rail out before your customers find it.
National switch connection
An adapter written against an internal contract rather than a protocol, with a simulator that reproduces the awkward cases — a timeout after a financial effect, a contradictory late rejection — before a real connection exists.
SDKs and plugins
SDKs in three languages and a shop plugin generated against the same operation table as the API, so an SDK cannot describe a call the platform does not have.
Move the money
What happens to money once it has arrived: wallets, transfers, payouts, cash and the journey across a border.
Wallets and transfers
A transfer between two accounts is one balanced posting on a double-entry ledger, not a message between two systems that might later disagree.
Agents and cash
Cash in and out through a human being near you, with the agent paid a commission the app shows before you confirm and a float the platform watches so the agent does not run dry mid-queue.
Adding money
Funding that is confirmed by evidence from the operator or the bank, not by the customer saying they paid — so a balance never appears that no money backs.
Withdrawals and payouts
A payout that is held against your balance the moment you request it, executed under four eyes above a threshold, and reversed on the ledger if the rail refuses — so money is never both spent and still spendable.
Remittance
A quoted rate that is locked for the life of the quote, with the margin stated in basis points — so the family at the other end gets the number you were shown, not whatever the rate became.
Currency exchange
Conversion quoted against a published mid rate with the margin in basis points, posted to the ledger as two linked legs so the cost of every conversion stays measurable afterwards.
Virtual cards
A card number for the sites that only take cards, issued against your own balance, with the card details never stored by BitriPay in a form that could be taken from it.
Restricted wallets
Money that can only be spent on what it was given for, enforced at the posting rather than trusted to the recipient — so a school allowance buys school things.
Goal savings
Savings kept in a separate balance with a named goal, so the money is out of the way of daily spending — and described honestly as a set-aside balance rather than an interest-bearing account.
Bills, airtime and vouchers
Fulfilment that is confirmed by evidence from the biller or the operator before it is called done, with the money returned automatically when the confirmation never comes.
P2P marketplace
Trades between people where the money is held in escrow until both sides have done their part, and a dispute goes to a human with the evidence already attached.
Bank connections
Linking a bank account to pay by bank and to verify income, with consent that is explicit, scoped and revocable from inside the app rather than buried on somebody else’s site.
Gift cards and vouchers
A voucher that is a claim on the issuer recorded on the ledger, redeemable once and traceable — not a code in a message that may already have been spent by somebody else.
Reach everyone
The customers a payment platform normally gives up on: no smartphone, no data, no signal, no electricity, no reading.
USSD and SMS
The same ledger, the same balances and the same limits reached from a feature phone with no data — not a reduced product for poorer customers, the same product through a different door.
BitriPay Lite
A full web app that works with JavaScript switched off entirely, rendered on the server, so it loads on a slow connection and an old browser instead of showing a spinner.
Offline payments
A signed promise exchanged between two phones with no network at all, with counters and nonces so the same promise cannot be spent twice when the signal returns.
Alerts you cannot miss
A loud alarm and a long vibration designed to be heard across a market and understood without reading, because the sound is the receipt a trader actually relies on.
Run the business
The books, the settlement, the statements, the disputes and the people who look after them.
Team and roles
Staff get their own sign-in with a role the software enforces every time, including a refund limit the owner sets — so delegating the counter does not mean handing over the business.
The ledger
A double-entry ledger where balances are derived from postings rather than stored, corrections are opposing entries rather than edits, and invariants are enforced at write time instead of checked by a nightly job.
Settlement and statements
A settlement statement that is numbered, hashed and reproducible, showing the provider fee, the platform fee and the tax on it as separate lines rather than one net figure.
Refunds and disputes
A refund that reserves the money atomically before it is promised, and a dispute that is an object with a timetable rather than an email thread somebody is supposed to remember.
Corridor network
A corridor records which phase it is in, under whose licence and with which custody model — as data, so moving from an orchestrator to a licensed issuer changes rows rather than code.
Referrals and growth
Rewards that pay on a real outcome, not a signup, with the attribution and the reward both visible to the person who earned them.
Support and help
Support that can see the same ledger and the same events you can, so an answer is read off the record rather than guessed — and cannot change your balance to make a problem go away.
Bulk payouts
A payout file that is validated before anybody approves it, approved as a batch, and reports per row — so one bad line does not fail the payroll and does not get paid twice on the retry.
Subscriptions and recurring billing
Recurring collection on a mandate the customer confirmed, with dunning that retries on a published schedule and a cancellation that actually stops the money.
Prove it
Identity, risk, the ledger’s own invariants and the evidence a regulator asks to see.
E-money and safeguarding
An issuance rule the platform refuses on rather than reports on: e-money cannot be issued beyond cleared safeguarded funds, checked at the moment of issuance rather than at the end of the month.
Identity and tiers
Tiers that let somebody start with a phone number and grow into higher limits, so verification is a ladder rather than a wall at the front door.
Risk and compliance
A sanctions screen that runs inside the posting, before money moves, so a blocked payment is refused rather than recalled — and every alert becomes a case with a decision and a name against it.
Credit readiness
A signal built from your own payment history that you choose to share with a lender — not a score held about you, sold about you, and used to refuse you without explanation.