Skip to content

Reporter app

Three feeds can tell us money arrived: your bank’s alert email, forwarded to us; your bank’s alert SMS, read on your own phone by the version of the app you download from moneylanded.com; and, in the Google Play version, your messages app’s notifications, if you turn that on. Any of them can activate an account. Anyone above a handful of orders an hour should run email forwarding and one phone feed.

The Android app comes as two builds of one app, with the same name and the same package. They differ in how they hear about a payment: the direct download reads your SMS, and the Google Play build asks for no SMS permission at all.

  • Google Play. Get the app on Google Play. It asks for no SMS permission. A payment is confirmed from your bank’s alert email, forwarded to your own moneylanded address (Settings shows it); from your messages app’s notifications, if you turn that on in the app (see Permissions); or by you placing a payment on an order by hand from the Unplaced screen. It has no SMS “connect this phone”, no 24-hour scan to backfill missed credits, and no staff-phone pairing.
  • Direct download. Download the app from moneylanded.com. It confirms from forwarded email and by hand too, and it also reads your bank’s alert SMS on the phone, scans the last 24 hours, and pairs staff phones. It does not read notifications; that is in the Google Play build only. Android will warn you when you install it. Installing from a website needs “install unknown apps” allowed for your browser. The warning is correct: it is telling you this file did not come from Play.

The app is Android only: iOS grants apps no access to SMS at all. On an iPhone, the built-in Shortcuts app does the reporting instead, with no app to install — see iPhone below.

The Google Play build is signed with a key Google holds, and the direct download is signed with our own key. Android refuses to replace an installed app with one signed by a different key, so you cannot install one over the other. To switch, uninstall the one you have, install the other, and sign in again with your email. Everything the app stored on the phone goes with the old install, including the session and, on the direct build, the connected feed. Your account lives on the server, so your orders and settings are still there when you sign in.

The server treats both builds the same. The endpoints on this page are the reporter contract in full, so you can build your own reporter against them instead of using ours.

Email forwarding is free, needs no app, and works on an iPhone. But the delay between your bank sending the alert and the mail reaching us is not something we control or have measured. SMS arrives on the phone in the merchant’s hand, which is why the direct download reads it. Measured once, on one phone, with a live ₹1 credit: a parsed credit reached the server about 160 ms after the phone received the message, with the app in the background and no battery exemptions. The Google Play build can read the same alert from your messages app’s notification instead, if you turn that on. We have not measured how quickly that reaches us, so we quote no figure for it.

Sign in with your own email address. We mail you a link and a six-digit code; type the code into the app and it is signed in for 180 days, sliding on use. From then on the app is your dashboard: home, orders, payment links, unplaced credits, the activity timeline and every setting, all native. There is no web page anywhere in it and no way to open one.

