how do psd3 and psr affect the ATM businesses, from the business perspective?

While PSD3 and PSR redefine the legal "who" and "how" of payment access, the [Digital Operational Resilience Act (DORA)](https://eur-lex.europa.eu/eli/reg/2022/2554/oj) introduces a technical "what" that fundamentally alters the cost of physical infrastructure. The "spillover" effect occurs when the high-level security requirements intended for systemic banks migrate—by contractual necessity or regulatory osmosis—into the independent ATM deployer (IAD) ecosystem. ## Contractual Isomorphism and the "Waterfall" Effect The most immediate spillover is not legislative but contractual. Under **Chapter V of DORA**, financial entities must manage ICT third-party risk. Because banks increasingly outsource ATM fleets to IADs, these IADs—regardless of whether they are officially "financial entities" under Article 2—are forced to adopt DORA-compliant posture to remain "bankable" partners. This creates a state of **contractual isomorphism**, where the smaller, leaner IAD begins to look exactly like a systemic bank in its administrative and technical overhead. As the European Supervisory Authorities (ESAs) note in their [Joint Technical Standards](https://www.esma.europa.eu/press-news/esma-news/esas-publish-first-set-final-draft-technical-standards-under-dora), third-party service providers must provide "unrestricted rights of inspection and audit." For an ATM business, this means the end of "set and forget" hardware; every terminal becomes a node in a live, auditable network. ## The Death of the "Patch Gap" Historically, ATM hardware lifecycles were measured in decades, often running on legacy operating systems (like Windows XP or 7) long after their "end-of-life." DORA’s requirement for **vulnerability management and accelerated patching (Article 6)** creates a "technical spillover" that effectively kills the legacy ATM. > "Financial entities shall identify, classify and document all ICT-supported business functions, the information assets supporting those functions, and the ICT system configurations and the links between them." — *DORA, Article 8(1)* For ATM businesses, this mandates a shift from hardware management to **continuous software orchestration**. The spillover here is a sudden, massive increase in Capital Expenditure (CapEx) as firms are forced to replace stable, physical machines that simply cannot support the encrypted, multi-factor, and log-heavy environments DORA demands. ## Concentration Risk and the "Critical Provider" Trap A counterintuitive spillover is the potential for IADs to be designated as **Critical ICT Third-Party Providers (CTPPs)**. If an ATM deployer captures significant market share in a specific EU member state, they may fall under the direct oversight of the Lead Overseer (e.g., the EBA). This creates a "regulatory ceiling" on growth. An ATM business might find that crossing a certain threshold of market penetration triggers a level of oversight—including "oversight fees" and "recommendations" that carry the weight of law—which destroys the thin margins typical of the ATM industry. Instead of seeking scale, smart IADs may intentionally fragment their operations to avoid the "critical" designation, leading to a less efficient, more decentralized cash infrastructure. ## Resilience as a Barrier to Entry DORA spillover effectively transforms **resilience into a competitive moat**. The requirement for "TLPT" (Threat-Led Penetration Testing) for significant entities means that only the largest ATM operators can afford the "Red Teaming" exercises required to prove their worth to banking partners. This tilts the scales toward consolidation, where the "resilience tax" becomes a barrier that prevents innovative, smaller fintechs from entering the physical cash space.

This creates a "regulatory ceiling" on growth. An ATM business might find that crossing a certain threshold of market penetration triggers a level of oversight—including "oversight fees" and "recommendations" that carry the weight of law—which destroys the thin margins typical of the ATM industry. Instead of seeking scale, smart IADs may intentionally fragment their operations to avoid the "critical" designation, leading to a less efficient, more decentralized cash infrastructure.

In the traditional logic of industrial organization, scale is the ultimate prize, offering economies that drive down marginal costs. However, under the European Union’s [Digital Operational Resilience Act (DORA)](https://eur-lex.europa.eu/eli/reg/2022/2554/oj), an Independent ATM Deployer (IAD) that successfully scales may find itself caught in a "regulatory death zone." Here, the reward for market leadership is not higher profits, but a designation as a **Critical ICT Third-Party Provider (CTPP)**, subjecting the firm to direct, intrusive oversight that can functionally invert the benefits of growth. ## The Regulatory Ceiling: Article 31 and Systemic Risk DORA shifts the focus of financial regulation from entities (banks) to the underlying infrastructure (ICT providers). Under **Article 31**, the European Supervisory Authorities (ESAs), such as the [European Banking Authority (EBA)](https://www.eba.europa.eu/), can designate a provider as "critical" based on the systemic impact of a failure. For an IAD, which provides the ICT-heavy services of cash dispensing and transaction processing, crossing a threshold of market penetration triggers this designation. > "The designation of critical ICT third-party providers should reflect the size and nature of the financial sector’s reliance on those providers... [and] the systemic impact that a failure or operational outage of such a provider could have on the financial stability of the Union." — [DORA Preamble, Recital 78](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32022R2554) ## The Economic Friction of Oversight Once designated, an IAD faces a regime designed for global cloud giants like AWS or Microsoft, not margin-thin cash operators. This includes: 1. **Oversight Fees:** Under Article 43, the Lead Overseer charges the CTPP fees to cover all expenses related to oversight tasks. For an IAD, these non-negotiable costs can exceed the annual profit generated by the very machines that triggered the designation. 2. **Recommendations with Teeth:** The Lead Overseer can issue "recommendations" on security, audits, and hardware. While technically recommendations, failure to comply can lead to daily penalty payments of up to 1% of the average daily worldwide turnover. ## Strategic Fragmentation: A New "Lucas Critique" Faced with this "regulatory ceiling," smart IADs may engage in a form of **regulatory arbitrage** by intentionally fragmenting their operations. Instead of a single large entity, an operator might split into multiple independent subsidiaries or limit its expansion in a specific Member State to stay below the ESAs' radar. This creates a paradox of resilience. While DORA aims to secure the financial system, it may inadvertently incentivize a **less efficient, more decentralized, and technologically stagnant** cash infrastructure. As the [Bank for International Settlements (BIS)](https://www.bis.org/publ/bcbs_nl25.htm) has noted in discussions on operational resilience, systemic risk often migrates rather than disappears. By forcing IADs to stay small, the regulator might prevent "too big to fail" providers but simultaneously create a "too fragmented to secure" landscape, where no single operator has the capital to invest in high-level cybersecurity. Does the pursuit of institutional resilience fundamentally threaten the economic viability of the very services being protected? This remains the central tension for the future of European cash access.

The "DORA Paradox" rests on a fundamental misinterpretation of market dynamics: it views regulatory compliance as a pure cost center rather than a **strategic barrier to entry**. In the post-DORA landscape, an Independent ATM Deployer (IAD) that avoids "Critical ICT Third-Party Provider" (CTPP) status does not achieve freedom; it achieves irrelevance. By ignoring the **"flight to quality"** triggered by the regulation's strict supply-chain requirements, the stagnation thesis fails to account for how systemic oversight transforms into a dominant market "moat." ## The Myth of Regulatory Arbitrage The suggestion that IADs can "stay small" to avoid oversight ignores the legal obligations DORA places on the *clients* of those IADs. Under **Article 28**, financial institutions are mandated to perform exhaustive due diligence and ongoing monitoring of all ICT third-party providers. For a bank, contracting a non-critical, fragmented IAD is a high-liability endeavor. The bank must shoulder the entire burden of auditing that provider's resilience. Conversely, a CTPP comes with a **sovereign guarantee of oversight**. As George Stigler argued in his seminal work, [*The Theory of Economic Regulation*](https://www.jstor.org/stable/3003161), powerful incumbents often embrace complex regulation because it raises the "cost of doing business" to a level that smaller, less-capitalized competitors simply cannot sustain. > "Regulation may be actively sought by the producer, since it can provide protection against the competition of outsiders." — George Stigler, *The Theory of Economic Regulation* (1971) ## Systemic Integration as a Lock-in Mechanism The argument that oversight fees and recommendations lead to "stagnation" overlooks the **Network Effect** of systemic trust. When an IAD is designated as a CTPP under **Article 31**, it is effectively woven into the Union’s financial stability architecture. This creates a "Too Big to Fire" dynamic. 1. **Reduced Procurement Friction:** Once a CTPP passes Lead Overseer audits, individual banks can rely on those findings, drastically shortening the sales cycle for the IAD. 2. **Capital Access:** A CTPP designation signals to private equity and institutional lenders that the firm is a "permanent" fixture of European infrastructure, likely lowering its cost of capital despite the oversight fees. ## The Counter-Example: The Cloud Precedent We have already seen this play out in the cloud sector. Critics once argued that the [EBA Guidelines on Outsourcing](https://www.eba.europa.eu/regulation-and-policy/internal-governance/guidelines-on-outsourcing) would drive banks away from "critical" hyperscalers like AWS or Azure. Instead, the opposite occurred: the rigor of the requirements forced a consolidation of the market around those few providers capable of meeting the standard. The [Bank for International Settlements (BIS)](https://www.bis.org/publ/othp46.htm) notes that "operational resilience is becoming a key determinant of competitive position." In this light, DORA does not create a "death zone"; it creates a **premier tier of service providers**. IADs that fragment their operations to avoid Article 31 will find themselves excluded from the procurement lists of major European banks, who cannot risk the "weakest link" in their ICT supply chain. The "stagnation" will not be felt by the giants, but by the small operators who lack the scale to be audited.

Imagine a scenario where a single configuration error in a data center in Northern Virginia causes the immediate cessation of all real-time gross settlement (RTGS) systems across the Eurozone. This is no longer a hypothetical IT incident; it is a systemic financial stability risk. The designation of **Critical ICT Third-Party Provider (CTPP)** represents the regulatory realization that the "too big to fail" doctrine has migrated from the balance sheets of global banks to the server racks of cloud hyperscalers. ## Defining the CTPP: The "Systemic" Cloud Under the European Union’s [Digital Operational Resilience Act (DORA)](https://eur-lex.europa.eu/eli/reg/2022/2554/oj), a CTPP is an Information and Communication Technology (ICT) provider whose services are so fundamental to the financial sector that their disruption would jeopardize the stability of the entire financial system. As established in Article 31 of DORA, the designation is determined by the **European Supervisory Authorities (ESAs)**—comprising the EBA, ESMA, and EIOPA—based on criteria such as the systemic impact of a failure, the concentration of financial entities relying on the provider, and the difficulty of migrating to an alternative. Think of a CTPP not merely as a vendor, but as a "digital utility." Just as a city cannot function without its power grid, the modern financial ecosystem—built on the pillars of AWS, Microsoft Azure, and Google Cloud—cannot function without these "critical" nodes. ## The Paradigm Shift: From Indirect to Direct Oversight Historically, regulators managed third-party risk "indirectly" by holding banks accountable for their vendors. DORA shatters this model. CTPPs are now subject to a **Direct Oversight Framework**, where a Lead Overseer (one of the ESAs) has the power to: - Conduct on-site inspections and request any relevant information. - Issue recommendations to address vulnerabilities in the CTPP’s resilience posture. - Impose **periodic penalty payments** (up to 1% of the average daily worldwide turnover) for non-compliance. As the [European Banking Authority (EBA)](https://www.eba.europa.eu/activities/digital-finance/digital-operational-resilience) notes, this shift addresses the "concentration risk" that individual financial institutions are powerless to mitigate on their own. ## The Sovereignty Friction: A Clash of Perspectives The CTPP status introduces a profound tension between tech giants and sovereign regulators. While regulators view oversight as a necessary safeguard for public goods, many ICT providers—often headquartered outside the EU—view it as an unprecedented jurisdictional reach into non-financial commercial operations. > "The Lead Overseer should, in the exercise of its powers, ensure that the confidentiality of data and the security of the ICT third-party provider's systems are preserved." — [Recital 82, DORA Regulation](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32022R2554) Legal scholars argue whether the "recommendations" issued by Lead Overseers are truly non-binding. If a bank is prohibited from using a CTPP that fails to follow an ESA recommendation, the "recommendation" functions as a *de facto* command, effectively placing the ESA in the position of a global CTO for the financial industry. ## Compelling Questions for Further Exploration The rise of the CTPP designation raises critical questions about the future of innovation: 1. **The Homogeneity Trap:** Does forcing all CTPPs to meet the same resilience standards inadvertently create a "single point of failure" by homogenizing the very technologies meant to provide redundancy? 2. **Market Exit:** Could the regulatory burden of CTPP status lead niche, highly innovative providers to exit the EU financial market entirely to avoid the Lead Overseer’s grasp? 3. **Global Alignment:** How will the EU’s CTPP framework interact with the [Financial Stability Board (FSB)](https://www.fsb.org/work-of-the-fsb/financial-innovation-and-structural-change/cyber-and-operational-resilience/)’s proposed international standards for third-party risk management?

While the "Cloud Hyperscalers" (AWS, Google, Microsoft) are the most visible targets of the CTPP designation, the scope of systemic risk extends into the "deep plumbing" of finance. The designation does not merely follow revenue; it follows the **non-substitutable functionality** of the digital supply chain. If a cloud provider is the electrical grid, these other entities are the transformers and high-tension wires without which the grid collapses. ## Beyond the Cloud: The Archetypal CTPPs The [European Supervisory Authorities (ESAs)](https://www.esma.europa.eu/press-news/esma-news/esas-publish-technical-advice-designation-criteria-and-fees-critical-ict-third) use specific quantitative and qualitative metrics to identify who qualifies. Beyond generic compute, CTPP status is likely to capture: 1. **Financial Market Data Monoliths:** Entities like Bloomberg or LSEG (Refinitiv). If their data feeds—integrated via APIs into automated trading algorithms—freeze, market liquidity can vanish in milliseconds. 2. **Specialized Connectivity Providers:** This includes the [SWIFT network](https://www.swift.com/about-us/legal/compliance/oversight), which, while already under central bank oversight, represents the pinnacle of ICT concentration. 3. **Core Banking Software-as-a-Service (SaaS):** Providers like Temenos or Mambu. For many mid-tier banks, these firms do not just host data; they *are* the bank’s operating system. 4. **Hardware and Cybersecurity Enclaves:** Companies providing specialized Distributed Denial of Service (DDoS) mitigation (e.g., Cloudflare) or Hardware Security Modules (HSMs) used for cryptographic signing in payment processing. ## The Geography of Governance: The "EU Subsidiary" Mandate The "where" of CTPPs is often a point of legal friction. Under **Article 31(12) of DORA**, any ICT provider designated as "critical" that provides services to EU financial entities from a third country (e.g., the US or UK) must establish a **subsidiary within the Union** within 12 months. > "To ensure effective oversight, ICT third-party providers... should be required to have a legal presence in the Union. This is essential to ensure that the Lead Overseer can perform its duties." — [ESA Final Report on Technical Advice](https://www.eba.europa.eu/sites/default/documents/files/document_library/Publications/Reports/2023/1063061/Joint%20ESA%20Technical%20Advice%20on%20DORA%20designation%20criteria%20and%20oversight%20fees.pdf) This creates a "regulatory gravitational pull." A provider headquartered in Silicon Valley becomes, for legal purposes, an EU-resident entity. This mandate prevents "jurisdictional arbitrage," ensuring the Lead Overseer has a physical point of entry for inspections and a legal person against whom to enforce the 1% turnover penalties. ## The Substitutability Metric: The "N-1" Problem The most critical "Who" is determined by the **Substitutability Metric**. The ESAs analyze whether a financial entity could migrate to another provider without "significant effort." As the [Financial Stability Board (FSB)](https://www.fsb.org/2023/06/enhancing-third-party-risk-management-and-oversight-discussion-paper/) notes in its work on third-party risk, some services are "highly bespoke," creating a "lock-in" that elevates the provider to CTPP status regardless of their actual size. If a niche AI firm provides a proprietary credit-scoring model used by 40% of Eurozone lenders, that firm is "critical," even if its global turnover is a fraction of a hyperscaler's. This forces the industry to confront a counterintuitive reality: **vulnerability is often found in the most specialized, least known corners of the tech stack.**

Euronet Worldwide, Inc. exists at the volatile intersection of physical cash infrastructure and digital payment rails, making it a "hidden" candidate for Critical Third-Party Provider (CTPP) status under the **Digital Operational Resilience Act (DORA)**. While hyperscalers manage the abstract compute, Euronet manages the "Last Mile" of liquidity through its REN Foundation and global ATM/POS networks. Its status depends on whether the [European Supervisory Authorities (ESAs)](https://www.esma.europa.eu/press-news/esma-news/esas-publish-technical-advice-designation-criteria-and-fees-critical-ict-third) view it as a regulated financial entity or a critical ICT service provider. ## The REN Platform: Software as Infrastructure The strongest case for Euronet’s designation lies in its **REN ecosystem**. Unlike traditional ATM operators, Euronet has pivoted to a cloud-native architectural stack that processes complex transactions for third-party banks. This moves Euronet from a mere "vendor" to a "core service provider." > "The REN Foundation allows for the integration of disparate payment systems into a single, cohesive processing environment... providing the scalability and flexibility required by modern financial institutions." — [Euronet 2023 Annual Report](https://ir.euronetworldwide.com/financial-information/annual-reports) If a significant number of EU credit institutions rely on REN for their domestic switching or cross-border processing, Euronet triggers the **Substitutability Metric**. Replacing a core payment switch is a multi-year "heart transplant" operation; under DORA's Article 31, such "lock-in" is a primary indicator of criticality. ## The Exemption Trap: Entity vs. Service A counterintuitive tension exists in DORA’s scoping. Under **Article 2**, DORA applies to both financial entities and ICT third-party service providers. However, if Euronet provides services primarily through its regulated subsidiaries (like Ria or XE), it may be treated as a **Financial Entity** rather than a CTPP. The [European Banking Authority (EBA)](https://www.eba.europa.eu/regulation-and-policy/operational-resilience) distinguishes between: 1. **Intra-group services:** Regulated entities providing services to their own branches. 2. **External ICT services:** A tech firm (like Euronet’s software arm) providing infrastructure to *other* banks. If Euronet’s REN platform is sold as a white-label SaaS to external Eurozone banks, it transcends its status as a "money transfer firm" and enters the CTPP "Gravitational Pull." ## The "Critical Node" in Cross-Border Liquidity The [Financial Stability Board (FSB)](https://www.fsb.org/2023/06/enhancing-third-party-risk-management-and-oversight-discussion-paper/) emphasizes that systemic risk is often found in "concentrated nodes of connectivity." Euronet’s XE and Ria brands represent a massive share of the cross-border remittance market. In a crisis, the failure of Euronet's FX pricing engines or its settlement APIs would not just be a corporate failure; it would freeze the flow of capital to emerging markets and disrupt the daily operations of millions of EU citizens. This **high-intensity transaction volume** makes it "close" to CTPP status, as it satisfies the quantitative threshold of impacting the "stability of the financial system of the Union."

If DORA identifies the "what" of operational resilience, the proposed **Payment Services Regulation (PSR)** and **Third Payment Services Directive (PSD3)** redefine the "who" by granting entities like Euronet direct access to the central nervous system of European finance: the payment settlement systems. This shift transforms Euronet from a peripheral "convenience node" into a direct peer of commercial banks, complicating its DORA status. ## The Disintermediation of Systemic Risk The most significant shift under the [European Commission’s June 2023 Proposal](https://finance.ec.europa.eu/publications/modernising-payment-services-and-opening-financial-services-data-0_en) is the amendment to the **Settlement Finality Directive (SFD)**. Currently, non-bank payment institutions (PIs) like Euronet must rely on commercial banks to access payment systems. The PSR mandates that payment system operators provide direct access to PIs, subject to certain safeguards. > "To ensure a level playing field... payment institutions should be allowed to participate in payment systems, including those designated under Directive 98/26/EC, provided that they satisfy the requirements for participation." — [PSR Proposal, Recital 35](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52023PC0367) This "Level Playing Field" paradox means Euronet may soon settle transactions directly at the central bank level. By removing the commercial bank intermediary, Euronet eliminates a layer of oversight while simultaneously becoming a **direct point of failure** for the settlement layer. Under this framework, the "substitutability" argument weakens; if Euronet fails while holding a direct settlement account, the resulting liquidity gap cannot be easily patched by a competitor's API. ## REN as a Regulated "Gatekeeper" While the Foundation noted Euronet’s status as a Financial Entity (FE) might exempt it from CTPP designation, PSD3 introduces a more granular categorization of **Technical Service Providers (TSPs)**. Under PSR, TSPs that provide "gatekeeper" services—specifically those managing the technical infrastructure for Strong Customer Authentication (SCA)—face heightened scrutiny. If Euronet’s REN platform is used by third-party banks to meet the stricter PSR requirements for **fraud monitoring and IBAN-name matching (Confirmation of Payee)**, REN ceases to be a modular software choice. It becomes a regulatory compliance engine. As PSD3 tightens the performance requirements for APIs, Euronet’s software arm may find itself caught in a "Regulatory Pincer": 1. **As a PI:** It is an FE under DORA Article 2. 2. **As a TSP for other banks:** It provides "critical ICT services" that are indispensable for those banks to remain PSR-compliant. ## The Liability Shift and Resilience Debt PSR introduces stricter liability for technical failures, particularly regarding "spoofing" and the failure of TSPs to prevent unauthorized access. This creates an **Economic Criticality** that mirrors DORA’s operational focus. > "Where a technical service provider... fails to provide the services necessary for the payment service provider to comply with the requirements... it shall be liable for the financial loss caused." — [PSR Proposal, Article 57](https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52023PC0367) By codifying the liability of technical providers, the PSR effectively "shadow-designates" REN as a critical node. If a failure in Euronet’s switching logic leads to a mass-scale breach of PSR-mandated fraud checks across multiple client banks, the systemic impact would be measured not in "unfilled ATMs," but in a collapse of the **digital trust architecture** of the Union. This makes the DORA designation debate academic; Euronet becomes critical because the law makes it legally and financially inseparable from the banks it serves.