Every month, someone has to ask your bank for money.
A mandate is your standing permission for that ask. This is a working back office: follow a recurring payment from a stack of signed cheques in a wooden vault to a UPI AutoPay approved in four seconds, and break it on purpose to see what fails.
Funds insufficient
Forty years in four eras
Pick an era to read its storyboard. Each one fixed the worst problem of the one before it, and created a smaller new one.
Watch messages move between the four parties
Pick a scenario and press Play, or walk through it one message at a time. Every arrow is a real message in the modern network; the log on the right records it like an operations console would.
Transaction log
—The problems each era had to solve
Filter by where the problem shows up. Open a card to see how each era handled it.
Mandate sandbox
Set up a mandate as the customer, approve it, then run the billing calendar as the merchant. Try a debit above the limit, an empty account, a pause, or a debit after you revoke.
Jargon buster
The words bankers use for all of this, in plain language.
Run the same loan EMI through four eras of banking
You play every desk: the payer filling the form, the lender's office, the bank clerks, the clearing house. Switch on faults to see the edge cases each era had to live with. Your runs are logged for the comparison tab.
A direct debit is two systems shaking hands.
One system remembers what the customer agreed to. The other moves the money under a shared rulebook. In India they are NACH’s Mandate Management System and the NACH debit rail; every country with direct debits has some version of the same split.
Who does what in the life of a mandate
Pick an event. The layer that does the work lights up, and the line between them shows what one asks the other.
Mandate Management System
Lifecycle and registry: the brain and the vaultEFT Direct Debit rail
Protocol and clearing: the rules and the pipeResponsibility matrix
Which layer owns each capability. The highlighted rows matter for the event you picked.
Push versus pull
The payer always sits on the left and the payee on the right. Watch which way the instruction travels compared with the money.
Clearing log
InstructionMoneyFailureOne debit, four stages, any rail
Walk a direct debit from consent to settlement. Switch the rail to see the same stage under India’s NACH, the US ACH network, SEPA in the eurozone, or UK Bacs. The record on the right fills in as each stage adds its data.
Mandate and debit record
The same idea around the world
Every scheme answers the same questions differently: where the mandate lives, how the customer agrees, how much warning they get, and how they get money back. Select a row for details.
Scheme rules change. Notice periods and refund windows here are scheme defaults as commonly published; check the current rulebook (NPCI, Nacha, EPC, Bacs, AusPayNet/NPP, Payments Canada, Banco Central do Brasil) before relying on them.
Every rupee moves twice: once on a rail, once on a ledger.
A payment network carries the message and settles between banks. Each bank’s core banking system posts the debit and credit to real accounts. Explore the rails one by one, then run them side by side with a live ISO 20022 inspector and a double-entry ledger.