Payments

<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/what-dormant-credit-cards-really-cost-indian-card-issuers_2_2000x1000-copy.webp" alt="What Dormant Credit Cards Really Cost Indian Issuers (2026)" title="" id="xscjjzdn2" width="100%" height="347">Most card issuers track dormancy as a percentage. Fewer track it as a rupee figure. That gap matters, because a dormancy rate sitting in a monthly report doesn't get anyone's attention — a cost sitting on the P&amp;L does.&nbsp;If your program has issued cards that customers aren't using, this is the actual math behind why that's a bigger problem than it looks.&nbsp;<h2 class="heading-node" id="bidfb6mad" style="text-align: left;">Dormancy Is Usually Treated as an Ops Metric - It's Actually a Program Design Problem&nbsp;</h2>A dormant card gets logged, monitored for compliance purposes, and mostly forgotten until someone asks why activation numbers look weak in a review. By then, the cost has already been incurred - it just hasn't been counted properly.&nbsp;<h2 class="heading-node" id="c3gmjrmoi" style="text-align: left;">Why Cards Go Dormant in the First Place?&nbsp;</h2>Briefly, before the cost breakdown - dormancy usually traces back to one of a few things:&nbsp;<ul class="list-node" id="d5qhstwi4"><li>Friction in the activation process itself (app downloads, PIN generation, physical activation steps)&nbsp;</li><li>No meaningful nudge or incentive in the first few days after the card is issued&nbsp;</li><li>A card issued as an add-on or eligibility-based offer, without genuine customer intent to use it&nbsp;</li><li>No visibility for the program team into where a customer drops off between issuance and first transaction&nbsp;</li></ul>The fix for each of these is a separate conversation. This piece is about what happens if none of them get addressed.&nbsp;<h2 class="heading-node" id="p0lsabxob" style="text-align: left;">The Real Cost Breakdown&nbsp;&nbsp;</h2>1. Issuance Cost That's Already Sunk&nbsp;Every card issued carries a cost - KYC verification, card manufacturing, personalization, and dispatch logistics. This cost is incurred the moment the card ships, regardless of whether it's ever activated. A card that never gets used means that cost never gets recovered through any downstream revenue.&nbsp;&nbsp;2. Blocked Credit Limit&nbsp;A sanctioned credit limit sits allocated against a dormant account, even though it's generating no interest income and no transaction volume. At a portfolio level, across thousands of dormant cards, that's real capital sitting idle that could otherwise be underwritten to customers who would actually use it.&nbsp;&nbsp;3. Lost Interchange and Fee Income&nbsp;The entire card revenue model - interchange income, EMI conversion fees, annual fees in some cases - depends on the card being used. A dormant card breaks that assumption completely. It's not a smaller version of revenue; it's zero.&nbsp;4. Ongoing Compliance and Servicing Overhead&nbsp;Dormant accounts don't disappear from the books. They still require monitoring, periodic KYC refreshes, and statement generation in many cases - costs that continue whether or not the customer ever transacts.&nbsp;&nbsp;5. Opportunity Cost&nbsp;Every dormant card represents an issuance slot, underwriting decision, and onboarding effort that could have gone toward a customer who was going to activate and use the card. At scale, this compounds.&nbsp;<h2 class="heading-node" id="e8i1gvgm8" style="text-align: left;">A Simple Way to See the Scale of It&nbsp;</h2>Take a program issuing 1 lakh cards a year, with a dormancy rate of 25% - not unusual for programs without strong early-activation triggers. That's 25,000 cards where issuance cost, blocked limit, and servicing overhead are incurred with no offsetting revenue. Multiply that by even a conservative per-card cost estimate, and the number moves from "a metric on a dashboard" to a figure that belongs in a board discussion.&nbsp;<h2 class="heading-node" id="no5gjiny6" style="text-align: left;">What “Good" Looks Like?</h2>Well-run card programs tend to share a few traits when it comes to activation and dormancy management:&nbsp;<ul class="list-node" id="i8jumbmg5"><li>Activation is tracked and acted on in near real time, not reviewed monthly after the fact&nbsp;</li><li>There's a structured first-30-days journey for every new cardholder, not just a generic welcome message&nbsp;</li><li>Program teams can see exactly where in the funnel - dispatch, activation, first transaction - customers are dropping off&nbsp;</li><li>Re-engagement triggers kick in well before an account crosses into full dormancy, not after.</li></ul><h2 class="heading-node" id="xkabk432t" style="text-align: left;">What Actually Moves the Needle&nbsp;</h2>Fixing dormancy at scale usually comes down to a few structural levers, not one-off campaigns:&nbsp;<ul class="list-node" id="jbbmfsvox"><li>Real-time activation triggers instead of static, delayed reporting&nbsp;</li><li>First-transaction incentives built into the program design, not bolted on later&nbsp;</li><li>Full visibility into the onboarding-to-activation funnel for program managers, not just aggregate percentages&nbsp;</li><li>Proactive re-engagement for at-risk accounts before they become fully dormant&nbsp;</li></ul>These aren't marketing tactics - they're program infrastructure decisions, and they tend to separate issuers who treat dormancy as an afterthought from issuers who treat it as a P&amp;L line they actively manage.&nbsp;Dormancy isn't a customer behavior problem - it's a visibility and program design problem, and most issuers only catch it after the cost has already been incurred. <a class="link" href="https://m2pfintech.com/credit-cards/" target="_blank">M2P's Credit Card Management System</a> gives program teams real-time activation tracking and lifecycle triggers built in, so dormancy gets caught and addressed early, not discovered in a quarterly review. <a class="link" href="https://m2pfintech.com/contact-us/?utm_source=M2PBlogs&amp;utm_medium=social&amp;utm_campaign=Dormancy_CC_Blog" target="_blank">Talk to us today</a> and see how issuers are reducing dormancy with real-time triggers.<h2 class="heading-node" id="j2svgj812" style="text-align: left;">Frequently Asked Questions&nbsp;</h2><ul class="list-node" id="or763dhrb"><li>What counts as a dormant credit card?&nbsp; Definitions vary slightly by issuer, but most programs treat a card as dormant if it hasn't recorded a single transaction within a defined window after issuance - commonly 90 to 180 days - or if an account that was once active hasn't transacted in 12 months. The exact threshold matters less than having one at all: without a clear definition, dormancy can't be tracked, and what isn't tracked doesn't get fixed.&nbsp;</li></ul><ul class="list-node" id="kvsx08pew"><li>Isn't dormancy just a marketing or engagement problem?&nbsp; It starts there, but it doesn't stay there. Every dormant card carries issuance cost that's already been spent, a credit limit that's sitting idle instead of earning interest income, and zero interchange or fee revenue. By the time someone in engagement or marketing notices low activation, the cost has usually already hit the P&amp;L — it just hasn't been labeled as a cost.&nbsp;</li></ul><ul class="list-node" id="7uvspuces"><li>Why does blocked credit limit matter if the money was never actually lent out?&nbsp; It's not a cash loss the way issuance cost is - it's an opportunity cost. That sanctioned limit is capital the issuer has committed and could have extended to a customer who'd actually use it. At small scale it's negligible; across a portfolio of dormant cards, it becomes a meaningful drag on how efficiently the program deploys capital.&nbsp;</li></ul><ul class="list-node" id="gjgf0crll"><li>Does dormancy cost anything beyond issuance, blocked capital, and lost fee income?&nbsp; Yes - dormant accounts still require ongoing servicing: periodic KYC refreshes, statement generation, and compliance monitoring, all of which continue whether or not the customer ever transacts. It's a quieter cost than the other three, but it doesn't stop just because the account is inactive.&nbsp;</li></ul><ul class="list-node" id="lqvqnj3jf"><li>Where does dormancy typically start?&nbsp; Almost always in the first 30 days - friction in activation (app downloads, PIN setup, physical activation steps), no meaningful nudge right after issuance, or cards issued on eligibility rather than genuine intent to use. Programs that lose visibility into this early window tend to discover the problem only once it shows up as a dormancy percentage in a monthly report.&nbsp;</li></ul><ul class="list-node" id="1fj4od46w"><li>What actually reduces dormancy -&nbsp; beyond a one-off reactivation campaign?&nbsp; Structural fixes, not campaigns: real-time activation triggers instead of delayed reporting, first-transaction incentives designed into the program from day one, full visibility into where customers drop off between dispatch and first transaction, and re-engagement that kicks in before an account crosses into full dormancy - not after.&nbsp;</li></ul><ul class="list-node" id="nylil5e70"><li>How do we put a number on what this is costing our own portfolio?&nbsp; That's exactly what a portfolio-level calculator is for - plug in your issuance volume, dormancy rate, and a few cost assumptions, and it turns the abstract percentage into your program's actual annual number.&nbsp;&nbsp;</li></ul>

