Payments Training Hub
Payment gateway PAYMENT OPERATIONS STARTED LIVE 01 Payment gateway - primarily a technology service. ACTIVE 02 Payment aggregator - contrast, holds one large merchant account QUEUED 03 Reserve Bank of India regulation - clear line between the two models. QUEUED 04 Settlement flow differs in timing - who the merchant sees on the bank QUEUED 05 Choosing between the models - merchant size, volume and control needs. QUEUED 06 Business analyst documents - choice, the fee impact and the exit plan, QUEUED A payment gateway is primarily a technology service. Step 1 of 6 Payment gateway STARTED Payment gateway primarily a technology service. ACTIVE Payment aggregator contrast, holds one large merchant account QUEUED Reserve Bank of India regulation clear line between the two models. QUEUED Settlement flow differs in timing who the merchant sees on the bank QUEUED Choosing between the models merchant size, volume and control needs. QUEUED Business analyst documents choice, the fee impact and the exit plan, QUEUED A payment gateway is primarily a technology service.
Payment aggregator PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment gateway - primarily a technology service. DONE 02 Payment aggregator - contrast, holds one large merchant account ACTIVE 03 Reserve Bank of India regulation - clear line between the two models. QUEUED 04 Settlement flow differs in timing - who the merchant sees on the bank QUEUED 05 Choosing between the models - merchant size, volume and control needs. QUEUED 06 Business analyst documents - choice, the fee impact and the exit plan, QUEUED A payment aggregator, by contrast, holds one large merchant account with the acquirer and onboards many small merchants under it as sub merchants. Step 2 of 6 Payment aggregator IN PROGRESS Payment gateway primarily a technology service. DONE Payment aggregator contrast, holds one large merchant account ACTIVE Reserve Bank of India regulation clear line between the two models. QUEUED Settlement flow differs in timing who the merchant sees on the bank QUEUED Choosing between the models merchant size, volume and control needs. QUEUED Business analyst documents choice, the fee impact and the exit plan, QUEUED A payment aggregator, by contrast, holds one large merchant account with the acquirer and onboards many small merchants under it as sub merchants.
Reserve Bank of India regulation draws PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment gateway - primarily a technology service. DONE 02 Payment aggregator - contrast, holds one large merchant account DONE 03 Reserve Bank of India regulation - clear line between the two models. ACTIVE 04 Settlement flow differs in timing - who the merchant sees on the bank QUEUED 05 Choosing between the models - merchant size, volume and control needs. QUEUED 06 Business analyst documents - choice, the fee impact and the exit plan, QUEUED Reserve Bank of India regulation draws a clear line between the two models. Step 3 of 6 Reserve Bank of India regulation draws IN PROGRESS Payment gateway primarily a technology service. DONE Payment aggregator contrast, holds one large merchant account DONE Reserve Bank of India regulation clear line between the two models. ACTIVE Settlement flow differs in timing who the merchant sees on the bank QUEUED Choosing between the models merchant size, volume and control needs. QUEUED Business analyst documents choice, the fee impact and the exit plan, QUEUED Reserve Bank of India regulation draws a clear line between the two models.
Settlement flow differs in timing PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment gateway - primarily a technology service. DONE 02 Payment aggregator - contrast, holds one large merchant account DONE 03 Reserve Bank of India regulation - clear line between the two models. DONE 04 Settlement flow differs in timing - who the merchant sees on the bank ACTIVE 05 Choosing between the models - merchant size, volume and control needs. QUEUED 06 Business analyst documents - choice, the fee impact and the exit plan, QUEUED The settlement flow differs in timing and in who the merchant sees on the bank statement. Step 4 of 6 Settlement flow differs in timing IN PROGRESS Payment gateway primarily a technology service. DONE Payment aggregator contrast, holds one large merchant account DONE Reserve Bank of India regulation clear line between the two models. DONE Settlement flow differs in timing who the merchant sees on the bank ACTIVE Choosing between the models merchant size, volume and control needs. QUEUED Business analyst documents choice, the fee impact and the exit plan, QUEUED The settlement flow differs in timing and in who the merchant sees on the bank statement.
Choosing between the models depends PAYMENT OPERATIONS IN PROGRESS LIVE 01 Payment gateway - primarily a technology service. DONE 02 Payment aggregator - contrast, holds one large merchant account DONE 03 Reserve Bank of India regulation - clear line between the two models. DONE 04 Settlement flow differs in timing - who the merchant sees on the bank DONE 05 Choosing between the models - merchant size, volume and control needs. ACTIVE 06 Business analyst documents - choice, the fee impact and the exit plan, QUEUED Choosing between the models depends on merchant size, volume and control needs. Step 5 of 6 Choosing between the models depends IN PROGRESS Payment gateway primarily a technology service. DONE Payment aggregator contrast, holds one large merchant account DONE Reserve Bank of India regulation clear line between the two models. DONE Settlement flow differs in timing who the merchant sees on the bank DONE Choosing between the models merchant size, volume and control needs. ACTIVE Business analyst documents choice, the fee impact and the exit plan, QUEUED Choosing between the models depends on merchant size, volume and control needs.
Business analyst documents PAYMENT OPERATIONS COMPLETE LIVE 01 Payment gateway - primarily a technology service. DONE 02 Payment aggregator - contrast, holds one large merchant account DONE 03 Reserve Bank of India regulation - clear line between the two models. DONE 04 Settlement flow differs in timing - who the merchant sees on the bank DONE 05 Choosing between the models - merchant size, volume and control needs. DONE 06 Business analyst documents - choice, the fee impact and the exit plan, ACTIVE The business analyst documents the choice, the fee impact and the exit plan, so the merchant is not locked in without understanding the cost. Step 6 of 6 Business analyst documents COMPLETE Payment gateway primarily a technology service. DONE Payment aggregator contrast, holds one large merchant account DONE Reserve Bank of India regulation clear line between the two models. DONE Settlement flow differs in timing who the merchant sees on the bank DONE Choosing between the models merchant size, volume and control needs. DONE Business analyst documents choice, the fee impact and the exit plan, ACTIVE The business analyst documents the choice, the fee impact and the exit plan, so the merchant is not locked in without understanding the cost.

