Gateway or Aggregator: Whose Books the Money Passes

One question separates them, and it is not a question about names: does the money pass through this party's own books. A payment gateway carries the instruction and never receives a rupee, so the business is paid by somebody else. A payment aggregator does receive the money, for many businesses, and pays each of them afterwards, so a business still waiting holds a claim on it rather than cash.

Both words turn up on the same sheet of the same agreement, used as though they were interchangeable, and a reader can easily come away unsure which one was signed with. The confusion is not a failure of attention. The two words are used loosely in ordinary trade, they have drifted, and the front of an agreement is written to introduce a party rather than to answer the one question that actually matters about it.

The words are the wrong place to start. The money is the right place, and it puts one question to every party in a payment chain: does the money pass through that party's own books on its way to the business. Everything else worth knowing about the two jobs is a consequence of the answer to that single question, and the answer is a fact about an arrangement rather than a fact about a name. Two parties described with the same word can answer it differently, and one party can answer it one way for one of its arrangements and the other way for another of its own.

What is the one question that separates these two jobs?

The definitions are what confuse people. Put the question before either of them. Does the money pass through this party's own books. Not does it see the money, not does it know about the money, not does its name appear anywhere near the money. Does the money arrive on its side of the ledger, sit there for a while as an amount it has and an amount it owes onward, and leave again.

Once that one question is answered, three others answer themselves. Whether the party can decide when the business is paid. Whether the party is holding money that is not its own in the meantime. Whether a business waiting to be paid has a claim on that party or on somebody else entirely. None of those three is a separate fact to be gone and found out. Each one follows from the first answer. A comparison of these two jobs is therefore not a list of features but one row and its consequences.

The domestic case happens to be exact rather than merely similar. Suppose a neighbour helps with the sale of a cupboard. In one arrangement the neighbour puts the buyer in touch with the seller, the buyer hands the seller the money directly, and the neighbour never touches a rupee. In the other arrangement the neighbour collects the money from the buyer and brings it to the seller afterwards. Both neighbours helped. Only the second one was ever holding the seller's money, and only the second one is the person to go and see if the money does not turn up.

What does a payment gateway do, and what can it never do?

A payment gateway takes the payer's instruction from wherever it was given, carries it to whoever has to decide on it, and carries the answer back. Carrying that message is the whole of the job. The money was never routed anywhere near the gateway in the first place, so a gateway does not receive the money, does not hold the money and does not pass the money on.

Here is the practical half of the whole comparison, stated flatly: a gateway cannot delay a business's money, cannot lose a business's money, and cannot fail in a way that leaves a business out of pocket on a payment somebody has already made. Not because it is careful or well run, which is a separate matter altogether. Because there is nothing of the business's for it to delay, lose or fail with. Nothing can be mislaid that never arrived.

Take the food stall outside one office building. Its payments run through a gateway, so the instruction goes out and the approval comes back and the screen says done. The money for those sales then arrives from a different party altogether, on a different path, and the gateway is not in that sentence at all. If a payment is late, the stall has a question and the gateway is not the party to ask it of. Who signed the stall up and stands behind its instructions in the first place is a separate job, covered separately and assumed here.

What does a payment aggregator do, and what follows from taking the money in?

A payment aggregator takes in the payer's money for a great many businesses at the same time, keeps it while it works out how much of the total belongs to each of them, and pays every business afterwards. The instruction still travels, exactly as it does in the other shape. The difference is that the money now has a stop in the middle, and that stop is somebody's own set of books.

Three things follow from that one fact, and the list carries the rest of the comparison: the party decides when each business is paid, it is holding money that belongs to somebody else in the meantime, and a business waiting to be paid holds a claim on it rather than cash. Very little else was needed. Not how large the party is, not what it charges, not how many businesses it serves, not what it is called. All three consequences come out of custody alone, and nothing else about the party touches any of them.

The money arriving that way is pooledAmounts belonging to several different parties arriving into one place together, so that working out how much of the total belongs to each of them becomes a separate step in its own right.. The word aggregator comes from that shape, and the word is also where the trouble starts. Aggregating is a description of the incoming shape. Whose the money is once it has arrived is the part a business actually needs, and the incoming shape says nothing about it. Charges for any of this are covered separately.

Why does a party that takes in money for a great many businesses exist at all?