What Dormant Credit Cards Really Cost Indian Card Issuers

<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/why-forex-cards-are-becoming-a-must-have-for-banks-serving-global-customers_2_2000x1000.webp" alt="Why Every Bank Needs a Forex Card Strategy in 2026" title="" id="sckcm6aru" width="100%" height="347">More people are traveling, studying, and working abroad than ever before. And every time someone crosses a border, they need a simple way to spend money in a different currency. This is exactly the gap a forex card fills.&nbsp;For banks, this isn't just a nice-to-have product anymore. It's becoming a core part of serving customers who live global lives. Having worked with banks and fintechs on building this exact stack, we've seen firsthand where forex card programs succeed and where they stumble - and most of the time, it comes down to the platform behind the card, not the card itself. In this blog, we'll look at why forex cards matter, how they work, and what banks need to know about forex card issuance and building a strong forex card platform.&nbsp;<h2 class="heading-node" id="erkrjmieq" style="text-align: left;">What Is a Forex Card?&nbsp;</h2>A <a class="link" href="https://m2pfintech.com/blog/forex-cards-international-travel-made-effortless/" target="_blank">forex card</a> is a prepaid card loaded with foreign currency, which customers can use to spend, withdraw cash, or make online payments while traveling abroad. Unlike a regular debit or credit card, a forex card locks in the exchange rate at the time of loading, protecting customers from daily currency fluctuations.&nbsp;Many modern <a class="link" href="https://m2pfintech.com/blog/global-payments-simplified-m2ps-turnkey-platform-for-forex-cards/" target="_blank">forex cards</a> are also multi-currency prepaid cards, meaning customers can load multiple currencies onto a single card and switch between them depending on which country they're in.&nbsp;<h2 class="heading-node" id="jvh0qbpvk" style="text-align: left;">Why Forex Cards Are Becoming Essential for Banks?</h2>1. Outbound travel is growing fast&nbsp;More people are traveling internationally for leisure, business, and education every year. Every one of these travelers needs a way to manage foreign currency, and banks that don't offer a forex product are missing this opportunity entirely.&nbsp;2. Customers expect it as part of their banking relationship&nbsp;Today's customers don't want to visit a separate forex counter or use a third-party app to convert currency. They expect their bank to offer this service directly, right alongside their savings account and credit card.&nbsp;3. It strengthens cross border payments capabilities&nbsp;Forex cards are a key part of a bank's broader cross border payments strategy. They give customers a reliable way to spend abroad without relying on international transaction fees on regular debit cards, which are often expensive and unpredictable.&nbsp;4. It opens up a new revenue stream&nbsp;Forex cards allow banks to earn through currency markup, loading fees, and reload charges - all while offering a genuinely useful product to customers.&nbsp;5. It builds loyalty among high-value customers&nbsp;Frequent travelers, students studying abroad, and business professionals tend to be high-value customers. Offering them a smooth forex card experience keeps them within the bank's ecosystem instead of switching to a fintech competitor.&nbsp;<h2 class="heading-node" id="oz2j6i08y" style="text-align: left;">Forex Card vs Regular Debit or Credit Card Abroad&nbsp;</h2>Many customers still use their regular debit or credit card while traveling, not realizing how much extra they're paying. Here's the difference:&nbsp;<ul class="list-node" id="rhjnv3e5n"><li>Exchange rate: Forex cards lock the rate at the time of loading. Debit and credit cards apply the rate at the time of transaction, which can vary and often includes a markup.&nbsp;</li><li>Foreign transaction fees: Regular cards usually charge 2-4% on every international transaction. Forex cards are designed specifically to avoid this.&nbsp;</li><li>Budget control: Since forex cards are prepaid, customers only spend what they've loaded, avoiding surprise charges or overspending.&nbsp;</li><li>Safety: If a forex card is lost or stolen, the loss is limited to the loaded balance, unlike a credit card linked to a larger credit limit.&nbsp;</li></ul>This is why more customers are actively looking for forex cards instead of relying on their regular banking cards while abroad.&nbsp;<h2 class="heading-node" id="ox574nefn" style="text-align: left;">What Banks Need to Know About Forex Card Issuance&nbsp;</h2>Launching a forex card program isn't just about adding a new product to the catalog. Banks need the right forex card platform to make it work smoothly. Based on programs we've helped banks launch, here's what actually determines whether a forex card program takes off or stalls:&nbsp;1. Multi-currency support&nbsp;Customers should be able to load and hold multiple currencies on a single multi-currency prepaid card, switching automatically based on where they're spending.&nbsp;2. Regulatory compliance&nbsp;Forex card issuance involves RBI guidelines (or the relevant regulator in the bank's country), FEMA compliance, and reporting requirements. A strong forex card platform should have these built in.&nbsp;3. Real-time rate locking&nbsp;Customers expect transparent, real-time exchange rates when they load their card. Delayed or unclear pricing leads to poor customer experience and complaints.&nbsp;4. Seamless reload and top-up options&nbsp;Customers should be able to reload their forex card easily through net banking, UPI, or the bank's app - without needing to visit a branch.&nbsp;5. Strong fraud and security controls&nbsp;Since forex cards are used internationally, banks need robust fraud detection, card freezing options, and instant alerts to protect customers while they're abroad.&nbsp;6. Easy integration with existing banking apps&nbsp;A modern forex card platform should integrate directly into the bank's existing mobile app, so customers don't need to download or manage a separate application.&nbsp;In our experience, the banks that get this right usually aren't building all six of these from scratch - they're partnering with a forex card platform that already handles compliance, rate-locking, and fraud controls, so the bank's team can focus on the customer experience layer instead.&nbsp;<h2 class="heading-node" id="zx8oxbu30" style="text-align: left;">Who Needs Forex Cards the Most?&nbsp;</h2><ul class="list-node" id="y15i02s02"><li>International travelers: For holidays, business trips, and family visits abroad.&nbsp;</li><li>Students studying overseas: Who need a reliable way to manage tuition-related spends and daily expenses in a foreign currency.&nbsp;</li><li>Business professionals: Who travel frequently and need predictable, trackable forex spending.&nbsp;</li><li>NRIs and expats: Who manage money across multiple countries and currencies regularly.&nbsp;</li></ul>Each of these segments represents a meaningful, recurring revenue opportunity for banks that get their forex card strategy right.&nbsp;<h2 class="heading-node" id="g3y31vex0" style="text-align: left;">Final Thoughts&nbsp;</h2>As more customers live, work, study, and travel across borders, forex cards are quickly becoming a core banking product rather than a niche add-on. For banks, offering a well-built multi-currency prepaid card isn't just about convenience - it's about staying relevant to a customer base that increasingly thinks and spends globally.&nbsp;Banks that invest in the right forex card platform and get forex card issuance right will be better positioned to serve these customers and strengthen their overall cross border payments offering.&nbsp;If your bank is exploring how to launch or upgrade a forex card program, <a class="link" href="https://m2pfintech.com/cross-border-payments/" target="_blank">M2P's forex card platform</a> handles multi-currency support, compliance, and real-time rate locking out of the box - so you can focus on the customer experience. <a class="link" href="https://m2pfintech.com/contact-us/?utm_source=M2PBlogs&amp;utm_medium=social&amp;utm_campaign=Forex_Cards_Blog" target="_blank">Talk to our team</a> to see how a modern card stack can fit into your roadmap.&nbsp;<h3 class="heading-node" id="r7vcrla4y">Frequently Asked Questions</h3><ul class="list-node" id="smd4shvbg"><li>What is the difference between a forex card and a multi-currency prepaid card? A forex card is typically loaded with one foreign currency, while a multi-currency prepaid card lets customers hold and switch between several currencies on the same card. Most modern forex cards now come with multi-currency capability built in.</li><li>What compliance requirements apply to forex card issuance? Forex card issuance is subject to regulatory guidelines such as RBI norms and FEMA compliance (in India), along with reporting requirements that vary by country. A strong forex card platform builds these checks into the issuance flow so banks don't have to manage them manually.</li><li>Can customers reload a forex card without visiting a branch? With a well-built forex card platform, yes. Customers should be able to reload via net banking, UPI, or directly through the bank's mobile app.</li><li>Who benefits the most from a forex card? International travelers, students studying abroad, frequently traveling business professionals, and NRIs/expats managing money across countries all benefit from the predictability and cost savings a forex card offers.</li><li>Should banks build a forex card program in-house or partner with a platform? Most banks find it faster and more reliable to partner with a forex card platform that already handles compliance, rate-locking, and fraud controls - letting the bank's team focus on customer experience and app integration instead of building infrastructure from scratch.</li></ul>

