moneylanded

Customers pay by UPI straight into your bank account. We read your bank’s own alert and tell you which order the money was for. The money never passes through us, so there is nothing to settle, nothing to withdraw, and nothing to reconcile at month end beyond what your bank already shows you.

The shape of it

you ── POST /v1/intents ─────────▶ an order
customer taps pay ───────────────▶ POST .../reserve ──▶ a UPI link with an exact amount
customer pays ───────────────────▶ their bank ──▶ YOUR bank
your bank's alert ───────────────▶ us ──▶ the order is confirmed
you ── GET /v1/intents/{id} ─────▶ confirmed, with evidence

Four calls, end to end, in Quickstart.

The one thing that will surprise you

A UPI deep link lets the payer set a reference and a note. Neither is ever returned to the payee. We checked twice: 665 real HDFC credit SMS carry no reference and no note in any of three historical formats, and a live credit email — which is richer, it even carries the payer’s name — carries neither either.

So the amount is the only field anybody controls before the customer pays, and the amount is how we tell one order from another. When two customers are paying ₹499 at the same moment, the second is offered ₹498.99. Always a discount, never a surcharge: the money that lands is never more than the price you set.

That is the whole trick, and Why amounts differ by paise explains how to invoice it so your books balance to the paisa.

What this is not

• We never hold your money. Not in escrow, not in a nodal account, not for a second. We are a technology service provider and never a payment aggregator.
• We never ask your customer for anything. No UPI ID, no reference number, no screenshot. The pay page has no input fields at all.
• We never decide by who paid. The payer’s name and UPI ID are shown to you as your receipt and decide nothing.
• We never guess on time. A credit that could belong to two open orders is parked for you to place, not assigned to the likelier one.

Where to go

Quickstart	Four calls, real request and response bodies.
API reference	Every endpoint, generated from one OpenAPI file.
Why amounts differ by paise	And how to invoice the discount.
Evidence	What a confirmation actually proves.
Limits	What this cannot do, in full. Read it before you ship.