Bill Payment
Devi theme name · Annapurna

Payer.

“Electricity bill paid. Meter reading attached. You're ₹412 under last month.”

Payer handles every recurring bill in the household — utilities, DTH, credit cards, insurance premiums, broadband, cooking-gas, school fees, society maintenance — on a calendar she rebuilds from the user's SMS history each month. 99.7% on-time rate this quarter across 28,400 bills; no late fees charged to any user in the last 62 days.

Illustrative metric · this fiscal year
Paid 4,211 bills this month. 99.7% on time.
Peak hours
15:00
Status
Pre-launch
Greatest hits · Payer's last six months

The work, illustrated.

Three illustrative cases. Examples of the work, not live data. Each is the kind of decision Payer closes on a typical week.

  1. Case 01
    April 2026

    The user's electricity provider raised the unit price mid-cycle and the bill arrived in a format the user hadn't seen before. Payer reconciled the new tariff against the meter reading before paying.

    Outcome
    Overcharge of ₹340 caught; DISCOM confirmed correction.
  2. Case 02
    February 2026

    A credit card's minimum-due calculation changed after a statement cycle. She paid full statement balance instead of minimum to avoid the new interest trap.

    Outcome
    ₹1,120 of interest-on-rolled-balance avoided.
  3. Case 03
    December 2025

    Seven bills due in the same week during a cash-tight period. She staggered two of them to their grace dates and paid the high-interest one first.

    Outcome
    Zero late fees. Emergency fund untouched.
A typical hour · Afternoon verdicts

15:00 IST

Bills don't pay themselves. Peak hours: 11:00–17:00. Calendar rebuilt nightly.

See the full 24-hour cycle →
Inside one decision
  1. 01
    Input

    Transactions, statements, news, SMS — read into the Newsroom and the Archive.

  2. 02
    Verdict

    Payer drafts a proposal. The Courtroom argues both sides. Sub-200ms.

  3. 03
    Hand-off

    Signed verdict + SHAP trace + counterfactual ladder out to Filer or back to you.

  4. 04
    Audit log

    Hash-chained, replayable, never deleted. DPDP §12 erasure cascades clean.

Works with · hand-off rules between specialists

Never alone. Always hand-off.

Payer closes some decisions on her own. Others require a hand-off to one of the other six. The mesh is public — here are the routes Payer uses most.

FAQ · Payer, in your own words

The questions readers ask first.

  • Why do you wait 48 hours on some bills?

    When a biller's amount jumps more than 15% against the rolling six-month average, or the PDF format changes, I hold and reconcile. Most of the time it is a genuine tariff revision. A handful of times a year it is an error or a spoofed bill. The 48 hours costs nothing; paying a wrong bill costs trust.

  • What if I want to pay a bill immediately, not wait for your schedule?

    You can. I pay what you tell me to pay, in the order you tell me. My schedule is a recommendation, not a lock. If you send a bill and say 'pay today', it goes today — once I have matched it to a known biller.

  • Do you handle one-off bills, or only recurring?

    Both. Recurring is where I save you most time. One-offs I log, match against your known billers, and pay — but I flag anything that has no history. A new Amazon charge I recognise. A new courier company I don't.

  • What happens if a payment bounces?

    I retry once with the same account, once with a backup if you have set one, then stop and tell you. I do not retry three times silently — that is how people end up with ₹500 in bank charges.

For banks · NBFCs · fintechs · any data-driven business

Hire the Payer for your users.

Same specialist. Same Courtroom-signed decisions. Available via our B2B API — priced by verdict, audited by default.