Why Forex Cards Are Becoming a Must-Have for Banks Serving Global Customers

<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/the-global-acquiring-landscape-in-2026_2_2000x1000.webp" alt="2026's Acquiring Wars: Who Consolidates, Who Disrupts, Who Gets Left Behind" title="" id="le0sddrbp" width="100%" height="362"><a class="link" href="https://m2pfintech.com/merchant-acquiring-solutions/?utm_source=blg&amp;utm_medium=mms&amp;utm_campaign=global-acquiring" target="_blank">Merchant Acquiring</a> in 2026 looks almost nothing like it did a decade ago, and arguably, less like it did even three years ago. What was once a relatively stable, bank-dominated business defined by processing volumes and interchange economics has become one of the most contested, fast-moving segments in financial services. Three forces are reshaping it simultaneously: consolidation among the traditional acquiring giants, relentless fintech disruption from platform-native players, and a bank response that is still very much being written.&nbsp;Understanding where the industry stands today, and where the pressure points lie, matters for anyone with a stake in merchant acquiring: banks, NBFCs, PSPs, and the infrastructure providers powering them all.<h1 class="heading-node" id="mpwy57jzk" style="text-align: left;">The Consolidation Wave: Scale Becomes the Only Defense&nbsp;</h1>The last several years have seen an unmistakable pattern among the traditional acquiring giants viz Fiserv, FIS, Global Payments, M2P Fintech, Nexi, Worldline, each of them navigating mergers, divestitures, and restructuring at a pace rarely seen in payments before. Global Payments' acquisition of Worldpay, M2P’s acquisition of Finflux(<a class="link" href="https://m2pfintech.com/core-lending-suite/?utm_source=blg&amp;utm_medium=mms&amp;utm_campaign=global-acquiring" target="_blank">Lending</a>) and Madstreet Den(AI capabilities), FIS's parallel moves to reshape its merchant business, and Worldline's continued portfolio rationalization across Europe are not isolated events. They reflect a single, shared realization across the legacy acquiring industry: scale is no longer optional.&nbsp;<h1 class="heading-node" id="8e1ao16bz" style="text-align: left;">Why has scale become existential?</h1><h3 class="heading-node" id="mw6rzw5zi" style="text-align: left;">A few structural reasons:&nbsp;</h3><h3 class="heading-node" id="y8ft3039x" style="text-align: left;">Technology investment costs have outpaced what mid-sized acquirers can sustain</h3>Building and maintaining a modern, omnichannel, API-first acquiring platform, one that supports cards, QR, wallets, BNPL, SoftPOS, and real-time settlement across multiple geographies requires sustained capital investment that only the largest players, or the most tightly focused specialists, can justify. Consolidation lets legacy acquirers pool R&amp;D spend across a larger merchant and transaction base.&nbsp;<h3 class="heading-node" id="lpxx3gxwi" style="text-align: left;">Interchange and MDR compression continues globally</h3>As regulators in market after market, from the EU's interchange fee caps to India's zero-MDR debit card/UPI policies to various price-cap discussions across the Middle East, squeeze the economics of card acceptance, acquirers need volume to make unit economics work. Smaller, sub-scale acquirers are increasingly unable to compete on price while maintaining margin, making them natural acquisition targets.&nbsp;<h3 class="heading-node" id="xqyxye5od" style="text-align: left;">Cross-border merchant demand rewards global reach</h3>As e-commerce merchants expand across markets, they increasingly prefer a single acquiring/PSP relationship that can operate across geographies rather than stitching together local acquirers market by market. This has driven consolidation not just for cost reasons, but to build the geographic breadth merchants are demanding.&nbsp;<h3 class="heading-node" id="qplb797av" style="text-align: left;">Private equity has accelerated the cycle</h3>Much of the consolidation activity in acquiring and payments processing over the past few years has been PE-driven, rolling up regional processors, ISOs (independent sales organizations), and payment facilitators into larger platforms that can then be sold, merged, or taken public at a premium. This financial engineering layer has added velocity to a consolidation trend that was already structurally inevitable.&nbsp;The result: by 2026, a handful of scaled global acquirers control an outsized share of processing volume, while the long tail of regional and niche acquirers faces a stark choice, either to get acquired, or specialize deeply into a defensible niche, or partner into a larger platform's infrastructure to stay relevant.&nbsp;<h1 class="heading-node" id="1gwi5uizj" style="text-align: left;">Fintech Disruption: The Platform Model Keeps Winning&nbsp;</h1>While the legacy acquiring industry consolidates around scale, an entirely different competitive logic has been playing out at the other end of the market, and it's the one reshaping merchant expectations everywhere.&nbsp;Adyen, Stripe, and Checkout built their businesses not around processing volume alone, but around a fundamentally different architecture: single-platform, API-first, globally consistent acquiring that treats every merchant, from a two-person e-commerce startup to a multinational retailer, as a product user rather than a processing account. This platform model has three characteristics that continue to disrupt the traditional acquiring business in 2026:&nbsp;<h3 class="heading-node" id="5i5wvqmfp" style="text-align: left;">Unified commerce as the default, not the upsell</h3>Merchants no longer think of "online payments" and "in-store payments" as separate systems needing separate integrations. Adyen's unified commerce platform and Stripe's expansion into Terminal and Tap to Pay have made omnichannel acceptance table stakes. Acquirers still selling online and offline as separate products are increasingly at a disadvantage.&nbsp;<h3 class="heading-node" id="3h2v8he8u" style="text-align: left;">Embedded acquiring has exploded</h3>Software platforms, marketplaces, and vertical SaaS companies, from POS software providers to logistics platforms to B2B marketplaces, increasingly want to embed payment acceptance directly into their own product, monetizing payments as a feature rather than routing merchants to a separate acquirer relationship. Stripe Connect, Adyen for Platforms, and a growing ecosystem of embedded acquiring infrastructure providers have made this a mainstream go-to-market model rather than a niche one. This directly threatens the traditional acquirer-merchant sales relationship, because the software platform, not the bank or acquirer, now owns the merchant relationship.&nbsp;<h3 class="heading-node" id="b0vpndft9" style="text-align: left;">Regional fintech acquirers have matured into serious competitors</h3>In India, Pine Labs, Razorpay, Cashfree, PayU, and Innoviti have moved well beyond payment gateways into full acquiring and merchant management propositions, same-day settlement, integrated lending, and value-added services bundled directly into the merchant dashboard. In the Middle East, Geidea, PayTabs, Telr, and Network International have driven a similar shift, often moving faster than the banks they were originally meant to complement. These regional players increasingly compete directly with banks for SME and MSME acquiring relationships, a segment banks have historically underserved and fintechs have aggressively targeted.&nbsp;The net effect of fintech disruption isn't just competitive pressure on pricing, it's a redefinition of what "good" looks like in merchant acquiring. Same-day settlement, real-time dashboards, self-service onboarding, and API-first integration are no longer differentiators; they're baseline expectations set by fintech-native acquirers, and every bank and legacy acquirer is now measured against that baseline whether they like it or not.&nbsp;<h1 class="heading-node" id="n1dm2g1w0" style="text-align: left;">The Squeeze in the Middle: Where Consolidation and Disruption Collide&nbsp;</h1>The genuinely difficult position in 2026 belongs to the players caught between these two forces, regional banks and mid-sized acquirers who are too small to achieve the scale economics of a Fiserv or Global Payments, but too structurally slow to match the product velocity of a Stripe or a Razorpay.&nbsp;This "squeezed middle" faces a familiar set of symptoms: merchant attrition to fintech competitors on price and experience, margin compression from interchange regulation, rising technology maintenance costs on aging infrastructure, and increasing difficulty attracting the engineering talent needed to modernize. For many of these players, the strategic question isn't whether to change, it's how fast they can change before the gap becomes unrecoverable.&nbsp;<h1 class="heading-node" id="6l1291tyz" style="text-align: left;">The Bank Response: Emerging Strategies&nbsp;</h1>Banks are not standing still in the face of this pressure, but their responses in 2026 are diverging into a few distinct strategic postures.&nbsp;<h2 class="heading-node" id="0dnf5djdc" style="text-align: left;">Partner and Modernize&nbsp;</h2>The most common and pragmatic response has been for banks to partner with modern Merchant Management System (MMS) providers to modernize their acquiring stack without undertaking a multi-year, high-risk internal rebuild. This lets banks retain the merchant relationship, the settlement account, and regulatory ownership, while offloading the technology burden viz onboarding automation, omnichannel acceptance, real-time settlement, risk and dispute management to a specialist partner. This is, in effect, banks borrowing the platform economics that made Adyen and Stripe disruptive in the first place, and applying them inside a bank-owned, regulated wrapper.&nbsp;<h6 class="heading-node" id="v9gu6uo3s" style="text-align: left;"><a class="link" href="https://m2pfintech.com/blog/why-banks-are-rethinking-in-house-merchant-acquiring-stacks-and-turning-to-mms-partner/?utm_source=blg&amp;utm_medium=mms&amp;utm_campaign=global-acquiring" target="_blank">Why Banks are Rethinking In-House Merchant Acquiring Stacks and turning to MMS Partner</a></h6><h2 class="heading-node" id="ketvndm8t" style="text-align: left;">Become the Acquiring-as-a-Service Backbone&nbsp;</h2>A second, more ambitious strategy sees banks flip the disruption narrative on its head: rather than simply modernizing their own merchant book, some banks are positioning themselves as the licensed, regulated infrastructure layer for fintechs, PSPs, and software platforms that want to offer embedded acquiring but don't want to become a bank themselves. In this model, the bank becomes a wholesale acquiring partner, powering other companies' merchant acquiring propositions under the hood, often through the same modern MMS infrastructure that powers its direct merchant business. This turns embedded acquiring from a threat into a growth channel.&nbsp;<h3 class="heading-node" id="ceoltwpkd" style="text-align: left;">Double Down on Underserved Segments&nbsp;</h3>A third response has been strategic focus, rather than trying to compete everywhere, some banks are concentrating on merchant segments where trust, credit relationships, and regulatory standing matter more than pure technology velocity: larger enterprise merchants with complex settlement needs, regulated industries, or markets where local banking relationships remain a genuine advantage over global fintech platforms. This is a narrower strategy, but a defensible one, particularly for banks that can pair it with a modernized technology layer via an MMS partner rather than trying to out-build fintech competitors head-on.&nbsp;What's notable is that these three responses aren't mutually exclusive, many banks are pursuing a blend of all three simultaneously, using a modern MMS partnership as the common technology foundation underneath each strategy.&nbsp;<h1 class="heading-node" id="zau9qnpry" style="text-align: left;">Regional Nuances Worth Watching in 2026&nbsp;</h1>India continues to be a bellwether for where global acquiring is headed, given the sheer pace of digital payments adoption, UPI's dominance in transaction volume, and the maturity of players like Pine Labs, Razorpay, and Cashfree in merchant-facing innovation. Regulatory shifts around MDR, tokenization mandates, and interoperability continue to reshape acquirer economics faster than in most other markets, making India a useful preview of pressures that eventually surface elsewhere.&nbsp;The Middle East (UAE, Saudi Arabia, Egypt) has seen a wave of acquiring modernization driven by national digital payment strategies, with Network International, Geidea, and PayTabs expanding aggressively, often in partnership with, rather than in competition against, regional banks that see the value of a modern acquiring layer without owning the full technology stack.&nbsp;Europe remains shaped by regulatory complexity (interchange caps, PSD2/3 evolution, and strong customer authentication requirements) that continues to favor scaled acquirers like Nexi and Worldline who can absorb compliance costs across a large merchant base, while also creating openings for API-first challengers like Adyen and Checkout to win share from banks slower to adapt.&nbsp;North America continues to be defined by the aftershocks of the Global Payments–Worldpay consolidation and Fiserv's ongoing platform integration efforts, alongside steady share gains by Stripe and Square (Block) in the SME and platform-embedded acquiring space.&nbsp;<h1 class="heading-node" id="hlzldvzvm" style="text-align: left;">What This Means Going Forward&nbsp;</h1>Three things seem clear as the global acquiring landscape continues to evolve through 2026 and beyond:&nbsp;<h3 class="heading-node" id="z2dysqj2z" style="text-align: left;">Scale and specialization are both viable strategies, but the middle ground is shrinking</h3>Acquirers and banks need to either achieve genuine scale advantages or build defensible specialization (by segment, geography, or use case). Being merely "adequate" across the board is an increasingly untenable position.&nbsp;<h3 class="heading-node" id="s974d29qk" style="text-align: left;">The merchant experience bar, set by fintech-native platforms, is now universal</h3>Same-day settlement, unified omnichannel acceptance, self-service onboarding, and embedded value-added services aren't premium features anymore, they're the baseline every acquirer, bank, and MMS provider is measured against, everywhere.&nbsp;<h3 class="heading-node" id="550seyu8n" style="text-align: left;">Infrastructure partnerships have become the great equalizer</h3>The single biggest lever available to banks and regional acquirers who want to compete with global platforms, without the years-long rebuild or the capital intensity of true in-house platform development, is partnering with a modern MMS provider that has already solved the hard technology problems at scale across multiple markets and client banks.&nbsp;<h1 class="heading-node" id="jokoz4c2u" style="text-align: left;">Where M2P’s Merchant Acquiring Fits?</h1>This is precisely the gap M2P's Merchant Acquiring infrastructure is built to close. As consolidation reshapes who owns global acquiring volume, and fintech platforms continue to redefine merchant expectations, banks and NBFCs need a way to modernize fast, compete credibly, and increasingly become acquiring infrastructure providers themselves for the fintechs and platforms building on top of them. M2P's modular, API-first Merchant Acquiring stack is designed to let banks do exactly that: modernize the technology layer, retain the merchant and regulatory relationship, and move at a pace that keeps them relevant in a landscape being reshaped in real time.&nbsp;The global acquiring industry in 2026 isn't converging toward a single winning model — it's fragmenting into scaled giants, disruptive platforms, and banks that have learned to borrow the best of both through the right infrastructure partner. The players who understand that distinction early will be the ones setting the pace for the next decade of merchant acquiring, rather than reacting to it.&nbsp;Want to see how M2P's Merchant Acquiring infrastructure can help your bank or fintech compete in this fast-consolidating, fintech-disrupted landscape?<a class="link" href="https://m2pfintech.com/contact-us/?utm_source=blg&amp;utm_medium=mms&amp;utm_campaign=global-acquiring" target="_blank"> Get in touch</a> with M2P to learn more.&nbsp;ti

