RuPay and Card Payment Networks: Digital Banking Guide (IIBF 2026)

Every debit or credit card swipe, tap, or online checkout in India rides on a card payment network — a rulebook-and-switch system that connects the cardholder's bank to the merchant's bank in seconds. For JAIIB and CAIIB Digital Banking candidates, RuPay and card payment networks is one of the highest-yield topics because examiners love testing the roles of issuer, acquirer, switch, and interchange in a single scenario question. This guide breaks the ecosystem down the way IIBF expects it — clearly, with the terminology examiners actually use, and with the settlement mechanics that trip up most candidates on exam day.

Understanding card networks also builds directly on your Overview of Digital Banking chapter, since card rails are one of the four pillars of India's digital payment stack alongside UPI, NEFT/RTGS, and prepaid instruments. Once you know how a card transaction actually moves money, several other Digital Banking topics — from ATM interoperability to POS deployment — start making a lot more sense.

💳 Issuing and Acquiring: The Two Sides of Every Card Transaction

Every card transaction has exactly two banks involved, and IIBF questions frequently test whether you can tell them apart under exam pressure. The issuing bank is the cardholder's bank — it issues the RuPay, Visa, or Mastercard card, underwrites the customer, sets the credit limit or links the savings account, and ultimately authorises or declines every transaction against that account. The acquiring bank is the merchant's bank — it onboards the merchant, deploys the POS terminal or payment gateway, and credits the merchant's account after the sale.

These two banks rarely have a direct relationship with each other. Instead, the card network sits between them, carrying the authorisation request from acquirer to issuer and the funds settlement back from issuer to acquirer. This is why a RuPay card issued by one public sector bank can be used seamlessly at a POS terminal deployed by an entirely different private bank — the network, not a bilateral arrangement, makes it possible. Candidates studying the POS (Point of Sale) chapter will recognise the acquirer's role immediately, since the acquiring bank is the one that owns and services the merchant's terminal.

💡 Exam Tip: If a question asks "whose bank declines the transaction," the answer is always the issuer — the issuer holds the account and runs the authorisation check, never the acquirer.

🔀 The Switch: How the Network Routes and Authorises

The "switch" is the technology layer operated by the card network — RuPay's switch is run by the National Payments Corporation of India (NPCI), while Visa and Mastercard operate their own global switches. When a customer taps a card at a POS terminal, the acquiring bank's system sends the transaction message to the network switch, which reads the card's BIN (Bank Identification Number) to identify the issuing bank, routes the authorisation request to that issuer, and relays the approve/decline response back to the merchant — typically within a couple of seconds.

The switch also performs risk and fraud screening in real time, applies network-level rules (such as domestic-only routing mandates), and generates the transaction logs used for reconciliation. Because RuPay's switch is domestic, transaction data for RuPay cards stays within India, which is a key reason RBI has pushed banks toward RuPay issuance under its data-localisation and payment-sovereignty objectives. This domestic routing angle is a favourite one-mark question in Digital Banking papers, so remember it as RuPay's core policy differentiator from Visa and Mastercard.

⚠️ Common Mistake: Candidates often confuse the "switch" with the "acquirer." The switch is the network's routing infrastructure; the acquirer is a bank that connects to the switch on the merchant's behalf.

⚖️ Interchange Fee and the Settlement Cycle

The interchange fee is the fee the acquiring bank pays to the issuing bank on every transaction, deducted before the merchant is credited. It compensates the issuer for underwriting the account, funding the transaction ahead of settlement, and absorbing fraud and credit risk. Interchange is set by the network (RuPay, Visa, or Mastercard) and varies by merchant category, card type (debit vs credit), and transaction channel (POS vs e-commerce vs contactless).

The Merchant Discount Rate (MDR) — what the merchant actually pays the acquirer — is built from interchange plus the network's own fee plus the acquirer's margin. For RuPay debit cards, RBI has kept MDR at zero on transactions below a specified value to encourage small-merchant digital adoption, while government reimburses banks separately for the cost. Settlement itself typically follows a T+1 or T+2 cycle: the network nets out all transactions between issuers and acquirers for the day and moves the net funds through designated settlement banks, so individual merchants and cardholders never see the gross flows — only the net credit or debit.