A comparison usually skips this question, and the honest answer comes out of one division. Setu Payments Limited put 1,200 crore instructions through in the stated year and carried Rs 3,60,000 crore of value on them. The division sets the count underneath the value. Rs 3,60,000 crore shared across 1,200 crore separate instructions gives Rs 300.00/- for the average payment. Not a typical payment, not a middle payment, not most payments. Two figures is all the record carries, so the result is an average and nothing more than an average.

Now think about what a payment of that size means for the party on the receiving end. A very small business taking a few hundred payments has taken a very small amount of money in total. A business that small cannot sensibly be a memberA party admitted to a settlement arrangement in its own name, able to settle there directly rather than through somebody else. Which parties may be members, and on what conditions, is settled separately. of a settlement arrangement in its own right, cannot hold an account at the common placeThe one institution where the parties to a settlement arrangement each hold an account, so that a transfer between any two of them is a movement on a single set of books. Worked in full separately., and is not worth the checking that admitting it would require. So one party becomes the member and stands in for a great many businesses at once, and that, rather than convenience or software, is the entire reason the job exists.

Hold the value carried still and change the average, and the shape of the receiving side changes completely. Carry that same Rs 3,60,000 crore on instructions worth Rs 3,00,000/- apiece, and it takes 1.2 crore of them rather than 1,200 crore. The average is a thousand times larger and the count is a thousand times smaller, for the arithmetic reason that their product was held fixed. Parties of that size can be members themselves, so a receiving side made of that many fewer and correspondingly larger parties has far less need of anybody to stand in for it.

The average does not turn into a count of businesses. How many businesses those 1,200 crore instructions are spread across is not in the record. Dividing to invent a count would assume that every business takes the same number of payments, and nothing establishes that. The absence stays an absence.

Two reported figures do all the arithmetic, and a pen can check both of them. Setu Payments Limited reports 1,200 crore instructions in the stated year and Rs 3,60,000 crore carried on them. The second divided by the first gives Rs 300.00/-. The same Rs 3,60,000 crore, with Rs 3,00,000/- set as the average instead, gives a count of 1.2 crore instructions. Two divisions produce every figure in this comparison.

When is a business actually paid, and why is there a gap?

Mechanically, three things happen in order. The payer's side settles into the party that received the money. The amount owed to each business is worked out, net of anything sent backA payment already made being returned to the payer, which reduces what a business is owed before the business is paid anything. The route by which that happens is worked separately.. Then a transfer goes out to each business. There is a gap between the first step and the third, and the gap exists because the second step is real work that has to happen on a whole set of businesses at once rather than on one payment at a time.

The reason one transfer covers many payments rather than each payment arriving on its own is the same reason banks net between themselves, applied one layer higher up: when the average payment is Rs 300.00/-, sending a separate transfer for every single payment would be far more work than the payments carry. Take a business that has accumulated 400 payments valued at that average. The whole run comes to Rs 1,20,000.00/-. Passing each one along separately is 400 separate transfers instead of one, four hundred times the handling for exactly the same money moved. So the party does for the business precisely what a settlement arrangement does for banks.

The shape is familiar from a household. Nobody settles up with the milkman after every delivery. The deliveries accumulate, somebody adds them up, and one payment covers the lot, and everybody involved understands that the gap is the price of not doing the small thing four hundred times. How long a party may hold money before passing it on is another matter entirely. The Reserve Bank of India sets it, the condition moves, and the table below names it without a value.

Whose money is it during that gap, and where does it sit?

Be exact here. The word aggregator does its most damage at this point. Money sitting with a party during that gap is not the party's own money. The money arrived because a set of businesses made sales, it is owed onward to those businesses, and it is never the receiving party's for a single moment in between. A party can control the timing of a transfer and still have no entitlement whatever to what it is timing.

Where that money has to sit while it waits, and what may be done with it while it is sitting there, is not chosen by the party holding it. The Reserve Bank of India sets both, and both move. The reason that condition matters is blunt: what happens to a business's money if the party holding it fails turns on where that money was sitting. An authority sets the condition for exactly that reason, rather than leaving it to whatever an agreement happens to say.