The Global Acquiring Landscape in 2026: Consolidation, Fintech Disruption, and the Bank Response

<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/npci-mapper-switch-and-psp-decoding-the-upi-transaction-journey_2.webp" alt="NPCI Switch and PSP" title="" id="pl2wl0tbl" width="100%" height="347"> Every time someone taps Pay on a UPI app, a lot happens in the two or three seconds before the screen shows Payment Successful. A UPI payment isn't a single hop from one bank account to another - it's a relay race across at least three distinct systems, each with a specific job, each bound by strict timing rules set by NPCI.&nbsp;Most explainers stop at UPI is fast and free. Very few actually open up the pipes and show what's moving inside them. This one does.&nbsp;If you work in banking technology, payments product, or fintech operations, understanding this journey isn't academic - it's the difference between reading an incident report and actually understanding why a transaction failed, or why your team is evaluating a new UPI payment platform in the first place.&nbsp;<h2 class="heading-node" id="cvf97exnt" style="text-align: left;">The Three Layers Behind Every UPI Transaction&nbsp;</h2>Before we walk through the flow step-by-step, it helps to meet the three main players. Each one solves a different problem, and each is a potential point of friction if not built or maintained well.&nbsp;1. PSP (Payment Service Provider)&nbsp;The PSP in UPI is the app layer - the interface the payer or payee actually touches. Google Pay, PhonePe, Paytm, and every bank's own UPI app are all PSPs. A PSP's job is narrow but critical: capture the payment intent (amount, VPA, PIN), present it in a usable interface, and pass it downstream. A PSP doesn't know how to actually move money - it simply hands off the request into the UPI ecosystem, expecting the other layers to do the heavy lifting of routing, validation, and settlement.&nbsp;2. NPCI Mapper&nbsp;&nbsp;Think of the Mapper as UPI's directory service - the "phonebook" that translates a Virtual Payment Address (VPA, like <code class="inline" spellcheck="false">name@bank</code>) into the actual account number and IIN (Issuer Identification Number) it's linked to. Without the Mapper, a UPI app would have no idea which bank, which branch, or which account a VPA actually points to. This lookup happens almost instantly, but it's a mandatory hop in the chain - every single UPI transaction touches the Mapper at least once.&nbsp;3. Payment Switch&nbsp;&nbsp;This is the layer most people outside payments engineering have never had to think about, and it's arguably the most important one operationally. A payment switch - sometimes called a payment gateway switch - sits between the PSP / NPCI layer and each bank's core banking system (CBS). Its job is to:&nbsp;- Route the transaction request to the correct destination bank&nbsp;- Translate message formats between NPCI's protocol and the bank's internal systems&nbsp;- Validate the transaction against business rules and fraud checks&nbsp;- Manage retries, timeouts, and status reconciliation&nbsp;- Ensure the entire round trip completes within NPCI's mandated Turnaround Time (TAT)&nbsp;If the PSP is the storefront and the Mapper is the directory, the switch is the logistics network - invisible when it works, and the first thing that breaks when transaction volumes spike.&nbsp;&nbsp;4. Issuer and Acquirer Bank Systems (CBS)&nbsp;At the very end of the chain sit the actual banks - the issuer (payer's bank) and the acquirer (payee's bank). Their <a class="link" href="https://m2pfintech.com/turing-core-banking/" target="_blank">Core Banking Systems</a> execute the real debit and credit. Everything before this point is essentially routing and validation; this is where the money actually moves.&nbsp;<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/upi-transaction-journey-diagram.svg" alt="UPI Transaction Journey" title="" id="4zthlcud3" width="NaN" height="NaN">Walking through it step by step:&nbsp;1. Initiation - The payer opens their PSP app and enters a VPA, amount, and UPI PIN. The PSP packages this as a payment request.&nbsp;2. VPA Resolution - The request reaches NPCI, which queries the Mapper to resolve the payee's VPA to their actual account and IIN.&nbsp;3. Routing via the Switch - NPCI forwards the request to the payment switch connected to the payer's issuing bank. The switch validates the request format, checks it against the bank's rules, and forwards it into the bank's CBS.&nbsp;4. Debit at the Issuer - The issuing bank's CBS checks balance and account status, then executes the debit, sending a confirmation back through the switch.&nbsp;5. Credit at the Acquirer - NPCI relays the transaction to the payee's bank via their own switch, which passes it to their CBS for the credit.&nbsp;6. Confirmation Loop - Success or failure status flows back up the same chain - CBS → switch → NPCI → PSP - and the payer and payee both see the result on their respective apps.&nbsp;All of this - six distinct hops across potentially four different organizations - is expected to complete within NPCI's TAT window, typically under 15–30 seconds depending on the transaction type. This is why UPI transaction processing at scale is such a demanding engineering problem: it isn't just about handling volume, it's about handling volume fast, correctly, every single time.&nbsp;<h2 class="heading-node" id="5hblm87qq" style="text-align: left;">Why the Switch Is the Layer That Makes or Breaks the Experience&nbsp;</h2>The PSP app is what users see. The Mapper mostly runs invisibly and reliably in the background, maintained centrally by NPCI. But the payment switch architecture each bank or PSP operates is where most real-world friction originates, for a few reasons:&nbsp;<ul class="list-node" id="v442f7788"><li>It has to handle enormous, unpredictable load - Salary days, festival sales, IPO subscription windows - UPI volume can spike 3-4x within hours. A switch that isn't built for elastic scaling becomes the bottleneck, causing timeouts that show up to users as "payment failed" even though money may have moved.&nbsp;</li></ul><ul class="list-node" id="81mqoln86"><li>It's where compliance actually gets enforced - NPCI's TAT rules, retry logic, and message format standards aren't self-enforcing - the switch is the component responsible for adhering to them. A poorly built switch can silently violate TAT norms, exposing the bank to penalties and reconciliation headaches down the line.&nbsp;</li></ul><ul class="list-node" id="xuqyteu5v"><li>It's the translation layer between two very different worlds - NPCI speaks a standardized protocol; every bank's CBS speaks its own internal format, often decades old. The switch has to bridge these without introducing errors, and this translation logic gets more complex as banks add new products - UPI Lite, Credit Line on UPI, international UPI acceptance - each with its own message variations.&nbsp;</li></ul><ul class="list-node" id="cz1fqzp66"><li>It's where fraud checks need to happen in real time - Since the switch sees every transaction before it hits the CBS, it's a natural chokepoint for velocity checks, risk scoring, and anomaly detection - but only if it's designed to do this without adding latency that blows the TAT budget.</li></ul>This is why so many banks, especially mid-sized and regional players, find that building and maintaining switch infrastructure in-house is a far bigger undertaking than it first appears. It's not a one-time build - it's an ongoing commitment to keep pace with every NPCI circular, every new UPI feature, and every traffic spike.&nbsp;<h2 class="heading-node" id="vkmm2bshm" style="text-align: left;">How This Differs From a Payment Gateway&nbsp;</h2>It's common for the terms UPI payment gateway and payment switch to get used interchangeably, but they solve different problems. A payment gateway typically sits on the merchant side, helping a business accept payments across multiple methods (UPI, cards, wallets) through a single integration - it's focused on UPI API integration for acceptance. A payment switch, by contrast, operates at the infrastructure level between PSPs, NPCI, and bank systems - it's concerned with routing, translation, and compliance at the network layer, not merchant-facing checkout experiences.&nbsp;To put it in simple words: a gateway helps a merchant accept a payment. A switch helps that payment actually travel correctly through the banking network to get there.&nbsp;<h2 class="heading-node" id="z287z2ygy" style="text-align: left;">Where Collect Requests and QR Payments Fit In&nbsp;</h2>The journey above describes a push transaction - the payer initiating a payment. But UPI also supports pull flows, most commonly through the UPI collect API, where a payee requests money from a payer (used heavily in bill payments, loan EMI collection, and merchant checkouts). A collect request follows a similar path through the Mapper and switch, but in reverse initiation - the payee's PSP raises the request, which is routed to the payer's bank for approval before the debit occurs.&nbsp;Similarly, a UPI QR payment solution simply changes how the VPA and amount are captured at the front end - a QR code encodes the payee's VPA so the payer's app can scan rather than type it - but once initiated, the transaction flows through the exact same Mapper-Switch-CBS journey described above. The QR code changes the input method, not the underlying UPI acquiring solution infrastructure that processes the transaction.&nbsp;<h2 class="heading-node" id="0lzxskfoj" style="text-align: left;">Why This Matters Beyond Curiosity?</h2>- For banks evaluating vendors: knowing what a switch actually does helps you ask the right questions when comparing UPI payment software providers - uptime SLAs, TAT adherence rates, reconciliation automation, and scalability under peak load all matter far more than surface-level feature lists.&nbsp;- For product and ops teams: when a transaction fails, knowing which layer likely caused it (Mapper resolution issue vs. switch timeout vs. CBS rejection) massively speeds up root-cause analysis and customer communication.&nbsp;- For anyone building on UPI: whether you're integrating a UPI payment gateway for merchant acceptance or building a UPI payment platform from scratch, understanding where the switch sits in the chain clarifies exactly which parts of the stack you need to build versus rely on partners for.&nbsp;<h2 class="heading-node" id="lkjke4qns" style="text-align: left;">The Bottom Line&nbsp;</h2>A UPI transaction that completes in under three seconds hides an enormous amount of coordinated engineering - VPA resolution through the Mapper, message routing and validation through the switch, and the actual ledger movement inside each bank's core system. The PSP is the part everyone sees. The switch is the part that determines whether the experience actually works.&nbsp;This is exactly the layer that specialized <a class="link" href="https://m2pfintech.com/blog/future-proofing-your-upi-infrastructure-strategy/" target="_blank">UPI switch infrastructure</a> is built to handle - absorbing the complexity of NPCI compliance, peak-load routing, real-time fraud checks, and reconciliation, so banks and PSPs don't have to build and maintain this machinery from scratch. <a class="link" href="https://m2pfintech.com/upi/" target="_blank">M2P's UPI Switch</a> is purpose-built for precisely this layer of the journey - if you're evaluating how your current switch infrastructure holds up against scale, compliance, and reliability demands. <a class="link" href="https://m2pfintech.com/contact-us/?utm_source=M2PBlogs&amp;utm_medium=social&amp;utm_campaign=NPCI_Mapper_Blog" target="_blank">Talk to us today</a>!<h2 class="heading-node" id="do51q939g" style="text-align: left;">Frequently Asked Questions</h2><ul class="list-node" id="8f07kttqw"><li>What is the difference between NPCI Mapper and a payment switch? The Mapper is a lookup service that resolves a VPA to an account and IIN. A payment switch is the routing and translation layer that carries the actual transaction request between NPCI, PSPs, and bank core systems, enforcing compliance and handling scale.</li><li>Is a PSP the same as a UPI payment gateway? Not quite. A PSP is the app-layer provider consumers interact with (like GPay or a bank's UPI app). A UPI payment gateway is typically merchant-facing infrastructure that helps businesses accept UPI (and other) payments through a single integration.&nbsp;</li><li>Why do UPI transactions sometimes fail even when money is debited?&nbsp; This usually happens when the confirmation message is delayed or lost somewhere in the Mapper-Switch-CBS return path, often due to timeouts under high load. The debit occurs, but the success confirmation doesn't reach the PSP in time, resulting in a "deemed approved" or later-reversed transaction.&nbsp;</li></ul>