Signing in is not part of the contract on this page. It uses /v1/app/*, a first-party surface versioned with our own clients rather than with the published API, so it is deliberately not in the API reference and you should not build against it. The endpoints below are the contract, and they are what a reporter you build yourself would use.

This section is for the direct download. The Google Play build has no SMS feed, so none of the screens below exist in it. Its Settings → Feed has the notification card described under Permissions instead, and it has no 24-hour scan.

Two ways, and which one you want depends on whose phone it is.

Settings → Feed → Connect this phone. Android asks for SMS access at that moment and not before: a merchant who never connects a phone, because their bank alerts reach us by email forwarding instead, is never asked for the permission at all. Scan the last 24 hours on the same screen backfills credits that arrived before you connected or while the phone was offline.

No pairing code is involved. Your session already proves what a code would prove, and proves it more strongly.

Disconnect this phone on the same screen stops it reporting and deletes what it stored. You stay signed in, and forwarded bank emails keep confirming orders — disconnecting a feed is not signing out.

If SMS access is greyed out when Android asks (direct download only): on Android 13 and newer, an app installed from a browser can have it blocked. Open the app’s info screen, tap the three-dot menu, choose Allow restricted settings, then connect the phone again.

Staff-phone pairing is in the direct download only.

A phone that should carry the bank’s alerts but must not see your orders or change your settings connects with a code instead, and holds only a narrow device token:

  1. Dashboard → Settings → Bank alerts → Generate pairing code. Six digits, valid ten minutes, single use.
  2. Open the app, choose Reporter-only phone, type it in.

That phone reaches no account screen at all — not over the network and not in the app. It reports bank SMS, it can mint a payment link that pays your own account, and that is the whole of it. If it is lost, revoking the device from Settings → Bank alerts stops it; nothing else on your account is exposed.

The app calls:

Terminal window
curl -sS -X POST https://moneylanded.com/v1/devices/pair \
-H "Content-Type: application/json" \
-d '{"code":"418203","device_name":"Counter phone"}'
{ "device_token": "vpd_1f0b...", "tenant_name": "Blue Mug Co" }

No Authorization header: the code is the credential. That makes it the one guessable surface here, so it lives ten minutes, is destroyed the instant it is claimed, and the endpoint is rate limited per source address. An unknown code, an expired one and an already-claimed one all answer identically, so nothing can be learned by trying.

The device token is returned once and stored only as a hash. It is scoped to one account and revocable from Settings; revoking stops reports immediately and leaves email ingestion untouched and every credit it already reported standing. Your own phone’s feed holds a token of exactly the same shape — it is minted by your session rather than by a code, and revoked from the same list.

Terminal window
curl -sS -X POST https://moneylanded.com/v1/reports \
-H "Authorization: Device vpd_1f0b..." \
-H "Content-Type: application/json" \
-d '{"messages":[{"sender":"JD-HDFCBK-S","body":"Credit Alert! Rs.498.99 credited to HDFC Bank A/c XX4558 on 18-09-25 from VPA asha@ybl (UPI 530112345678)","received_at_ms":1758212001000}]}'
{
"accepted": 1,
"rejected": 0,
"results": [
{ "rrn": "530112345678", "status": "matched", "intent_id": "int_9f2c1a77b40e6d3a5c81",
"order_id": "ORD-10432", "paid_paise": 49899 }
]
}

results is in request order, one entry per message. That is what lets the phone raise a notification naming the order — “₹498.99 received for ORD-10432” — which is how a WhatsApp seller knows to ship.

Up to 50 messages a batch. An empty messages array is a valid heartbeat. Retrying is free: credits are deduplicated on the bank’s reference number, and a retry returns the same result object as the first attempt rather than a bare “duplicate”, precisely so the notification still names the order. Of 665 real messages on one device, only 514 references were distinct — 139 arrived more than once — so this is the normal case, not an edge case.

A credit that lands with no order it could be for is filed quietly: {"rrn": "530112345678", "status": "quiet", "reason": "unplaced"}. reason can also be "stale", or "dismissed": a retry answers from the stored credit, and one you have since marked not an order is waiting for nothing. The app raises no notification for any of these, the same as it already does for any status it does not recognise.

What the app does, and what it deliberately does not

Section titled “What the app does, and what it deliberately does not”

The SMS half is in the direct download only; the Google Play build has none of it. It is the same whichever way the phone was connected:

  • A manifest-registered receiver fires on every incoming SMS, app foregrounded or not.
  • It parses on the device with the same rules the server uses, and posts only parsed credits: amount, account last four, date, payer handle, reference, sender id, receive time.
  • OTPs, debits, card spends and promotions never leave the phone. They are not uploaded and rejected; they are never sent.
  • Posts are queued and retried until acknowledged.
  • When a feed is connected, and on demand from Settings, it scans the last 24 hours of bank credits and posts them, which backfills any outage.

The client half, on a signed-in phone, is the same in both builds:

  • Home — today’s confirmed total, what is still open, what is waiting on you, and whether your feed is healthy.
  • Orders, Links, Unplaced, and behind More, Payments, Activity and Settings — the same screens the dashboard has, doing the same work through the same server code, so the two cannot answer differently.
  • While the phone is reporting (the SMS feed in the direct download, the notification feed in the Google Play build), a payment notification names the order and opens the screen it belongs to.

And what it does not do:

  • No customer is ever asked for anything. There is no field for a customer name, phone number or UPI id on any screen. That is the same rule the pay page is held to, and it is absolute.
  • A reporter-only phone gets none of the client half. No orders, no settings, no key. That is the point of the mode, not a limitation of it.
  • No web view, no in-app browser. The dependency that could open one is not in the build.

On our side: raw message bodies are parsed in memory and never stored, never echoed back, and never put in an alert — including when parsing fails.

The direct download from moneylanded.com requests RECEIVE_SMS and READ_SMS. RECEIVE_SMS is how it hears a bank alert as it arrives. READ_SMS is used only for the 24-hour scan, when you ask for it. Android asks when you connect the phone, not before.

The Google Play build requests neither; Google Play restricts those permission groups. If you turn it on, it uses Android’s notification access instead, to read the notifications your phone’s default messages app shows, only to find your bank’s credit alerts.

  • It is off until you turn it on: Settings → Feed → Confirm payments from this phone → Turn on, tap Agree on the disclosure, then allow notification access for moneylanded in Android settings.
  • Notifications from other apps are ignored. A message that is not a bank credit alert is dropped on the phone and is not kept or sent. Nothing that arrived before you agreed is read.
  • A bank credit alert goes through the same server path as one read from SMS: it is parsed in memory, deduplicated on the bank’s reference number, and the raw text is not stored.
  • Turn off in the same card, or notification access in Android settings, stops it. Turning it off in the app also removes the phone’s credentials.

Android can hide the text of a message notification from apps. On Android 15 with Google Messages it can, and then the app cannot read the alert. The app says so in Settings → Feed, and email forwarding is the route for that phone. Gmail forwarding works on every phone.

Both builds confirm the same orders. Only the direct download reads the phone’s SMS, and only the Google Play build reads notifications.

Pay yourself ₹1 by UPI. The first verified credit binds your account’s last four digits, and from then on a credit for any other account is rejected rather than matched. This is what stops somebody else’s forwarded alert ever confirming one of your orders.

iOS grants apps no access to SMS, so an iPhone reports through its built-in Shortcuts app instead: an automation that runs when a message containing “credited to” arrives and posts that message to us. There is nothing to install.

Dashboard → Settings → Bank alerts → Set up an iPhone makes a reporter-only key and shows it once, inside two things:

  • A description to paste into Shortcuts. On iOS 27 with Apple Intelligence (iPhone 15 Pro or newer), tap + in Shortcuts and paste it, and Apple Intelligence builds the automation. Check that it made the trigger — Notify When Run off — as well as the four steps that follow it.
  • The same automation as manual steps, for any iPhone on iOS 17 or later: a message trigger on “credited to”, Notify When Run turned off, set to run immediately; then Format Date; Get Contents of URL; Get Text from Input, with Contents of URL as its input; and an If set to Text has any value, with Show Notification (text: Text) inside it.

Notify When Run has to go off by hand — otherwise iOS shows “Running your automation” every time a credit SMS arrives, on top of whatever the Shortcut itself shows.

Run it once by hand. It should answer that it is connected to your account; if iOS asks whether it may connect to moneylanded.com, choose Always Allow. Then pay yourself ₹1 by UPI. If your account is not switched on yet, the notification should say it is now. If it already is, that payment is not for an order, so no notification appears, but this phone’s Last seen time in Settings updates.

The Shortcut calls:

Terminal window
curl -sS -X POST "https://moneylanded.com/v1/reports/shortcut?v=2" \
-H "Authorization: Device vpd_1f0b..." \
-H "Content-Type: application/json" \
-d '{"message":"Credit Alert! Rs.498.99 credited to HDFC Bank A/c XX4558 on 18-09-25 from VPA asha@ybl (UPI 530112345678)","received_at":"2025-09-18T21:43:21+05:30"}'
₹498.99 received for order ORD-10432.

It is POST /v1/reports for one message, shaped for what a Shortcut can build, plus the ?v=2 marker:

  • No sender. iOS hands a Shortcut a contact card rather than the sender id, so the message alone picks the bank’s rules. The sender never proved anything: the device key and your bound account are the checks, and both still run.
  • The time as ISO 8601 with its offset, which is what Format Date writes. A missing or malformed time, or one more than ten minutes from our clock, is refused and records nothing. Recording the payment anyway would spend its bank reference, and the email copy of the same payment could then never match.
  • A text/plain reply, which the Shortcut shows as a notification when it is not empty — see Replies, below. It never contains the message, the payer, the reference or any account digits.
  • An empty message is the setup test. It marks the phone as seen and names the account the key belongs to.

Most replies are one sentence, same as always — “₹498.99 received for order ORD-10432.” Three cases are different on this recipe:

  • A credit that landed with no order it could be for gets an empty reply here. A Shortcut built before ?v=2 existed still gets one sentence: “{amount} received. No recent order is for this amount, so there’s nothing to do.”
  • The credit that switches your account on gets a sentence on either recipe: “{amount} received. Your account is switched on, and your live API key works now.”
  • Once your account is switched on, this recipe also replies empty to a message that was not a bank credit, and to one for a different bank account. Both got a sentence before; neither is something you need to see.

An empty reply is a 200 with nothing in the body. Paired with If Text has any value → Show Notification, the Shortcut raises no banner for any of the three cases above — which is the point, once your account is live. A Shortcut built before now has no ?v=2 to ask for this and keeps getting a sentence for everything. Settings → Bank alerts → Set up an iPhone now hands out this recipe; rebuild the automation from there to switch.

What it gives up compared with the direct-download app:

  • Every message containing the phrase leaves the phone, personal ones included. We read it for a bank credit in memory and never store it, but the app filters on the phone and a Shortcut cannot.
  • No retries and no backfill. If the phone is offline when the SMS arrives, that report is lost. Keep Gmail forwarding set up as a second feed.
  • iOS decides when it runs. With Notify When Run off it runs without a banner of its own; after an iOS update, check that the automation is still switched on.

The rate limit is the app’s: one budget per device, whichever endpoint it uses.