Skip to content
Kisoasms

Mobile money · MVola · Orange · Airtel

Payment texts, structured.

Confirmation SMS landing on your paired phones becomes a record your system can use — amount in Ariary, counterpart, reference — and a webhook the moment it arrives.

Read the API docsDownload the app

mobile_money.detected · verified: false, always

One confirmation becomes

  1. The SMS arriveson a paired phone, the default SMS app
  2. Templates match itMVola, Orange Money, Airtel Money
  3. A record appearsamount, counterpart, reference — unverified
  4. A webhook firesmobile_money.detected to your endpoint

What is recognised

Three providers, fixed templates.

Known confirmation formats are recognised exactly, with no model involved. From each one Kisoasms extracts the same three things.

  1. 01

    MVola mvola

    Deposit and transfer confirmations are matched against fixed MVola templates: amount in Ariary, the counterpart number, and the transaction reference.

  2. 02

    Orange Money orange_money

    Orange Money confirmations are matched against fixed templates: amount in Ariary, the counterpart number, and the transaction reference.

  3. 03

    Airtel Money airtel_money

    Airtel Money confirmations are matched against fixed templates: amount in Ariary, the counterpart number, and the transaction reference.

amount_ariary
The amount in Ariary, as a number — 150 000 Ar arrives as 150000.
counterpart
The other side of the transfer: the number that sent or received the money.
reference
The transaction reference from the message, for matching against your books.

Record and webhook

One shape, twice.

The record your dashboard shows and the webhook your endpoint receives carry the same fields — including the flag that matters most.

Sample record
{
  "provider": "mvola",
  "amount_ariary": 150000,
  "counterpart": "034 12 345 67",
  "reference": "AB12CD34",
  "verified": false
}
mobile_money.detected
{
  "event": "mobile_money.detected",
  "data": {
    "provider": "mvola",
    "amount_ariary": 150000,
    "counterpart": "034 12 345 67",
    "reference": "AB12CD34",
    "verified": false
  }
}

Subscribe to mobile_money.detected like any other webhook: signed HTTPS callbacks, retries on failure, and a delivery log you can replay.

The unverified rule

An SMS is not proof of payment.

Anyone can write an SMS that looks like a confirmation. Kisoasms reads what the message says — it cannot prove money moved.

Every record carries verified: false

Treat a detected record as a hint to check — against the provider's own balance, statement or API — never as confirmation that funds arrived. Build that check into your flow before you release goods, credit wallets or mark invoices paid.

Optional AI recognition

Off until you ask for it.

Fixed templates miss some messages: wording changes, new formats. For those, an AI-assisted fallback exists — disabled for every organization until someone turns it on.

  • Off by default, enabled per organization

    Nothing is sent to a model unless your organization enables AI recognition. Template matching — which involves no model at all — keeps working either way.

  • Masked before it leaves

    One-time codes and phone numbers are masked before anything is sent to the provider, so the model sees the shape of the message, not the secrets in it.

  • Groq or Google Gemini

    Recognition runs through Groq or Google Gemini, and only for organizations that enabled it. Everything else stays exactly as above — including verified: false.

Watch a confirmation become a webhook.

Pair a phone, receive a mobile-money SMS, and see the record and the webhook arrive together. Free during beta.

Get startedRead the API docs