Key points of this lesson, in order.

0:00 / 3:29 Step 1 of 6

Payment Aggregators vs Gateways

Payment Gateway Architecture, Lesson 5 of 7, Narration 3:29, D09 Payment architecture and technology

SettlementAggregatorAcquirer

What you will learn

Your objective. By the end of this lesson, you will be able to explain payment aggregators vs gateways. A payment gateway is primarily a technology service.

Why it matters. A business analyst must check the authorization status of any aggregator on the Reserve Bank website before recommending it, because an unauthorized aggregator puts the merchant at risk of frozen settlements and regulatory action.

Chapter objective: Learner explains payment gateway architecture, including checkout, token vault, routing, retries, and settlement, and designs a gateway flow for an online merchant. Learner practises this skill on realistic banking cases, explaining the reasoning clearly and using correct terminology throughout the work.

Key learning points

  • Payment gateway
  • Payment aggregator
  • Reserve Bank of India regulation draws
  • Settlement flow differs in timing
  • Choosing between the models depends
  • Business analyst documents

Key terms

Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.

Aggregator: A payment provider that lets many small merchants accept card payments under the aggregator master merchant account, without each merchant holding its own acquirer contract.

Acquirer: A bank or licensed institution that processes card payments for merchants and receives transaction funds from card schemes on their behalf.

Banking architecture diagram showing Payment Aggregators vs Gateways.

Practise this lesson

Exercise

Map the payment in this lesson through the hub components.

Use the hub components and their order in this lesson.

  1. What to do. List each component the payment passes through, what it does, and what happens if it fails.

Correct result. The payment enters through a channel, passes the gateway, validation, fraud and sanctions checks, routing, and the ledger, then leaves through the right clearing system. A failure at any component stops or holds the payment, and the hub must record where it stopped.

Why. The hub is where most payment requirements live. If you cannot map a payment through it, you cannot specify, test or fix it.

Check your understanding

Practice question

Which of the following best describes payment aggregators vs gateways?

Takeaway and next step

What to remember

The business analyst documents the choice, the fee impact and the exit plan, so the merchant is not locked in without understanding the cost.

Send a payment through the hub and watch it pass each component named in this lesson.

Open the Payment Hub Architecture Simulator →

Builds on "Routing and Retries".

Transcript and full text

Show transcript

