Payment Gateway vs Payment Aggregator: Where the Money Actually Sits

The short answer: a payment gateway is technology that carries a payment from your checkout to the banks and back. A payment aggregator is a business that collects your customers' money on your behalf and then pays it out to you. The gateway never holds your funds. The aggregator does, for a while, and that's why RBI regulates the two so differently.

In practice the line blurs, because most companies you'd sign with offer both: they run a gateway and they're an authorised aggregator. That's exactly why the difference is worth understanding. The role a company plays in your contract decides who checks your business, where your money sits before it reaches you, and who you hold responsible when something goes wrong.

RBI's Master Direction on the Regulation of Payment Aggregators, issued on 15 September 2025, defines both terms. A payment gateway is an entity that provides the technology infrastructure to route and process a payment "without any involvement in handling of funds". A payment aggregator facilitates payments from customers to merchants through the merchant's interface and "subsequently settles the collected funds to such merchants".

Everything else follows from those two phrases. Because a gateway never touches the money, the Direction states plainly that a gateway doesn't fall within its scope, although gateways are encouraged to adopt RBI's baseline technology recommendations. Because an aggregator does touch the money, a non-bank aggregator needs RBI authorisation, minimum net worth, an escrow account and a set of conduct rules. A bank doesn't need separate authorisation to carry on aggregator business.

Here are the practical differences, drawn from the 2025 Direction:

The difference is easiest to see with one order. Say a customer pays ₹5,000 by card on your website. In the aggregator model, the aggregator's bank receives the money and holds it in escrow until settlement. In the gateway-only model, your own acquiring bank receives the money, and the gateway is just the pipe between your checkout and that bank.

The first model suits businesses that want every payment method under one contract, with the aggregator doing the bank-side work. The second tends to appear where a merchant already has a direct acquiring relationship with a bank. Neither is better by default; what matters is that you know which one you're in.

Four practical consequences follow from where the money sits.

With an aggregator, money collected for you and not yet settled sits in an escrow account. The Direction says the balance in escrow can't fall below the amount collected and owed to merchants but not yet paid. The permitted outflows are listed too: payments to merchants, refunds to payers, transfers needed for certain outward flows, and the aggregator's own commission. Your settlement timeline is whatever your agreement says, and the Direction requires that agreement to be fair and to state the timelines clearly. So read the settlement clause before you sign.

An aggregator must do customer due diligence on you as a merchant, following RBI's KYC rules, and is to retrieve your KYC record from the central KYC registry with your consent. For small merchants (annual turnover up to ₹40 lakh, or annual export turnover up to ₹5 lakh), the Direction allows a lighter process: PAN or Form 60, a contact point verification and one officially valid document. Merchants onboarded up to 31 December 2025 have one year from the date of the Direction to meet these requirements; from 1 January 2026, new merchants are onboarded under them. A gateway-only provider isn't bound by these rules, although your acquiring bank will run its own checks.

Under the Direction, an aggregator must send refunds back to the original payment method unless the customer specifically asks for another mode that belongs to them. Refunds and reversals flow back through the escrow account unless you handle the refund directly and the customer knows it. None of this affects the customer's chargeback rights, which stay with their card issuer. Our guide to chargebacks covers what that means for you.

If a settlement is late, the party that owes it to you is the one holding the money: the aggregator in the first model, your bank in the second. A gateway that only routes payments can tell you what happened to a payment, but it can't settle what it never held. Aggregators must also publish their merchant policies, privacy policy and terms on their website, so you can read them before signing.

If you choose a gateway with your own acquiring bank, you take on work the aggregator would otherwise do. You'll need a merchant agreement with a bank for each way you accept payments, you'll deal with the bank directly on settlement and disputes, and you'll reconcile two parties: the gateway's records of what happened and the bank's records of what was paid. In return, you control the banking relationship and can negotiate it directly. For a business without a finance team, that trade rarely makes sense early on.

A rough guide, not a rule:

The Direction splits aggregators by where the payment happens, and one company can hold more than one kind of authorisation:

If you sell online and in a shop, or to customers outside India, check that your provider is authorised for each way you sell, not just one.

Company websites often say "payment gateway" for everything, because that's the term customers search for. Read the contract instead, and ask these questions:

A few things come up again and again when merchants compare providers:

Payment orchestration sits a layer above both. It connects your checkout to more than one provider and decides, payment by payment, which one to use. It doesn't change who handles the money: in Peneu's setup, each payment is collected and settled by the provider that processed it, and Peneu handles the routing, statuses and one consolidated record. If you want to see how that compares with contracting an aggregator directly, read Peneu vs payment aggregators. If you're wondering how a technology company fits into this regulated chain, read what a technology service provider is.