{"id":"pace-act","title":"PACE Act","content":"The Payments Access and Consumer Efficiency Act (PACE Act) is a bipartisan bill introduced on April 21, 2026, that proposes a new pathway for qualified nonbank payment providers to access Federal Reserve payment services. Sponsored by U.S. Representatives Young Kim (R–CA) and Sam Liccardo (D–CA), the bill aims to make everyday payments faster, cheaper, and more reliable by modernizing access to core payment infrastructure while establishing consumer protection and federal supervisory standards for participating firms. Media coverage and sponsor statements place particular emphasis on potential benefits for fintech and digital-asset payment companies that currently rely on bank intermediaries to connect to Federal Reserve systems. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75) [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk)​\n\n## Overview\n\nThe PACE Act would open a statutory pathway for “qualified payment companies”—nonbank payment providers that meet defined standards—to obtain direct access to a subset of Federal Reserve payment rails. The bill’s core objectives are to lower consumer costs (for example, by reducing fees and intermediary spreads), speed up settlement for everyday transactions, and enhance reliability and competition in the U.S. payments ecosystem. Coverage identifies Fedwire, FedNow, and FedACH as the principal services contemplated for access, subject to risk controls and oversight. The proposal also includes prudential safeguards such as a full-reserve requirement for customer funds, segregation of customer assets, and risk-management and recordkeeping standards. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75) [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk)​\n\nNews reporting describes the bill as 23 pages in length and introduced with bipartisan backing as part of broader debates over the role of nonbank and digital-asset firms in U.S. payment networks. Supporters argue that permitting vetted, well-supervised nonbanks to access certain Federal Reserve services can reduce settlement friction and costs borne by consumers and small businesses. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Background and Context\n\nIn the United States, access to core Federal Reserve payment systems—such as Fedwire for high-value settlement, FedNow for instant payments, and FedACH for automated clearinghouse transactions—has historically been limited to depository institutions. Nonbank payment providers typically access these rails indirectly by partnering with banks, a structure that can introduce delays, additional costs, and operational dependencies. The PACE Act responds to longstanding calls from parts of the fintech sector for more direct, regulated pathways to the Federal Reserve’s services. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\nMedia coverage of the bill situates it within parallel policy discussions about “skinny master accounts,” a concept that contemplates constrained forms of Federal Reserve account access for nonbank entities under strict limitations. Reporting indicates that the PACE Act acknowledges this concept and preserves final decision-making authority for the Federal Reserve Board over such account applications. This framing reflects active debate over how to balance innovation and competition with safeguards for operational integrity and financial stability. [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI) [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Legislative History\n\nThe PACE Act was introduced in the U.S. House of Representatives on April 21, 2026, by Representatives Young Kim and Sam Liccardo. On the day of introduction, both the sponsors and multiple industry groups issued public statements of support, and several media outlets published analyses describing the bill’s objectives and potential implications. As of introduction, the bill’s number, committee referrals, and subsequent procedural steps were not publicly detailed in the materials cited here. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk) [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI)\n\n## Purpose and Policy Goals\n\nThe sponsors frame the PACE Act as a consumer- and competition-focused modernization of the U.S. payments system. By enabling direct access to designated Federal Reserve services for qualified nonbanks under a uniform federal framework, the bill aims to:\n\n* Shorten settlement times for everyday payments.\n* Lower or eliminate intermediary fees and processing costs that are often passed on to consumers.\n* Enhance reliability and resilience by reducing dependence on multiple third-party links.\n* Encourage competition and innovation among payment providers, including digital-asset and fintech firms that meet rigorous standards.\n\nIn sponsor materials, Rep. Young Kim states that the bill is intended to fix “outdated payment infrastructure” so Americans do not have to wait days or pay extra to move their own money. Supporters from industry associations similarly describe the proposal as a responsible route to faster and less expensive payments, contingent on strong oversight and consumer protections. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk) [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Key Provisions\n\n### Direct Access to Specified Federal Reserve Services\n\nThe PACE Act would establish a pathway for qualified nonbank payment providers to access certain Federal Reserve payment systems. Reporting identifies three principal services:\n\n* Fedwire: The high-value funds-transfer service used for real-time gross settlement.\n* FedNow: The instant payment service designed to facilitate 24/7/365 real-time payments.\n* FedACH: The Federal Reserve’s automated clearinghouse processing service.\n\nThis access would be conditioned on qualification and ongoing compliance, with the Federal Reserve maintaining its usual risk controls and operational oversight as applicable. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n### Optional Federal Supervisory Framework\n\nThe proposal contemplates an optional federal supervisory regime for eligible nonbank payment companies administered by the Office of the Comptroller of the Currency (OCC). Under this model, companies opting in would be held to federal standards for safety, soundness, consumer protection, and operational risk management as a condition of access. The OCC’s role would include examination and enforcement consistent with the framework created by the statute, in coordination with applicable Federal Reserve requirements tied to account or service access. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n### Streamlined Federal Registration and Review Deadlines\n\nThe PACE Act envisions a federal registration process for qualified payment companies featuring clear standards and government review timelines. Sponsors characterize this as a means to reduce duplicative or protracted approvals across jurisdictions, especially for large multi-state payment firms that already hold numerous state licenses. By regularizing the process at the federal level, the bill seeks to create a more predictable on-ramp to Fed services for entities that meet the statutory and supervisory criteria. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk)​\n\n### Full-Reserve and Segregation Requirements\n\nTo mitigate customer-fund risk, the bill would require participating payment firms to maintain 1:1 reserves for customer balances and to segregate those funds from company assets. These provisions are designed to minimize the risk that consumer funds are commingled or rehypothecated, and to simplify customer recovery in the event of a firm’s failure. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75) [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk)​\n\n### Insolvency and Consumer Priority\n\nSponsor materials describe consumer-first protections in failure scenarios, including prioritization of consumer claims over other creditors. Combined with full-reserve and segregation requirements, these measures are intended to enhance consumer recourse and reduce loss severity if a registered payment company becomes insolvent. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk)​\n\n### Risk-Management and Recordkeeping Standards\n\nParticipating companies would need to demonstrate and maintain robust risk-management frameworks, compliance controls, and recordkeeping practices consistent with federal supervisory expectations. These standards are framed as prerequisites for access and as ongoing obligations subject to examination. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Eligibility and “Qualified Payment Companies”\n\nThe PACE Act targets nonbank payment providers that offer money transmission or similar services but are not depository institutions. Reporting indicates that a practical benchmark for eligibility may include holding a substantial number of state money-transmitter licenses. Sponsor materials specifically reference a threshold of 40 or more state licenses as a criterion for electing into the federal framework under OCC supervision. The exact statutory definition of a “qualified payment company,” along with any asset, volume, operational, or compliance thresholds, would be detailed in the bill text and subsequent regulatory guidance. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75) [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk)\n\n## Account Structure and “Skinny Master Accounts”\n\nCoverage notes that the bill acknowledges the concept of “skinny master accounts”—a constrained form of Federal Reserve account access—and clarifies that the Federal Reserve Board retains final authority over applications for such access. The intent is to provide a standardized but carefully controlled mechanism for nonbank entities to interface with the Federal Reserve’s services, subject to the Fed’s risk criteria and discretion. The exact account architecture and operational parameters would depend on both statutory language and the Federal Reserve’s implementation policies. [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI) [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Relationship to Digital-Asset Payment Firms\n\nMedia analyses highlight the PACE Act’s potential implications for regulated digital-asset payment companies, including stablecoin-focused firms, that could seek direct access to Federal Reserve services if they meet the qualification standards. Outlets specifically referenced U.S.-based companies such as [Ripple](https://iq.wiki/wiki/ripple-labs) and [Circle](https://iq.wiki/wiki/circle) as potential beneficiaries under the bill’s framework, while underscoring that eligibility would depend on statutory criteria and supervisory approvals. This reflects a broader trend of integrating blockchain-enabled payment solutions into mainstream payment pathways, contingent on regulatory oversight and consumer protections. [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI) [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\nSome coverage also noted that at the time of reporting, a crypto-affiliated institution had been identified in media as having a form of access to Federal Reserve rails, illustrating both the demand for access pathways and the sensitivity of such arrangements. This context underscores why the PACE Act pairs potential access with full-reserve, segregation, and supervisory requirements. [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI)​\n\n## Support and Endorsements\n\nThe bill drew public endorsements from several trade associations and industry groups upon introduction. Organizations praising the proposal included:\n\n* Financial Technology Association\n* Blockchain Association\n* The Digital Chamber\n* Crypto Council for Innovation\n\nIn public statements, these groups emphasized competition, consumer benefits, and responsible modernization of payments infrastructure. For example, supporters described the bill as an “important step forward” for enabling qualified nonbank providers to deliver faster and more cost-effective payment services while operating under strong oversight. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk) [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Opposition and Concerns\n\nWhile introductory materials emphasized bipartisan support and industry endorsements, media reporting also referenced opposition from segments of the banking industry. Critics have raised concerns about operational risk, the potential for fraud, and broader financial-stability implications of granting nonbank and crypto-affiliated firms access to Federal Reserve services. A statement attributed to the Colorado Bankers Association warned that “skinny master accounts” could create an “expedited fraud” channel if not carefully controlled. These concerns suggest that debate around the PACE Act would likely focus on the robustness of supervisory standards and the operational safeguards governing nonbank access. [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI)​\n\nMore generally, open questions include how the PACE framework would interact with existing state money-transmitter laws, how responsibilities would be divided among the Federal Reserve, OCC, and other federal and state regulators, and how to calibrate risk controls for nonbank participants using real-time and high-value settlement systems. These issues are typically central to policy deliberations about opening central banking services to a broader range of entities. [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)​\n\n## Implementation Mechanics\n\nUnder the PACE framework as described, implementation would involve several coordinated steps:\n\n* Federal registration under defined standards, with explicit review timelines to provide predictability for applicants.\n* OCC-administered supervision for companies that opt into the federal framework, including examinations and enforcement consistent with prudential and consumer-protection aims.\n* Federal Reserve evaluation of applications for account access, including the possibility of “skinny master accounts,” with the Fed Board retaining final authority over approvals and risk parameters.\n* Ongoing compliance with full-reserve, segregation, and risk-management requirements, along with recordkeeping sufficient to support audits, examinations, and consumer recourse.\n\nThe specifics of each element—such as the volume thresholds, types of permissible activities, and exact services covered—would be clarified in the bill text and subsequent regulatory guidance and rulemaking. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk) [\\[3\\]](#cite-id-tLNqdPeYWAdDUYRI)​\n\n## Consumer Protections\n\nThe bill’s consumer-protection architecture centers on:\n\n* Full reserve backing for customer funds at a 1:1 ratio.\n* Segregation of these funds from company assets to prevent commingling.\n* Restrictions on reuse of consumer funds that could elevate loss risk.\n* Priority for consumers to recover funds if a provider fails.\n\nProponents argue these measures, combined with federal supervision, materially reduce consumer harm risks traditionally cited in opposition to nonbank access. Enforcement would rely on examination authority and clear standards for recordkeeping and disclosures to support audits and consumer claims. [\\[2\\]](#cite-id-b3sdlPcjjHcnbGUk) [\\[1\\]](#cite-id-AehjoVKyMTtgZo75)","summary":"The Payments Access & Consumer Efficiency (PACE) Act, a bipartisan bill introduced Apr 21, 2026 by Reps Young Kim and Sam Liccardo, lets qualified nonbank payment firms access Fedwire, FedNow and FedACH under OCC oversight with 1:1 reserves and safeguards","images":[{"id":"QmeEybFkCxevtvTMZqC325YKy1KVrR2LH8CmUPChx6V66T","type":"image/jpeg, image/png"}],"categories":[{"id":"organizations","title":"organizations"}],"tags":[{"id":"Regulations"},{"id":"Government"}],"media":[{"id":"QmcwJJTShdYgZzcSGsQRcRo6WLzh19wSUxL55DXPwr3cPd","type":"GALLERY","source":"IPFS_IMG"},{"id":"QmRGBUH3s2YrJBp6MQKQDBN58LT5fEJRCAFPdwixFdnEPX","type":"GALLERY","source":"IPFS_IMG"},{"id":"QmWs1LvamGbcUZQ9yaqwBpftgxGz2AQJmXzgv7XTUaHQvq","type":"GALLERY","source":"IPFS_IMG"},{"id":"QmSbPGxXgzQ9YihVsAgAaQNWUkudzHeoTs1f74W6cErssm","type":"GALLERY","source":"IPFS_IMG"}],"metadata":[{"id":"references","value":"[\n {\n \"id\": \"AehjoVKyMTtgZo75\",\n \"url\": \"https://www.theblock.co/post/398319/bipartisan-pace-act-looks-open-fed-payment-rails-nonbanks-crypto-support?utm\\\\_source=twitter\\\\&utm\\\\_medium=social\",\n \"description\": \"The Block report\",\n \"timestamp\": 1776792173312\n },\n {\n \"id\": \"b3sdlPcjjHcnbGUk\",\n \"url\": \"https://youngkim.house.gov/2026/04/21/rep-kim-introduces-pace-act-to-make-everyday-payments-faster-cheaper-and-more-efficient-for-americans/\",\n \"description\": \"Rep. Young Kim press release\",\n \"timestamp\": 1776792173312\n },\n {\n \"id\": \"tLNqdPeYWAdDUYRI\",\n \"url\": \"https://coingape.com/u-s-reps-unveil-bipartisan-crypto-bill-that-enables-ripple-circle-access-feds-payment-rails/\",\n \"description\": \"CoinGape coverage\",\n \"timestamp\": 1776792173312\n }\n]"},{"id":"references","value":"https://www.theblock.co/post/398319/bipartisan-pace-act-looks-open-fed-payment-rails-nonbanks-crypto-support"},{"id":"commit-message","value":"\"Added PACE Act summary on Fed access for nonbank payment providers\""}],"events":[{"id":"c8dc5a4a-8fcb-4c03-9178-ca0d67971842","date":"2026-04","title":"PACE Act introduced in the U.S. House","type":"CREATED","description":"Reps. Young Kim and Sam Liccardo unveil the bipartisan PACE Act to broaden qualified nonbank access to Federal Reserve payment services.","link":"https://youngkim.house.gov/2026/04/21/rep-kim-introduces-pace-act-to-make-everyday-payments-faster-cheaper-and-more-efficient-for-americans/","multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"6e35d3ac-1d22-4e42-92e9-6abe0df13f23","date":"2026-04","title":"Industry groups endorse PACE Act","type":"DEFAULT","description":"Fintech and crypto trade groups, including the Blockchain Association, CCI and others, publicly support the bill’s goals.","link":"https://liccardo.house.gov/media/press-releases/reps-liccardo-and-kim-introduce-bipartisan-pace-act-make-everyday-payments","multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null},{"id":"e4ad5121-38eb-4ae5-bab3-605902159004","date":"2026-04","title":"Media highlight Fed rails access for nonbanks","type":"DEFAULT","description":"Coverage notes the bill could enable qualified firms, including crypto payment companies, to seek access to Fedwire, FedNow and FedACH.","link":"https://www.theblock.co/post/398319/bipartisan-pace-act-looks-open-fed-payment-rails-nonbanks-crypto-support","multiDateStart":null,"multiDateEnd":null,"continent":null,"country":null}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"operator":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"language":"en","version":1,"linkedWikis":{"blockchains":[],"founders":[],"speakers":[]}}