Merchant Payment: Meaning, Processing Flow, Fees and Settlement Explained
A customer's payment succeeding at checkout and a merchant actually receiving that money are two different events, days apart. Here's everything that happens in between.
Merchant payment is the transfer of funds from a customer's bank or card issuer into a business's merchant account after a transaction is authorised and settled. It's different from the customer payment itself: the customer's payment happens instantly at checkout, but the merchant payment — the money actually landing in the business's account — completes later, once the payment gateway, acquiring bank, and payment network have processed authorisation, clearing and settlement, typically within one to three working days.
A merchant account, a payment gateway, and one or more merchant outlets are the three building blocks that make this happen — each playing a distinct role between checkout and the funds reaching the business's bank account.
What Is Merchant Payment?
Merchant payment means the transfer of funds from a customer's bank or card issuer to a business's merchant account after authorization and settlement. In plain terms, it's how a business actually receives money after a customer completes a card or digital transaction — not the moment the customer clicks "pay," but the later point when that money is credited to the business.
A payment gateway or POS system, a merchant account, and the broader payment processing chain are all part of this system, with each entity playing a distinct role. RBI's own regulatory framework draws a specific line here: payment aggregators facilitate merchant connections with acquirers and handle the movement of funds, while payment gateways provide the technology infrastructure without handling funds directly. Knowing which one a provider actually is matters for understanding who's holding your money and when.
How Merchant Payment Processing Works
The flow begins the moment a customer chooses a payment method and ends when the transaction amount is settled to the merchant, according to the applicable settlement cycle.
Checkout
Customer pays via card, bank transfer, wallet or UPI.
Gateway
Encrypts and routes details to the acquirer/processor.
Authorization
Issuing bank approves or declines the transaction.
Clearing
Network/acquirer reconciles the approved transaction.
Settlement
Net amount credited to the merchant's account.
At settlement, the amount due to the merchant is credited to the designated bank account after processing fees, refunds, disputes, taxes and any other adjustments — which is why the amount that lands in the account is almost always less than the amount the customer paid.
Types of Merchant Payment Processing
Merchant payment processing can be classified by payment method, whether the customer is physically present, and the underlying rail. Most businesses use several types at once.
Card-based processing
Card-present (in-person): transactions at physical terminals, card readers or POS devices.
Card-not-present: payments where the card isn't physically presented — phone or online transactions.
Bank transfer-based processing
Payments move directly between bank accounts via net banking, UPI, ACH or wire transfer. Authorization is typically near-instant, though settlement timing still varies by system, and a gateway may still sit in the middle even though the rail is banking, not card networks.
Mobile payment processing
Payments accepted through mobile devices, QR codes, apps or softPOS. Availability, authentication and settlement speed depend on the specific method and provider.
Merchant Payment Fees Explained
What a merchant pays depends on the provider, payment method, transaction type, geography, risk profile and commercial agreement — not every fee below applies to every merchant.
Common merchant payment fee components.
| Fee Type | What it covers |
|---|---|
| Processing / transaction fee (MDR) | Percentage, fixed amount, or a combination charged per transaction. |
| Interchange and network costs | Costs tied to card-issuing banks and payment networks, where applicable. |
| Gateway or platform fee | Charges for the payment technology layer and related services. |
| Refund or dispute fee | Charges or adjustments tied to refunds and chargebacks. |
| Equipment or POS fee | Purchase, rental or maintenance of payment hardware. |
| Cross-border and currency-conversion costs | Additional charges on international payments. |
| Account or subscription fee | Recurring charges for account maintenance or reporting. |
Regulatory update — watch this space
UPI merchant transactions have carried zero MDR since a January 2020 mandate. On 4 August 2026, Parliament amended the Payment and Settlement Systems Act, 2007, removing the legal ban on charging UPI merchant fees — this doesn't impose a fee immediately, but it means the government can now notify an MDR for large-merchant UPI transactions in future. Small merchants and all consumer UPI transactions remain protected either way. Card MDR typically runs roughly 0.4-0.9% for debit/RuPay and 1.5%+ for credit cards, with wallets and EMI generally in the 1-2% range — always confirm the current, method-by-method fee schedule directly with your provider rather than assuming a flat rate.
Merchant Accounts: Meaning, Purpose and Role
A merchant account is what allows a business to accept card and digital payments in the first place. Transactions route through and are briefly held in this account while authorisation, risk checks, chargebacks and settlement processing complete, before the final, net amount reaches the business's actual bank account.
In practice, the merchant account acts as a control layer for payment risk and fund movement — it lets acquiring banks and processors manage fraud exposure, apply fees and reversals, and handle chargebacks before releasing funds. A merchant account is not the same thing as a business bank account: the bank account is where settled funds ultimately land, while the merchant account is the processing and control layer that gets them there.
KYC and KYB in merchant onboarding
Opening a merchant account isn't just a technical integration step — it's a regulated onboarding process. Under RBI's 2025 Payment Aggregator Directions, merchant KYC must run through the Central KYC Records Registry (CKYCR), with ongoing monitoring rather than a one-time check at signup. For a business itself (not just its individual signatories), that means both individual KYC and business-level KYB verification, since a merchant account is issued to a legal business entity, not a person.
Merchant Outlets in Multi-Store Businesses
A merchant outlet is a specific business location — physical or online — where a business sells and accepts payments. Multi-store and multi-branch businesses use outlets to separate payment activity by location while still operating under a single merchant account, avoiding the overhead of managing a separate account per store.
Every outlet connects to specific POS systems or payment terminals.
Transactions flow through the same merchant account for authorization and settlement.
Each outlet generates its own settlement report for reconciliation and audit.
This outlet-level mapping is what makes location-wise revenue tracking, reconciliation and audits manageable once a business has more than one point of sale.
Online vs Offline Merchant Payment: A Worked Example
Online — e-commerce
A customer places a ₹1,000 online order and pays by card. The gateway and processor handle authorization, and the transaction is recorded — but the merchant doesn't receive the funds immediately. At settlement, the amount is credited after deducting processing charges and any applicable taxes, so the full ₹1,000 never lands in the merchant account as-is.
Offline — POS or retail
A customer pays by card or UPI at a physical POS terminal. Transactions are batched — most merchants settle daily, though weekly cycles are also available — and settled together, with reporting that shows exactly which outlet generated each payment, which is critical for reconciliation across multi-store operations.
Common Mistakes to Avoid
Confusing a payment gateway with a payment aggregator.
One moves technology, the other moves funds — knowing which one you're dealing with changes your risk and compliance picture.
Assuming the full transaction amount settles.
Fees, refunds, disputes and taxes are deducted before the merchant is credited — budget against the net, not the gross.
Treating KYC as a one-time step.
RBI's current framework expects ongoing merchant monitoring, not just onboarding-day verification.
Running multiple outlets without outlet-level reporting.
Without it, reconciling revenue by location becomes a manual, error-prone exercise.
Ignoring settlement cycle differences across payment methods.
Card, UPI and bank-transfer rails don't all settle on the same timeline.
Best Practices
Get the full fee schedule in writing
broken down by payment method, not a single blended rate.
Reconcile against net settlement, not gross transaction value
to avoid cash-flow surprises.
Set up outlet-level reporting from day one
if you operate more than one location.
Keep KYC and KYB documentation current
not just complete at onboarding.
Confirm the settlement cycle for each payment method you accept
rather than assuming a single uniform timeline.
How AOPAY Fits
Merchant payment involves more moving parts than accepting a card — onboarding, collection, settlement visibility and, often, paying money back out. AOPAY's infrastructure covers this end to end:
A payment gateway covering UPI, cards, netbanking and wallets in one integration.
Connected banking for real-time visibility into settlement as it lands, instead of waiting on a batch report.
KYC and KYB verification built into merchant onboarding, aligned with current CKYCR requirements.
PayOut infrastructure for the other direction — refunds, settlements to sub-merchants, or paying your own vendors.
Dedicated vendor payment tools for businesses that need to manage outgoing payments to suppliers alongside incoming merchant payments.
Readiness Checklist
Key Takeaways
Merchant payment is the funds actually landing in a business's account — a separate, later event from the customer's payment at checkout.
The flow runs through checkout, gateway, authorization, clearing and settlement, with fees deducted before the merchant is credited.
A payment gateway moves technology; a payment aggregator moves funds — RBI regulates the two differently.
Merchant accounts require both KYC and KYB, with ongoing monitoring under RBI's current framework.
Merchant outlets let multi-location businesses track payments by site while operating under one account.
Settlement timing and fees vary by payment method — confirm both directly rather than assuming a single flat rate.
Setting up or re-evaluating your merchant payment stack?
See how AOPAY's payment gateway, connected banking, KYC/KYB and payout infrastructure fit together, in a live sandbox.