NPCI Mapper, Switch, and PSP: Decoding the UPI Transaction Journey

Liability Shift 101: Who Pays When Authentication Fails, and How ACS Placement Changes the Answer

How to Issue a Business Credit Card in South Africa Without a Legacy Banking Core (2026 Guide)

Build vs. Buy: The Real Cost of Running an In-House ACS

<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/the-great-acquiring-rethink_why-banks-are-choosing-mms-partners-over-diy_2_2000x1000.webp" alt="The Great Acquiring Rethink: Why Banks Are Choosing MMS Partners over DIY" title="" id="vei2l68by" width="100%" height="362">For decades, Merchant Acquiring was one of those businesses banks simply assumed they had to own end-to-end. The logic seemed sound: acquiring touches core banking relationships, settlement accounts, and merchant credit risk, so why would a bank hand any of that over to a third party?&nbsp;That logic is now being tested — and increasingly, it's losing. Across markets, banks and NBFCs are quietly (and sometimes not so quietly) stepping back from running their own Merchant Acquiring and Merchant Management System (MMS) stacks in-house, and instead partnering with specialist MMS providers to power that business. Global acquirers built their scale over the last twenty years partly by absorbing exactly this kind of outsourced infrastructure demand. Newer entrants built platform-native acquiring stacks that banks now benchmark themselves against. And in high-growth markets like India, the Middle East, and Southeast Asia, players have shown just how fast a modern, API-first acquiring stack can move compared to a legacy one.&nbsp;So what's actually driving this shift? Let's unpack the real reasons banks are rethinking their in-house Merchant Acquiring stacks — and why "partner with an MMS provider" has gone from a fallback option to a strategic first choice.&nbsp;<h2 class="heading-node" id="dn647bgke" style="text-align: left;">The Cost of Legacy Acquiring Infrastructure Has Become Impossible to Ignore&nbsp;</h2>Most in-house Merchant Acquiring stacks at banks were built 10, 15, even 20 years ago. They were designed for a world of physical POS terminals, batch settlement, and a relatively small, stable base of large-format merchants. That world doesn't exist anymore.&nbsp;Today, a bank's merchant base includes everything from a single QR code at a roadside kiosk to an omnichannel retail chain processing in-store, online, and app-based payments simultaneously. Supporting that diversity on a legacy stack means one of two things: expensive custom development bolted onto an aging core, or simply not supporting large segments of the merchant market at all.&nbsp;The total cost of ownership (TCO) math has quietly flipped. A decade ago, building in-house was often cheaper than the licensing fees of third-party platforms. Today, the opposite is frequently true, once you account for:&nbsp;<ul class="list-node" id="31yurlud5"><li>Maintenance and technical debt on systems that were never designed for cloud-native, API-first operations&nbsp;</li></ul><ul class="list-node" id="udi872vy6"><li>Specialized talent needed to keep old acquiring cores running — a shrinking and increasingly expensive pool of engineers&nbsp;</li></ul><ul class="list-node" id="dtoryyszz"><li>Opportunity cost of engineering teams spent on "keeping the lights on" rather than building differentiated merchant products&nbsp;</li></ul><ul class="list-node" id="tliiaaodj"><li>Compliance re-certification costs every time a legacy system needs to be brought up to the latest PCI-DSS or card network mandate&nbsp;</li></ul>MMS providers spread these costs across many client banks, meaning the same infrastructure investment that would bankrupt a single bank's IT budget becomes a shared, amortized cost across a partner's entire portfolio. This is precisely the "SaaS logic" that made Adyen and Stripe so disruptive to the acquiring business — and banks are now applying that logic inward.&nbsp;<h2 class="heading-node" id="9zk6esfps" style="text-align: left;">Speed to Market Has Become a Competitive Weapon&nbsp;</h2>In-house acquiring stacks are notoriously slow to change. Adding a new payment method, supporting a new merchant category, or launching a value-added service like dynamic currency conversion or tap-to-phone acceptance can take a legacy team six months to a year — by which point a fintech competitor has already captured the merchant relationship.&nbsp;Contrast that with what modern MMS platforms enable. Companies like M2P have built their entire value proposition around turning POS deployment and merchant onboarding into a same-day or same-week activity in India. M2P’s Merchant Acquiring architecture lets enterprise merchants go live across markets in weeks, not quarters. Even in cross-border e-commerce acquiring, players have pushed the industry toward configuration-based go-lives rather than custom-coded integrations.&nbsp;Banks that still run in-house stacks are watching their addressable merchant segments — particularly SMEs and MSMEs who won't wait months for onboarding — get captured by fintechs and payment aggregators who partner with agile MMS providers. The realization setting in across the industry is simple: owning the infrastructure is no longer synonymous with owning the merchant relationship. A bank can retain the merchant relationship, the settlement account, the brand, and the risk book, while letting a specialist MMS partner run the acquiring engine underneath it.&nbsp;<h2 class="heading-node" id="7klfx88ui" style="text-align: left;">Merchant Expectations Have Moved Faster Than Bank IT Roadmaps&nbsp;</h2>Merchants today expect same-day settlement, real-time dashboards, self-service onboarding, embedded lending offers, and omnichannel acceptance across QR, cards, wallets, and BNPL — often in a single unified merchant portal. These are baseline expectations shaped by what merchants have experienced and what the industry had already built and not luxury features.&nbsp;Legacy in-house acquiring stacks, built around batch-mode settlement cycles and static reporting, simply cannot deliver this experience without a ground-up rebuild. And a ground-up rebuild inside a regulated bank's technology environment is a multi-year, multi-million-dollar undertaking with real execution risk.&nbsp;Modern MMS providers, by contrast, have already solved these problems — because merchant experience is their core product, refined across hundreds of client banks and thousands of merchants. Partnering means a bank can offer a merchant experience competitive with Adyen or Stripe on day one, without having to become a product engineering organization first.&nbsp;<h2 class="heading-node" id="6wgjgewhu" style="text-align: left;">Regulatory and Compliance Complexity Keeps Rising&nbsp;</h2>Merchant Acquiring sits at the intersection of some of the most demanding compliance regimes in financial services: PCI-DSS, card network mandates (Visa/Mastercard/RuPay/local schemes), AML/KYB requirements for merchant onboarding, data localization rules, and — in markets like India and the GCC — an evolving regulatory posture from central banks and payment regulators on interoperability, MDR caps, and merchant categorization.&nbsp;Each of these requires continuous, specialized investment to stay compliant. A bank running its own stack has to independently track, interpret, and implement every regulatory change across every market it operates in. An MMS provider serving multiple banks does this once, centrally, and pushes the update across its entire client base — turning a recurring compliance burden into a shared, managed service.&nbsp;This matters even more for banks operating across multiple geographies, where regulatory divergence (say, between RBI guidelines in India and central bank requirements in the UAE or Saudi Arabia) can otherwise mean maintaining parallel, market-specific compliance teams for the same underlying acquiring function.&nbsp;<h2 class="heading-node" id="msfmslefs" style="text-align: left;">Talent Is the Real Bottleneck — Not Just Budget&nbsp;</h2>It's tempting to frame the build-vs-partner decision purely as a cost question. But conversations with bank technology leaders increasingly point to a deeper issue: it's genuinely hard to hire and retain engineering talent that wants to work on legacy acquiring cores.&nbsp;The best payments engineers want to work on modern, API-first, cloud-native systems — the kind of stacks that MMS providers and fintech-native acquirers have built. Banks competing for this talent against major players and well-funded MMS providers are fighting an uphill battle when the job on offer is maintaining a fifteen-year-old COBOL-adjacent settlement engine.&nbsp;Partnering with an MMS provider effectively lets a bank access modern engineering capability without having to win the talent war itself. The provider's roadmap, informed by serving dozens of banks and millions of merchant transactions, becomes the bank's roadmap too — without the bank needing to staff a payments engineering org from scratch.&nbsp;<h2 class="heading-node" id="d8i335opl" style="text-align: left;">Embedded Finance Is Rewriting Who Even Needs to Acquire&nbsp;</h2>Perhaps the most structural shift is this: acquiring is no longer just a bank-to-merchant relationship. Marketplaces, SaaS platforms, and vertical fintechs increasingly want to embed acquiring directly into their own products — think a POS software company that wants to offer payment acceptance natively, or a B2B marketplace that wants to settle its sellers directly.&nbsp;This is the "embedded acquiring" or "acquiring-as-a-service" wave, and it fundamentally changes the economics of building in-house. A bank now competes not just with other banks and traditional acquirers, but with software platforms that white-label acquiring capability from an MMS provider and go to market faster than any bank's internal roadmap would allow.&nbsp;For banks, the strategic response has been to flip the model: instead of trying to out-build these platforms, banks are partnering with MMS providers to power their own acquiring-as-a-service offering — becoming the licensed, regulated backbone for fintechs and platforms, while the MMS provider handles the technology layer.&nbsp;<h2 class="heading-node" id="m0twvnlzf" style="text-align: left;">Risk Management Gets Better, Not Worse, With the Right Partner&nbsp;</h2>A common objection banks raise is risk: "If we don't run the stack ourselves, how do we control merchant risk?" In practice, the opposite tends to be true with a mature MMS partner.&nbsp;Modern MMS platforms come with built-in, continuously updated risk and underwriting engines — AI-driven merchant risk scoring, transaction monitoring, <a class="link" href="https://m2pfintech.com/frm-aml/?utm_source=build-buy&amp;utm_medium=mms&amp;utm_campaign=aug" target="_blank">fraud and risk management</a>, chargeback and dispute automation, and portfolio-level anomaly detection — refined across a much larger and more diverse merchant dataset than any single bank's portfolio alone could provide. Banks retain the decision-making authority and the credit relationship, but the underlying risk tooling is sharper because it's built on a broader base of merchant behavior data across industries and geographies.&nbsp;This is a meaningful shift from the earlier assumption that risk control requires infrastructure control. Increasingly, risk control requires the best infrastructure — and that's rarely the one a single bank can build and maintain alone.&nbsp;<h2 class="heading-node" id="l01narj7t" style="text-align: left;">The Competitive Landscape Has Made "Good Enough" No Longer Good Enough&nbsp;</h2>It's worth stating plainly: banks aren't just competing with other banks anymore. They're competing with<a class="link" href="https://m2pfintech.com/merchant-acquiring-solutions/?utm_source=build-buy&amp;utm_medium=mms&amp;utm_campaign=aug" target="_blank"> M2P’s MMS</a>, Adyen, Stripe, Pine Labs, Razorpay, Cashfree, PayU, BillDesk, Checkout, Network International, Geidea, and a long list of well-capitalized, technology-first acquirers and PSPs — many of whom can onboard a merchant in minutes and settle funds same-day.&nbsp;A bank running a legacy in-house stack isn't just accepting higher operating costs; it's accepting a permanently inferior product compared to what fintech-native competitors offer. In a merchant acquiring market where switching costs for merchants are falling (thanks to easier onboarding elsewhere), that product gap translates directly into portfolio attrition.&nbsp;Partnering with a modern MMS provider like M2P is, in this light, less about outsourcing and more about competitive parity — it's how a bank ensures its merchant acquiring business can actually compete for the next decade, not just maintain the one it inherited from the last.&nbsp;<h3 class="heading-node" id="2xefvqnwr" style="text-align: left;">So What Does the "Partner" Model Actually Look Like?&nbsp;</h3>Rethinking the stack doesn't mean a bank exits merchant acquiring or hands over its merchant relationships wholesale. In practice, the shift toward MMS partnerships tends to preserve what banks value most — the merchant relationship, the balance sheet, the brand, and regulatory ownership — while transferring the technology burden to a specialist. That typically includes:&nbsp;<ul class="list-node" id="hzt77ob8n"><li>Merchant onboarding and lifecycle management — automated KYB, risk-based underwriting, and self-service merchant portals&nbsp;</li></ul><ul class="list-node" id="2ix5ceho6"><li>Multi-rail acceptance — cards, QR, wallets, BNPL, and SoftPOS/Tap-to-Phone under one merchant experience&nbsp;</li></ul><ul class="list-node" id="niwwwfikw"><li>Settlement and reconciliation — real-time or near-real-time settlement engines with <a class="link" href="https://m2pfintech.com/recon360/?utm_source=build-buy&amp;utm_medium=mms&amp;utm_campaign=aug" target="_blank">automated reconciliation</a>&nbsp;</li></ul><ul class="list-node" id="2bd2zkpng"><li>Risk and dispute management — AI-driven monitoring, chargeback workflows, and portfolio risk dashboards&nbsp;</li></ul><ul class="list-node" id="wfca48gfm"><li>Value-added services — the analytics, lending, and loyalty layers that turn a payments relationship into a broader merchant banking relationship&nbsp;</li></ul>The bank stays the bank. The MMS provider becomes the engine room.&nbsp;<h2 class="heading-node" id="i629a8zsj" style="text-align: left;">The Bottom Line&nbsp;</h2>The shift away from in-house Merchant Acquiring stacks isn't a story about banks giving up on payments. It's a story about banks recognizing that the infrastructure layer of acquiring has become a specialized, fast-moving, capital-intensive discipline of its own — one best run by partners who do nothing else, all day, across dozens of clients and millions of merchants.&nbsp;The banks winning in merchant acquiring today aren't the ones with the biggest internal engineering teams. They're the ones who've figured out how to combine their trust, balance sheet, and merchant relationships with a modern MMS provider's technology, speed, and compliance depth, and get the best of both.&nbsp;This is exactly the space M2P's Merchant Acquiring stack is built for: modular, API-first infrastructure that lets banks and NBFCs launch or modernize their acquiring business without the multi-year rebuild, so they can compete with the Adyens and Pine Labs of the world on the merchant experience that matters most.&nbsp;<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAlsAAAABCAYAAADpT2vJAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAADsMAAA7DAcdvqGQAAAAZSURBVEhL7cExAQAAAMKg9U9tCj8gAABeagltAAHvBUYeAAAAAElFTkSuQmCC" alt="" title="" width="100%" height="1">&nbsp;Looking to modernize your bank's Merchant Acquiring stack without the multi-year rebuild? <a class="link" href="https://m2pfintech.com/contact-us/?utm_source=build-buy&amp;utm_medium=mms&amp;utm_campaign=aug" target="_blank">Talk to M2P</a> about how our Merchant Acquiring and MMS infrastructure can get you there faster.&nbsp;

