Marketplace payment verification at scale: onboard thousands of sub-merchants under one master key, each verifying their own mobile money payments with scoped access.
— reads
A marketplace lives or dies on trust between many small sellers and the buyers who pay them. When a buyer sends mobile money to a seller you have never met, your platform's reputation is on the line for a transaction you did not witness. KODA's Plateforme tier solves that by giving every seller real, independent payment verification while your platform keeps just one relationship to manage.
The model is built for scale from the first day. You onboard sub-merchants under a single master account, and each one receives scoped, restricted credentials tied to their own verified ledger. A seller can only see and act on their own payments; the master account sees aggregate health across the whole network. This isolation is not cosmetic — every sub-merchant has a separate ledger and separate receipts, so one onboarding deal can bring on thousands of sellers without any cross-contamination between them.
Verification itself runs on the The Mobile Money Verification API (3 Endpoints, No Telco Deal), the same engine that powers every KODA product. When a buyer pays a seller, KODA matches the buyer's reference code against the operator's own confirmation SMS on the receiving phone — M-Pesa, Orange Money, Airtel Money, MTN MoMo, Wave and more — and returns a verdict in about three seconds. It is worth stating plainly: KODA never moves, holds or touches the money. It is not a bank or a wallet. It proves the transfer happened; the funds travel on the mobile money rails your sellers already use.
Because there is no telco API, no contract and no integration required to start, onboarding a new seller is fast. A sub-merchant does not need a developer or a bank negotiation — they need only their existing mobile money number and the operator's confirmation SMS, which already arrives on their phone. Buyers, meanwhile, still get the fraud-proof confirmation described on How KODA verifies mobile money payments through any of the Five Ways to Accept & Verify Mobile Money (One Engine): the manual console, WhatsApp, API and checkout, USSD, or inbound SMS. Whichever door a seller prefers, the result is the same locked, verified confirmation.
That locking is central to why a marketplace can trust the network. Every verified reference code is locked forever, so a single code can confirm exactly one payment. A fraudster cannot pay one seller and then reuse the same reference to claim they paid another. On top of that, KODA runs anti-forgery on device streams, fraud scoring and velocity rules, and screenshot forensics. Velocity rules matter especially in a marketplace, where an attacker might try to spray many small fake confirmations across different sellers; the engine sees patterns your individual sellers cannot.
Each seller can also issue White-Label Payment Receipts Your Customers Trust under their own brand, so buyers see the shop they bought from rather than your platform's plumbing. That keeps the buyer relationship where it belongs — with the seller — while the platform still gets a clean, verifiable record of every transaction for reconciliation, payouts and dispute handling. A verified receipt carries the reference, amount, operator and timestamp, which is exactly the evidence a seller needs to win a chargeback or a "I never paid" claim.
There are pitfalls worth avoiding as you grow a network like this. Do not let sub-merchants share one set of credentials — the scoped-key model exists precisely so a compromised seller cannot touch anyone else's ledger. Do not rely on sellers eyeballing screenshots during busy periods; automated verification removes the human error that fraud thrives on. And do not treat verification as an afterthought bolted on at payout time — verifying at the moment of payment is what stops a bad transaction before goods ship.
This design fits high-volume KODA for restaurants, retail, schools & marketplaces particularly well — agent networks, delivery fleets, ticketing platforms, and multi-vendor storefronts — where the number of sellers is large and the average payment is small, so per-transaction trust has to be automatic. Developers can find the integration details on KODA API for developers, including how master and scoped keys relate and how webhook events roll up to the platform level.
One integration, thousands of verified sellers, and a network you can actually stand behind. Head to Get started with KODA free and talk to us about the Plateforme tier for your marketplace.
Yes — the Plateforme tier onboards sub-merchants under one master account, each with scoped keys, verifying their own payments. See KODA API for developers.
Yes. Every sub-merchant has its own ledger, receipts and restricted credentials, so one deal can onboard thousands without cross-contamination.