Getting the sequence right — authorisation, clearing, interchange deduction, then net settlement — is exactly what multi-mark CAIIB case-study questions test, so walk through each stage slowly rather than memorising it as one block.

📌 Remember: Interchange flows from acquirer to issuer; MDR flows from merchant to acquirer. They are related but not the same fee.

🇮🇳 RuPay's Role in India's Card Ecosystem

RuPay was launched by NPCI in 2012 as India's own domestic card network, built to reduce dependence on international networks and lower transaction costs for banks and merchants. Today RuPay cards are issued by nearly every scheduled bank, are mandatory for several government-linked schemes such as PM Jan Dhan Yojana accounts, and increasingly support UPI-linked credit lines through RuPay credit cards on UPI. RuPay's growth has been a deliberate policy push, and understanding why RBI and NPCI favour it over Visa and Mastercard for financial inclusion is essential exam context.

Where RuPay differs most from global networks is cost and control: because the switch, settlement, and data all sit within India, RuPay transactions avoid the cross-border fees and data-transfer dependencies that come with international networks. This makes RuPay the default choice for low-ticket, high-volume use cases like Jan Dhan debit cards, while Visa and Mastercard retain strength in premium and cross-border card segments. The table below summarises the comparison IIBF examiners test most often.

These policy-driven differences connect closely to related Digital Banking topics such as POS terminals in banking, where MDR structures play out at the merchant end, and Payment Aggregators and Gateways, which route online card transactions into the same issuer-acquirer-switch pipeline described above. Even feature-phone rails like UPI 123Pay exist partly because of the financial-inclusion push that also drove RuPay's rollout, so examiners like linking these threads together in scenario-based questions.

🛡️ Governance, Security and the Regulatory Framework

Card payment networks in India operate under RBI's oversight as Payment System Operators, with NPCI additionally regulated for its role running RuPay, IMPS, and UPI. Networks must comply with RBI's guidelines on data storage, tokenisation for card-not-present transactions, and mandatory two-factor authentication for online payments. Banks issuing cards must also follow RBI's card issuance and conduct norms, covering everything from unsolicited card issuance restrictions to grievance redressal timelines. You can review RBI's official payment systems framework directly at rbi.org.in for the latest circulars affecting card networks.

Banks also lean heavily on outsourced technology partners to run switch connectivity, fraud monitoring, and settlement reconciliation for card operations. If you want the compliance side of this vendor relationship — due diligence, business continuity, and RBI's outsourcing norms — it is covered in depth under IT outsourcing guidelines for banks, a CAIIB ITDB topic that pairs naturally with this chapter for candidates preparing both subjects together.

Security failures in the interchange and settlement chain — from BIN attacks to switch-level fraud — are exactly why RBI mandates real-time fraud monitoring at the network layer, not just at the issuer or acquirer level. Expect at least one MCQ each exam cycle testing which layer of the network stack is responsible for a given control.

🎯 Exam Strategy: Where Marks Are Won and Lost

Most candidates lose marks on this topic not because they don't know the terms, but because they mix up direction of fee flow and sequence of settlement. Before your exam, be able to draw the full chain from memory: cardholder → merchant → acquirer → switch → issuer → authorisation response → clearing → interchange deduction → net settlement. Practise this sequence with both a POS and an e-commerce example, since IIBF alternates between physical and online scenarios in its case studies.

Also revisit your Retail Banking - Digital Banking Class 12 notes for how card products fit into the broader retail banking product suite, since cross-linking topics is common in the 100-mark Digital Banking paper. For a full list of related posts, browse the Digital Banking tag hub on iibf.store.

✅ Conclusion: Lock In RuPay and Card Payment Networks Before Exam Day

RuPay and card payment networks form the backbone of India's card ecosystem, and IIBF consistently tests the issuer-acquirer-switch-interchange-settlement chain as a unit rather than as isolated facts. Once you can explain who gets paid what, in which order, and why RuPay's domestic switch matters for policy, this topic becomes one of the easiest scoring areas in Digital Banking. Reinforce it with timed practice before you sit the paper.

Ready to test yourself? Explore the JAIIB course plan or jump straight into chapter-wise mock questions to see where you stand.

🧠 Practice MCQs: RuPay and Card Payment Networks

Want chapter-wise mock tests with 100+ MCQs? Start practising free →