A payment gateway is primarily a technology service. It provides the payment page, the API, the token vault and the routing engine, but it does not hold the merchant money. The merchant signs a separate agreement with an acquiring bank, the acquirer opens a merchant account in the merchant name, and settlement goes directly from the acquirer to the merchant bank account. Examples of pure gateway providers include companies that offer gateway software to banks and large merchants. The merchant keeps control of the acquiring relationship and can change gateway providers without changing acquirers, although the integration work still takes time. A payment aggregator, by contrast, holds one large merchant account with the acquirer and onboards many small merchants under it as sub merchants. The aggregator collects payments on behalf of all its sub merchants, receives one bulk settlement from the acquirer, and then splits the money and pays each sub merchant. Razorpay, PayU, Cashfree and CCAvenue operate as aggregators in India, and a small business can start accepting payments within a day or two, because it does not need its own direct acquiring agreement. The trade off is dependence. The aggregator controls the settlement timing, the fee structure and the risk checks, and the merchant cannot easily move its acquiring history elsewhere. Reserve Bank of India regulation draws a clear line between the two models. Payment aggregators must obtain authorization from the Reserve Bank under the Payment and Settlement Systems Act, meet minimum net worth requirements, follow know your customer checks for each sub merchant, and hold customer funds in a nodal or escrow account until settlement. A pure technology gateway that does not touch merchant funds is not a payment aggregator, although it still must follow data security and outsourcing rules. A business analyst must check the authorization status of any aggregator on the Reserve Bank website before recommending it, because an unauthorized aggregator puts the merchant at risk of frozen settlements and regulatory action. The settlement flow differs in timing and in who the merchant sees on the bank statement. With a direct gateway and acquirer model, the acquirer settles the net amount, for example 98,000 rupees from 100,000 rupees of sales after a 2 percent fee, directly into the merchant current account with a reference such as ACQ SETT 12 NOV. With an aggregator model, the acquirer settles the bulk amount to the aggregator nodal account, and the aggregator then transfers each sub merchant share, often after deducting its own fee and holding a small reserve against refunds and chargebacks. The merchant bank statement then shows the aggregator name, not the acquirer, and the merchant must reconcile the aggregator settlement report against its own order records. Choosing between the models depends on merchant size, volume and control needs. A small retailer processing 5 lakh rupees per month benefits from an aggregator, because onboarding is fast, there is no separate acquirer negotiation, and the aggregator handles risk and settlement. A large enterprise processing 50 crore rupees per month usually prefers a direct acquirer relationship plus a gateway, because it can negotiate a lower merchant discount rate, control its own routing, and keep its settlement direct. Some large merchants use both, an aggregator for quick onboarding of a new brand, and a direct gateway for the main store. The business analyst documents the choice, the fee impact and the exit plan, so the merchant is not locked in without understanding the cost.

A payment gateway is primarily a technology service. It provides the payment page, the API, the token vault and the routing engine, but it does not hold the merchant money. The merchant signs a separate agreement with an acquiring bank, the acquirer opens a merchant account in the merchant name, and settlement goes directly from the acquirer to the merchant bank account. Examples of pure gateway providers include companies that offer gateway software to banks and large merchants. The merchant keeps control of the acquiring relationship and can change gateway providers without changing acquirers, although the integration work still takes time.

A payment aggregator, by contrast, holds one large merchant account with the acquirer and onboards many small merchants under it as sub merchants. The aggregator collects payments on behalf of all its sub merchants, receives one bulk settlement from the acquirer, and then splits the money and pays each sub merchant. Razorpay, PayU, Cashfree and CCAvenue operate as aggregators in India, and a small business can start accepting payments within a day or two, because it does not need its own direct acquiring agreement. The trade off is dependence. The aggregator controls the settlement timing, the fee structure and the risk checks, and the merchant cannot easily move its acquiring history elsewhere.

Reserve Bank of India regulation draws a clear line between the two models. Payment aggregators must obtain authorization from the Reserve Bank under the Payment and Settlement Systems Act, meet minimum net worth requirements, follow know your customer checks for each sub merchant, and hold customer funds in a nodal or escrow account until settlement. A pure technology gateway that does not touch merchant funds is not a payment aggregator, although it still must follow data security and outsourcing rules. A business analyst must check the authorization status of any aggregator on the Reserve Bank website before recommending it, because an unauthorized aggregator puts the merchant at risk of frozen settlements and regulatory action.

The settlement flow differs in timing and in who the merchant sees on the bank statement. With a direct gateway and acquirer model, the acquirer settles the net amount, for example 98,000 rupees from 100,000 rupees of sales after a 2 percent fee, directly into the merchant current account with a reference such as ACQ SETT 12 NOV. With an aggregator model, the acquirer settles the bulk amount to the aggregator nodal account, and the aggregator then transfers each sub merchant share, often after deducting its own fee and holding a small reserve against refunds and chargebacks. The merchant bank statement then shows the aggregator name, not the acquirer, and the merchant must reconcile the aggregator settlement report against its own order records.

Choosing between the models depends on merchant size, volume and control needs. A small retailer processing 5 lakh rupees per month benefits from an aggregator, because onboarding is fast, there is no separate acquirer negotiation, and the aggregator handles risk and settlement. A large enterprise processing 50 crore rupees per month usually prefers a direct acquirer relationship plus a gateway, because it can negotiate a lower merchant discount rate, control its own routing, and keep its settlement direct. Some large merchants use both, an aggregator for quick onboarding of a new brand, and a direct gateway for the main store. The business analyst documents the choice, the fee impact and the exit plan, so the merchant is not locked in without understanding the cost.

Full lesson text (all scenes)

Completing a lesson updates your progress dashboard on the homepage.

Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.