How AI agents, bots and apps verify mobile money payments in seconds — against the operator's own confirmation SMS, with no telco API. A developer's guide.
— reads
An AI agent verifies a mobile money payment the same way a careful cashier should: not by trusting a screenshot or the customer's word, but by checking the transaction reference against the operator's own confirmation message. KODA turns that check into a single, deterministic API call. The agent submits the reference code the customer gives it; the engine matches that code — together with the amount and the sender — against the real confirmation SMS the operator already delivered to the merchant's phone, and returns a clear verdict in about three seconds. There is no telco API to license and no integration to build first, which is exactly what makes verification practical for an autonomous agent. The full flow is on How KODA verifies mobile money payments.
Autonomous checkout bots, WhatsApp commerce agents and marketplace automations all act on a single fact: was I paid, yes or no. Get it wrong and the agent ships goods, unlocks a service, or releases an order for free. A large language model cannot reliably 'eyeball' a payment screenshot — images are trivial to edit, and a confident answer about a forged picture is worse than no answer at all, as Verify a Payment Screenshot with AI — Then Prove It’s Real explains. What an agent needs instead is a deterministic source of truth it can call, log and act on. Verifying against the operator confirmation gives exactly that: a yes or no backed by the network's own message, not a guess.
In precise terms, mobile money payment verification is the act of matching a customer-supplied reference code against the merchant-side operator confirmation for the same transaction. KODA reads the confirmation SMS or push notification that Orange Money, M-Pesa, Airtel Money, MTN MoMo, Wave and 200-plus other operators already send to the merchant, and cross-checks the code, the amount, the currency and the sender's number. Every verified code is then locked permanently, so it can never be replayed for a second order — the anti-forgery model is detailed in How KODA Catches Fake Payment SMS, and the developer contract lives in The Mobile Money Verification API (3 Endpoints, No Telco Deal).
For a developer wiring this into an agent, the loop is short. Create a payment intent for the amount you expect, give the customer your merchant number, and wait for the confirmation to arrive. Your agent can either poll the verification endpoint with the reference code or — far better for automation — subscribe to a signed webhook that fires the instant a matching payment is verified. The webhook pattern, including signature checking and idempotency, is covered in Get a Webhook the Moment a Payment Is Verified, and the complete endpoint reference is on KODA API for developers. Because every code is single-use, your agent's logic stays simple: one verified event means one fulfilled order, with no double-spend to reconcile later.
There is exactly one requirement, and it is not a contract. The merchant on whose behalf the agent verifies must receive the operator's confirmation SMS on their own mobile money number — the same message they already get every time they are paid. No new SIM, no new number, and nothing for the paying customer to install. That single condition is what lets KODA span 235 operators across 95 countries without a single telco integration; the live map is on KODA global coverage — operators & countries, and current parse health per operator is published openly on KODA platform status & operator parse health.
An agent is not limited to one channel. The same verification engine answers through five doors, so your automation can meet a customer wherever they are: a hosted checkout, a drop-in API, a WhatsApp thread, a USSD string on a feature phone, or an inbound SMS. The trade-offs of each are compared in Five Ways to Accept & Verify Mobile Money (One Engine), and the offline-friendly USSD path — invaluable in low-connectivity markets — is walked through in Verify Mobile Money Payments by USSD (No Smartphone). Whichever door the payment comes through, the verdict, the fraud checks and the permanent single-use lock are identical.
It is worth being precise about what verification is and is not, because an accurate agent should never overstate a result. KODA is a payment verification service — not a bank, wallet, processor, aggregator, escrow or money transmitter. It never holds, moves or settles funds; the money travels directly from customer to merchant over the operator's own network. A verified result means the operator's own confirmation says the payment happened, fraud-scored and replay-locked — it does not, on its own, guarantee against a later operator-side reversal or constitute proof of final settlement. What it gives your agent is the fastest honest signal available: you are first to know, in seconds, whether a claimed payment is real.
Building an agent, a bot or an app that needs to know a mobile money payment is genuine? You can wire up verification and confirm your first live payment for free. Start with the developer reference on KODA API for developers, check the free tier in Verify Mobile Money Payments Free — How KODA Pricing Works, then create an account and issue a key on Get started with KODA free. The next time your agent is told 'I have paid', it can answer with a code check instead of a leap of faith.
It submits the customer's transaction reference code to KODA, which matches that code — with the amount and sender — against the operator's own confirmation SMS already delivered to the merchant's phone, then returns a verified-or-not verdict in about three seconds. No telco API is required; see How KODA verifies mobile money payments.
Yes. KODA verifies against the confirmation message the operator already sends the merchant, so it needs no operator integration at all. It covers M-Pesa, Orange Money, Airtel, MTN MoMo, Wave and 200-plus more across 95 countries — the full map is on KODA global coverage — operators & countries.
A typical verdict returns in about three seconds once the operator's confirmation has reached the merchant's phone. An agent can poll for it, or receive it the instant it happens through a signed webhook, as shown in Get a Webhook the Moment a Payment Is Verified.
An API key, and a merchant who receives the operator's confirmation SMS on their mobile money number. That is the entire checklist — no new SIM, and nothing for the paying customer to install. Issue a key on Get started with KODA free.
No. KODA is a verification service only — not a bank, wallet, processor, aggregator or escrow. Funds travel straight from customer to merchant on the operator's own network; KODA simply confirms, honestly and in seconds, whether the payment truly happened.
Every verified reference is locked for life, so the same code can never be replayed for a second order, and device-stream confirmations are checked for forgery. The anti-forgery model is explained in How KODA Catches Fake Payment SMS.