Two payment businesses may show the same checkout button and face different regulatory duties. The dividing line is not the user interface. It is who receives, pools, controls and settles customer payments for merchants.
That distinction affects authorisation, bank arrangements, merchant due diligence and the contracts signed before the first live transaction.
Quick Answer
A payment aggregator facilitates merchant acceptance and handles collection and settlement of customer money; non-bank aggregators fall within RBI’s authorisation framework. A payment gateway that only supplies transaction-processing technology may not itself require that PA authorisation. Mixed models, escrow control, merchant contracts and foreign ownership must be tested against current RBI rules.
1. Follow money, not the brand name
A gateway can transmit payment instructions and connect checkout systems without taking the merchant settlement role. An aggregator brings merchants onto a platform and receives money for later payout. A group may call its product a gateway while one entity actually performs aggregation.
Map each transaction from customer bank or instrument through acquiring bank, collection account and merchant payout. Record who can pause settlement, deduct charges, refund a customer or hold a reserve. These facts are more useful than a generic product description.
- Identify the merchant-onboarding entity.
- Show every collection and payout account.
- Name the party responsible for disputes.
2. Authorisation and escrow
RBI’s PA/PG framework distinguishes non-bank payment aggregators requiring authorisation from gateway technology providers. The framework and later circulars address escrow, merchant onboarding, security and settlement. Verify capital thresholds and transitional dates against the latest RBI text before using a number.
Escrow is not a general operating account. Money held for merchants has a defined purpose and reconciliation requirement. Involve the bank early so the proposed flow matches both contracts and technical configuration.
- Check the current authorisation category.
- Test permitted escrow debits and payout timing.
- Plan merchant due diligence and security evidence.
3. Contracts and merchant operations
A technology-only vendor may still face security and outsourcing duties imposed by its regulated clients. An aggregator has direct operational duties around onboarding, settlement, refunds, complaints and cyber controls. Customer-facing terms should make each entity’s role plain.
Merchant agreements should address prohibited goods, chargebacks, reserves, settlement cycles and support. A standard SaaS contract pasted into an aggregation business can leave responsibility for disputed funds unclear.
- Compare marketing with actual merchant terms.
- Document fraud and chargeback escalation.
- Audit payout changes and failed settlements.
4. Foreign ownership and future products
Foreign ownership adds a separate FDI/FEMA analysis. Review the Indian entity, ultimate owners and investment instrument before funds are remitted. Cross-border merchant payments may trigger another RBI category; a domestic PA plan cannot simply be reused.
Wallets and prepaid balances belong to the PPI framework. Adding stored value, lending or cross-border remittance to a gateway roadmap should prompt another classification before developers or sales staff promise the feature.
- Keep domestic and cross-border flows separate.
- Review the entry route for proposed ownership.
- Reassess authority when features change.
How to record the decision
A short decision note should explain why the chosen route fits the facts, which authority controls the point, what was checked and which assumptions remain open. For payment aggregator vs payment gateway, the note should also identify the responsible person, the next filing or approval event and the evidence that supports each conclusion.
Keep the note with board materials, agreements, portal acknowledgements and professional advice. This simple record helps founders answer investor, lender and regulator questions without reconstructing the reasoning months later. Update it whenever the business model, ownership, money flow, instrument terms or scheme status changes.
Documents to keep in one working file
The exact set depends on the transaction, but the working file should make the facts easy to test. Start with these records and add authority-specific forms or declarations where required:
- Diagram customer-to-merchant money movement.
- Identify merchant contracting and onboarding entity.
- Record settlement and refund authority.
- Compare the model with current RBI directions.
- Check foreign ownership and FEMA.
Use dated versions and keep a clear approval trail. A missing email, valuation input or portal receipt can become a material due-diligence issue even when the commercial decision itself was sound.
Decision table
Use the facts of the proposed transaction to test each row before choosing a route.
| Question | Payment aggregator | Payment gateway |
|---|---|---|
| Handles merchant money? | Collects and settles under PA framework | May only process messages |
| Merchant onboarding? | Direct operating responsibility | May serve an authorised PA or bank |
| RBI authorisation? | Non-bank PA framework applies | Tech-only status needs fact review |
| Escrow? | Central to fund flow | Not a substitute for PA escrow |
Practical checklist
Work through these steps using dated documents, not assumptions made in a pitch deck.
- Diagram customer-to-merchant money movement.
- Identify merchant contracting and onboarding entity.
- Record settlement and refund authority.
- Compare the model with current RBI directions.
- Check foreign ownership and FEMA.
- Prepare bank, security and grievance records.
Mistakes that create avoidable delay
The following shortcuts frequently create avoidable legal or filing work later.
- Calling a fund-handling business a gateway to avoid authorisation.
- Assuming a bank escrow contract itself grants RBI authority.
- Quoting old capital or application deadlines.
When professional review is useful
A fact-specific review should test the chosen route, evidence and filing sequence before money or customer commitments make a correction expensive.
For a fact-specific review, share the proposed activity, ownership, funding instrument and present stage with Sunny G And Co. at contact@cssunnygupta.com. The scope and professional fee should be agreed only after the facts and required filings are clear.
Related service paths
If the issue involves actual filings or structuring, these service pages describe the relevant scope of work. They do not change the eligibility and approval tests explained above; the right route still depends on the company’s documents and intended activity.
Official sources and last review
This article was last reviewed on 15 September 2026. Rules, portal status and filing practices can change, so check the current authority before acting.
