Pay by any method, land in any bank
Collect on card, UPI, netbanking, wallet or EMI through the integrated gateway, then settle to a bank account by IMPS or NEFT. Any bank in India, one flow.
Business software for letting agents and property-management agencies: collect rent by any method, settle to any bank in India by IMPS or NEFT, and keep a record of every step.
Payments, master records, reports, audit, rate card and receipts — one platform, one agent code, one record of what happened.
Collect the rent by whichever method the tenant chooses, then disburse to the landlord. The full charge split and the landlord's net amount appear before you confirm.
Tenants and landlords are stored as reusable master records. The beneficiary account is checked against the bank, and the name the bank returns is the name kept on file.
The transaction report, the overall ledger and the gateway ledger, filterable and exportable. Every row carries its status, its rail and its bank reference.
One append-only log per transaction, each row SHA-256 hash-chained to the row before it. Payloads are redacted before storage, so the record is safe to read.
UPDATE and DELETE.Payment types, banks and commission rates are administrator-controlled. Charges are computed from the rate card that applies to the method and card type used.
Every transaction produces a printable receipt: both parties, the bank, a masked account number, the bank reference, the order ID and the live status.
Click a step to see what the agency sees at that point in the flow.
Six things the platform does on every transaction, whether anyone is watching or not.
Collect on card, UPI, netbanking, wallet or EMI through the integrated gateway, then settle to a bank account by IMPS or NEFT. Any bank in India, one flow.
Bank-confirmed account and account-holder name on every landlord, and PAN verification of the sender above ₹50,000.
The full charge split and the landlord's net amount, on screen before you confirm. Nothing is deducted silently.
When the bank confirms a failure, the amount reverses to your wallet automatically. No ticket, no chasing.
Every event appended to one hash-chained log. The database refuses updates and deletes outright.
Both parties, the receiving bank, a masked account number, the bank reference (RRN), the order ID and the live status — printable, and tied to the same transaction ID as the audit trail.
Every event in a payment's life is written once to a single append-only log, keyed by the transaction ID: the agency's request, the gateway's callback, the outbound call to the bank with its exact payload, the bank's exact reply, the ledger posting and any refund.
Each row is SHA-256 hash-chained to the row before it. Database triggers refuse UPDATE and DELETE outright, and a verification routine can prove the chain is intact — or name the exact row that was altered.
Stored payloads are redacted before they are written: API credentials stripped entirely, PAN partially masked, account and card numbers reduced to their last four digits. Detailed enough to settle a dispute, safe enough that reading the log is not itself a breach.
This is tamper-evidence, not a claim of invulnerability: history cannot be altered without the alteration being provable. [[CERTIFICATION — confirm before publishing]]
{ "event": "payment.request",
"txn_id": "TXN-24081-5507",
"kcode": "KC-0148",
"amount": 45000.00,
"method": "UPI",
"pan": "ABCDE••••F",
"prev_hash": "9d77…41c0" }
PAN partially masked. Credentials stripped before storage.
{ "event": "gateway.callback",
"order_id": "ORD-77F1D2E9",
"status": "captured",
"method": "upi",
"signature": "[verified]",
"prev_hash": "c41f…9ab2" }
Gateway API credentials removed entirely.
{ "event": "bank.transfer.request",
"mode": "IMPS",
"account": "••••4417",
"ifsc": "XXXX0000XXX",
"name_at_bank": "[as returned by bank]",
"amount": 44205.27,
"prev_hash": "7be0…c1d4" }
Account number reduced to its last four digits.
{ "event": "bank.transfer.response",
"status": "SUCCESS",
"rrn": "418923077461",
"mode": "IMPS",
"bank_message": "Txn processed",
"prev_hash": "1a58…30ef" }
The bank's exact reply, stored as received.
{ "event": "ledger.post",
"collected": 45000.00,
"service_charge": 673.50,
"gst": 121.23,
"disbursed": 44205.27,
"prev_hash": "e309…77b6" }
The same split the agency saw before confirming.
{ "event": "receipt.issued",
"order_id": "ORD-77F1D2E9",
"rrn": "418923077461",
"account": "••••4417",
"status": "SUCCESS",
"prev_hash": "bd12…04aa" }
A refund, where one occurs, joins the same chain as its own row.
Charges come from a rate card that varies by payment method and card type: a service charge, a distributor margin and an agent margin, plus GST. Drag the amount to see how the breakdown is presented.
Illustrative only. Actual rates are set per agreement, and the product shows your exact split before every confirmation.
At ₹50,000 and above, PAN verification of the sender is also required.
Stop reconciling bank transfers by hand: collect by the method the tenant prefers and pay the landlord to a verified account, with a receipt for both sides.
Run many tenants and landlords under one agent code, with reusable master records and the exact charge split visible on every transaction.
Answer a payment questioned months later with a record instead of a recollection, and let confirmed failures reverse themselves.
Any bank account in India that can receive IMPS or NEFT. You enter the account number and IFSC, and the account is verified against the bank before any transfer is attempted.
IMPS is near-instant and runs outside banking hours. NEFT is processed in the banking system's batch cycles, so it settles later on working days. The rail used is recorded on the receipt.
When the bank confirms the transfer failed, the amount is reversed to your wallet automatically — no support ticket needed. The bank's reply and the refund are both written to that transaction's audit trail.
Payments at or above ₹50,000 carry an additional PAN verification of the sender, alongside the OTP confirmation of their mobile number. Below that threshold the OTP and the beneficiary bank verification apply as usual.
It carries both parties, the bank, a masked account number, the bank reference (RRN), the order ID and the live status — printable, and tied to the same transaction ID as the audit trail behind it.
Your agency sees its own complete record. Administrators see everything, filterable by date, category, severity, actor, transaction ID and free text. Stored payloads are redacted first: credentials stripped, PAN partially masked, account and card numbers cut to their last four digits.
No. The agency signs in with its agent code and registers the tenant as a sender. The tenant confirms their mobile by OTP and pays through the gateway by card, UPI, netbanking, wallet or EMI.
From a rate card that varies by payment method and card type: a service charge, a distributor margin and an agent margin, plus GST. The full split and the landlord's net amount are shown before you confirm. Rates are set per agreement.
Online rent payment is launching shortly. Agency partners can sign in today, or talk to us about onboarding.
Powered by MOS Utility Ltd