Why Banks are Rethinking In-House Merchant Acquiring Stacks and turning to MMS Partner

<img src="https://m2p-website-file.s3.ap-south-1.amazonaws.com/marketing-cms/m2p-blog/2026/08/what-every-banks-product-team-should-understand-before-partnering_2_2000x1000-copy.webp" alt="Credit Card Stack" title="" id="gtxcd3glr" width="100%" height="347">Every few months, a new brand - an airline, a fintech app, an e-commerce platform - launches a co-branded credit card. Somewhere behind that card is a bank or NBFC, and increasingly, a Banking-as-a-Service (BaaS) partner sitting in between.&nbsp;If you're on a bank's product team and you've been asked to evaluate a BaaS partnership for a card program, this piece is meant to save you a few uncomfortable surprises six months into the contract.&nbsp;<h2 class="heading-node" id="spd78v11y" style="text-align: left;">What BaaS Actually Means for Credit Cards</h2>In the context of credit cards, is simple: a technology and operations layer that lets your bank issue cards through a partner's rails - APIs for card issuance, KYC, transaction processing, and often the customer-facing app - instead of building all of it in-house.&nbsp;Your bank still holds the license, still carries the regulatory responsibility, and still owns the customer relationship on paper. The BaaS partner handles the plumbing.&nbsp;That last point is where most confusion starts. Plumbing doesn't mean irrelevant - it means invisible until something breaks, and when it breaks, the bank is still the one RBI calls.&nbsp;<h2 class="heading-node" id="6i1p6efqo" style="text-align: left;">Why This Conversation Is Happening Now&nbsp;</h2>Three things are pushing more banks toward BaaS-style credit card partnerships:&nbsp;<ul class="list-node" id="obocj3dzp"><li>Speed. Building card issuance infrastructure from scratch takes time most banks don't want to spend when a competitor's co-branded card is already live.&nbsp;</li><li>Non-bank brands want in. Airlines, D2C brands, and fintech apps want a credit card product, but they're not licensed to issue one. They need a bank, and increasingly, that bank needs a BaaS layer to make the partnership operationally workable.&nbsp;</li><li>Regulatory scrutiny has increased. [VERIFY: cite specific RBI circular/guideline on co-branded cards and outsourcing of financial services, latest version] has made banks more cautious about who they partner with and how responsibilities are split — which ironically has made well-structured BaaS partnerships more attractive, not less.&nbsp;</li></ul><h2 class="heading-node" id="u58ylwkgl" style="text-align: left;">The Three Ways Credit Card Programs Get Built Today&nbsp;</h2>1. Direct issuance - the bank builds and owns the entire stack, from card issuance to servicing.&nbsp;2. BaaS partnership - the bank owns the license and compliance responsibility; a BaaS provider handles issuance infrastructure, processing, and often the co-brand integration.&nbsp;3. Full outsourcing to a program manager - the bank plays a more limited role, and a third party manages most of the day-to-day program operations under the bank's licence.&nbsp;Most large co-branded card programs in India today sit somewhere between models 2 and 3, with the exact split depending on the bank's risk appetite and the BaaS provider's capabilities.&nbsp;<h2 class="heading-node" id="el6raas8g" style="text-align: left;">Who's Responsible for What - And Why This Is the Part Product Teams Skip&nbsp;</h2>This is the section that gets glossed over during the sales pitch and becomes a headache during an audit.&nbsp;<ul class="list-node" id="cvuv3svrx"><li>The bank is accountable to the regulator, full stop. A BaaS partner's failure is still the bank's compliance failure in the eyes of RBI.&nbsp;</li><li>The BaaS/program management partner typically owns the technology stack, uptime, fraud monitoring tooling, and often first-line customer support.&nbsp;</li><li>The brand partner (in co-branded programs) owns marketing, customer acquisition, and the reward/loyalty construct - but has no regulatory standing of its own.&nbsp; </li></ul>Before signing anything, a bank's product team should have clear, written answers to:&nbsp;<ul class="list-node" id="k583z0caz"><li>Who is liable if a fraud incident goes undetected - the bank, the BaaS partner, or both, and in what proportion?&nbsp;</li><li>Who owns the customer data, and where is it hosted? Does this comply with (VERIFY: current RBI data localization requirements)?&nbsp;</li><li>What SLAs exist for card issuance turnaround, dispute resolution, and system uptime - and what are the penalties if they're missed?&nbsp;</li><li>Can the bank audit the BaaS partner's systems and processes on demand, or only on a scheduled basis?&nbsp;</li><li>What happens to the program (and the customer base) if the bank wants to exit the partnership?&nbsp;</li></ul><h2 class="heading-node" id="tilwhz9vi" style="text-align: left;">Common Mistakes Banks Make in BaaS Partnerships&nbsp;&nbsp;</h2><ul class="list-node" id="l2p4qjkjb"><li>Treating the BaaS partner as a vendor instead of an extension of the bank's compliance perimeter. Regulators don't make that distinction, and neither should you.&nbsp;</li><li>Underestimating the integration effort. "API-first" doesn't mean zero effort on the bank's side - core banking integration, KYC alignment, and reconciliation processes still need real engineering time.&nbsp;</li><li>Not stress-testing the exit clause. Many banks only read the exit terms after they've decided they want out - by then, negotiating leverage is gone.&nbsp;</li><li>Assuming BaaS means less compliance work. It shifts where the compliance work happens, not whether it happens.&nbsp;</li></ul><h2 class="heading-node" id="u81zeyw6c" style="text-align: left;">Where This Is Headed?</h2>Embedded finance is only going to push more non-bank brands toward wanting credit products, and BaaS is the structural bridge that makes that possible without every brand becoming a bank. For product teams at banks and <a class="link" href="https://m2pfintech.com/blog/can-nbfcs-issue-credit-cards-india/" target="_blank">NBFCs</a>, the winning position isn't avoiding these partnerships - it's going into them with a clear map of who owns what, backed by contracts that hold up under regulatory scrutiny, not just commercial negotiation.&nbsp;Getting the technology, compliance, and program management pieces right on day one is usually the difference between a BaaS partnership that scales smoothly and one that turns into a firefighting exercise. If you're evaluating partners for a credit card program, <a class="link" href="https://m2pfintech.com/credit-cards/" target="_blank">M2P's Credit Card Management System</a> is built to handle exactly this split - issuance, compliance workflows, and program operations - so your product and compliance teams aren't left reverse-engineering responsibility after something goes wrong. <a class="link" href="https://m2pfintech.com/contact-us/?utm_source=M2PBlogs&amp;utm_medium=social&amp;utm_campaign=BaaS_CCPartnership_Blog" target="_blank">Talk to us</a> about how a program like this gets structured. Frequently Asked Questions: 1. What is BaaS in the context of credit cards? Banking-as-a-Service (BaaS) for credit cards is a technology and operations layer that lets a bank issue and manage credit cards through a partner's infrastructure — covering card issuance APIs, KYC, transaction processing, and often the customer-facing app — instead of building this stack in-house. The bank retains the banking license and regulatory accountability; the BaaS partner handles the underlying plumbing.2. Who is legally responsible if something goes wrong in a BaaS credit card partnership? The bank or NBFC holding the license is always accountable to the regulator, regardless of which partner caused the failure. A BaaS partner's system failure, fraud gap, or compliance lapse is still treated as the bank's compliance failure by RBI. This is why banks should treat BaaS partners as an extension of their compliance perimeter, not as an ordinary vendor.3. What's the difference between a BaaS partnership and a program manager model for credit cards? In a BaaS partnership, the bank owns the license and compliance responsibility while the BaaS provider handles issuance infrastructure and processing. In a full program manager model, the bank plays a more limited role and the third party manages most day-to-day program operations under the bank's license. Most large co-branded card programs today sit somewhere between these two models.4. Does using a BaaS partner reduce a bank's compliance workload? No. BaaS shifts where compliance work happens - from the bank's internal teams to a shared or partner-managed workflow - but it does not eliminate the compliance obligation itself. Banks that assume BaaS means less compliance oversight are the ones most likely to face issues during an audit.5. What should a bank's product team confirm before signing a BaaS credit card partnership? Before signing, a bank should have written clarity on: fraud liability and its proportional split, customer data ownership and hosting location, SLAs for issuance turnaround and dispute resolution (with penalties for misses), audit rights over the BaaS partner's systems, and a clearly defined exit process for the program and customer base.6. Why is the exit clause in a BaaS contract so important? Because negotiating leverage is highest before the contract is signed and lowest once a bank has already decided to leave. Many banks only scrutinize exit terms after they want out, by which point the BaaS partner has little incentive to offer favorable terms.7. Why are more non-bank brands launching credit cards through BaaS partners? Non-bank brands like airlines, D2C companies, and fintech apps aren't licensed to issue credit directly. BaaS gives them a structural bridge to launch co-branded card products through a licensed bank without either party having to build the entire stack from scratch.

M2P Fintech

Product

About

Compliance

Resources