The household version is a deposit with a shopkeeper for an order not yet delivered. Whether it comes back if the shop closes depends entirely on whether that deposit was kept apart from the shop's own till or mixed into it, and that is a question about where the money sat rather than about how the shopkeeper felt about the customer. Same question, different scale, and it is the only question in this part of the subject.

What does a business hold while it waits, and on whom?

A business owner should leave with one short sentence. In the gateway shape, a business is paid by the party that presented its instructions. Nothing of the business's ever went to the gateway, so the business never had a claim on the gateway at all. In the aggregator shape, a business that has taken payments and has not been paid holds a claim on the aggregator, and holding a claim is a different position from holding money.

Different how? A claim cannot be spent. A claim cannot be moved. The decision about when a claim turns into cash belongs to whoever is holding the money, not to the business holding the claim. A claim is a real thing and it is worth exactly what the party owing it is good for. Nobody enjoys reading that sentence, and it is the reason the conditions below exist at all.

So the test that survives every arrangement is this: who owes the money, rather than when it will be paid. The second question has an answer only if the first one does. Somebody who knows only that they will be paid soon knows nothing. Somebody who knows exactly which party is holding their money knows who to ask, what to ask, and whether the wait is a normal step in a process or a problem. Working out what a business is owed across many payments, less anything sent back, is ordinary practice and lets one transfer cover the lot. The claim exists for exactly as long as that work takes.

What has happened when a payer has paid and the business has no record of it?

There are two questions worth asking at that moment. The first is what state the instruction is in. The money has left the payer and has reached a party in the chain. The message telling the business about it has either not arrived or has not been matched to the order it belongs to. The money and the message travel separately, and this whole subject rests on that one fact. A payer who has paid while the business has no record of it is simply what that looks like when the message is the one running behind.

The second question is who the matter is raised with. Two parties can see two different halves of it. The payer's own bank can see that the money left and where it went. The business can see whether anything was matched to the orderThe record a business keeps of one sale, against which an arriving payment has to be matched before the business treats that sale as paid for. it is looking at. Between those two views the amount is locatable, and that is the whole of what anybody needs at that moment.

Here is the part that makes this bearable: an amount that has left a payer and has not been matched is somewhere specific rather than nowhere, and the routine matching of money that has moved against records of what it was for finds amounts in exactly that state as ordinary work. None of this puts a step in a payer's hands: a message running behind is not an act that anybody performed. Every step allowed at every stage of raising it is set by the Reserve Bank of India, the condition moves, and the table below carries the address instead of the value.

What does this comparison not settle?

Which arrangement suits a business is a separate question, and the custody question does not answer it. Neither shape stands above the other: a party that never touches the money and a party that takes it in are two arrangements, not a better one and a worse one. Two figures belonging to one payment system rank nothing.

Knowing the shape is more useful than a preference: a business that knows whether its money passes through a party's books knows who decides when it is paid, who it has a claim on while it waits, and what question to ask on the day a payment is late. A preference would go out of date the moment anything changed. The shape is a fact rather than a reading of a market, so knowing the shape does not go out of date.

Several subjects are leaned on here rather than taught again. Who signs a business up and stands behind its instructions is covered separately and assumed here. The three events inside a card payment are covered separately. The settlement arrangements underneath everything are covered separately. The verificationEstablishing who a party actually is before agreeing to deal with it. How that is done, and what has to be established, is settled separately and is not explained here. of a business before it may be signed up at all is covered separately: a party checks who it is dealing with, and how that check is made belongs to that separate subject.

How does somebody about to sign an agreement actually use this?

Who sets the conditions on holding money that belongs to somebody else?

Four conditions govern how a party may hold money belonging to somebody else, and no value for any of them is stated below. The Reserve Bank of India settles every one, every one moves, and a value written out would be wrong rather than merely stale on the morning it changed. So each appears below with its own label, with the authority printed inside the row, and with an empty value column that can be filled from the source in a single sitting.

The second row is the one to read first, and it earns the extra sentence: everything a business would want to know about what happens to its money if the party holding it fails turns on where that money was sitting. Not on what the agreement promised, not on the party's reputation, and not on how quickly it usually pays. On where the money sat. An authority sets the condition for that reason, rather than leaving it to whatever two parties happen to agree between themselves. Carrying away the fact that such a condition exists, together with the name of whoever fixes it, beats carrying away last season's figure.