What Is Fintech & Transfers?
Fintech covers the technology-driven transformation of financial services — from digital wallets and neobanks to real-time payment rails, open banking APIs, and cross-border transfer infrastructure that moves trillions globally.
📂 Explore by Sub-Topic
Digital Payments
Contactless, wallets, QR codes, tokenization, card-present
Cross-Border Transfers
SWIFT, remittances, international money movement
Neobanks & Banking-as-a-Service
Digital banks, BaaS, embedded finance, challenger banks
Open Banking
APIs, data sharing, account-to-account payments
Payment Rails & Infrastructure
Real-time rails, ISO 20022, gateways, acquiring banks
Emerging Fintech
BNPL, biometrics, embedded payments, Stripe case study
Related Finance Sub-Topics
Latest Fintech & Transfers Articles
Recently published expert guides from the Fintech & Transfers hub.
The Fintech Charter Boom: Why Fintechs Are Racing to Become Banks in 2026
More than 30 fintechs, neobanks and non-bank lenders are seeking bank or industrial loan charters in 2026, including PayPal, Affirm, Stellantis and World Liberty Financial. A charter removes reliance on a sponsor bank, lowers funding costs and cuts compliance risk — but it also brings full prudential regulation, capital requirements and years of review. For finance and treasury teams, the wave signals which fintech partners are becoming more durable, and which sponsor-bank-dependent platforms carry more counterparty risk.
A record number of financial technology companies are applying to become banks in 2026, and a fintech bank charter is now one of the clearest signals of which platforms are built to last. Federal regulators are processing an unprecedented pipeline of de novo bank and industrial loan company (ILC) applications from neobanks, payment platforms, auto lenders and even a cryptocurrency venture tied to the Trump family. This guide explains why the rush is happening now, what a charter actually changes, and what it means for businesses that rely on fintech partners for banking, payments or lending.
This guide provides general information, not legal or regulatory advice. Bank chartering rules vary by regulator and jurisdiction; consult qualified counsel before relying on any fintech's regulatory status.
What is a fintech bank charter?
A license — full bank, trust bank or industrial loan company (ILC) — that lets a fintech hold deposits and lend directly, without routing transactions through a sponsor bank.
Why is 2026 different?
Over 30 companies are in the pipeline, including PayPal, Affirm, Stellantis, Nissan and World Liberty Financial, more than in any prior year on record.
What should businesses do?
Treat a partner's chartering status as a due-diligence signal: chartered institutions carry direct federal oversight and deposit insurance that sponsor-bank arrangements do not guarantee.
What is driving the fintech bank charter boom in 2026?
The 2026 surge is driven by regulators approving more charters faster, and by fintechs wanting to escape costly sponsor-bank partnerships after years of enforcement actions against that model. Over 30 neobanks, lenders, payment firms and digital-asset companies are now in the federal charter pipeline.
Banking Dive and American Banker both describe an "explosion" of charter applications processed by the OCC, FDIC and state regulators through 2026. The applicant list spans consumer fintech (rent-payment platform Flex, buy-now-pay-later leader Affirm, payments giant PayPal), captive auto lenders (Ford Credit Bank, GM Financial Bank, Stellantis Bank, Nissan), a wealth manager (Edward Jones Bank) and even World Liberty Financial, the cryptocurrency platform associated with the Trump family, which received conditional trust-charter approval. Dutch neobank Bunq, by contrast, had its US charter application denied — a reminder that approval is not automatic.
Why do fintechs want to become chartered banks instead of using sponsor banks?
Fintechs pursue charters to cut the cost of routing deposits and payments through a partner bank, to reduce dependence on a single sponsor's risk appetite, and to gain direct access to payment rails and deposit insurance. A charter converts a fragile partnership into a regulated, standalone banking business.
For most of the last decade, non-bank fintechs relied on "bank-as-a-service" arrangements: a chartered sponsor bank held the actual deposits and licenses, while the fintech built the app and customer relationship. That model has come under sustained regulatory pressure. The Federal Reserve's own September 2026 press releases show agencies actively tightening oversight of this arrangement — including new proposed third-party risk-management guidance and a statement on how community banks should engage with core service providers, alongside a separate move to ease exam burdens for smaller, well-run community banks. Sponsor banks that mismanaged fintech partnerships have faced consent orders and enforcement actions in the past two years, and fintechs increasingly see chartering as the more durable, lower-risk long-term structure.
What is the difference between a full bank charter and an industrial loan company (ILC) charter?
A full national or state bank charter permits deposit-taking and lending under comprehensive prudential regulation, typically with Federal Reserve oversight of any parent company. An ILC charter, chartered mainly through Utah, offers FDIC-insured deposit-taking and lending without subjecting the parent company to full bank holding company regulation.
The ILC route has become the preferred path for commercial parents that do not want to become regulated bank holding companies — notably auto manufacturers' finance arms. Since January 2026, the FDIC has conditionally approved ILC deposit insurance applications from Ford Credit Bank, GM Financial Bank, Edward Jones Bank and Stellantis Bank, with additional applications filed by Nissan, OneMain and Affirm. Rent-payment fintech Flex filed a similar ILC application with the FDIC and the Utah Department of Financial Institutions in 2026. Regulatory law firms including Freshfields and Goodwin describe this as a structural shift in "the regulatory perimeter" for fintechs, payments companies and industrial parents alike.
How long does it take to get a bank charter approved in 2026?
Approval timelines vary widely and can run well over six months even for conditional approval. World Liberty Trust Company's conditional approval took 221 days, while Bunq's denial took 212 days — illustrating that a long review period does not by itself predict the outcome.
Applicants typically clear several sequential hurdles: a charter approval from the primary regulator (OCC for national banks and trust banks, state regulators for ILCs), a separate deposit insurance application to the FDIC, and — for companies that will operate as bank holding companies — Federal Reserve approval of the holding company structure. Each stage involves capital adequacy review, business-plan scrutiny, management background checks and, increasingly, cybersecurity and anti-money-laundering readiness assessments. Experts quoted by Banking Dive expect the pipeline to keep growing through the rest of 2026 as more fintechs conclude that regulatory certainty is worth the wait.
What does the fintech charter trend mean for the wider finance and payments industry?
The trend signals a maturing fintech sector where scale players are converting temporary bank partnerships into permanent regulatory infrastructure. It also means more of the payments and lending stack is moving under direct federal supervision rather than indirect oversight through sponsor banks.
This has knock-on effects across the industry covered in Kurums' Fintech & Transfers hub. As stablecoin issuers pursue trust-bank charters for dollar-backed tokens — Sony Bank's OCC-approved trust subsidiary is one recent example — the line between "fintech" and "bank" keeps narrowing, a shift already visible in Kurums' stablecoin regulation guide. At the same time, the sponsor-bank model itself is under renewed scrutiny following a string of consent orders, a dynamic explored in Kurums' coverage of 2026 sponsor-bank consent orders. Search interest in "bank charter" has spiked around specific applicants — Google Trends shows "world liberty financial bank charter" as the single largest related query in the category this month — suggesting public and investor attention is now tracking individual filings rather than the trend in the abstract.
How should a business evaluate a chartered fintech versus a sponsor-bank fintech partner?
Businesses should weigh three factors: deposit insurance clarity, regulatory accountability and continuity risk. A chartered fintech carries its own federal or state banking license, while a sponsor-bank fintech's stability depends on a third-party relationship that can be terminated or restructured with little customer warning.
In practice, that means checking whether customer funds sit in FDIC-insured accounts at the fintech itself or are "pass-through" insured via a partner bank, reviewing whether the sponsor bank has any recent consent orders or enforcement history, and building a contingency plan in case a banking partnership is unwound — as has happened abruptly at several sponsor-bank fintechs in the past two years. Finance and procurement teams that formalize this review as part of vendor onboarding avoid being surprised by a sudden loss of banking services.
Frequently Asked Questions
Is a fintech with a bank charter safer than one using a sponsor bank?
Generally yes for continuity and regulatory accountability, because the fintech itself is directly supervised and insured rather than depending on a third-party bank relationship that can change.
Which companies received bank or ILC charters in 2026?
Approvals and pending applications in 2026 include Ford Credit Bank, GM Financial Bank, Edward Jones Bank, Stellantis Bank, Sony Bank's trust subsidiary and World Liberty Trust Company, among more than 30 applicants overall.
What is an industrial loan company (ILC)?
An ILC is an FDIC-insured lender, chartered mainly in Utah, that lets a commercial parent take deposits and make loans without becoming a regulated bank holding company.
Does a bank charter application always get approved?
No. Denials happen — Dutch neobank Bunq's 2026 US charter application was rejected after a 212-day review, showing regulators still apply meaningful scrutiny.
How does this affect businesses that use fintech payment or lending platforms?
It changes counterparty risk. A charter gives businesses clearer recourse and deposit protection, so vendor due diligence should now include a partner's chartering status alongside its pricing and features.
Last updated: September 13, 2026. Sources: American Banker, Banking Dive, Goodwin, Freshfields, Federal Reserve Board press releases.
Agentic Payments Arrive in Production: What Blik’s First AI-Agent Transaction and the New Know-Your-Agent Framework Mean for Finance Teams
Last Updated: September 11, 2026
By the Kurums.com Finance Desk
Agentic payments moved from pilot to production this week. Polish payment network Blik confirmed it processed its first agentic payment transaction on September 11, 2026, where a user authorized an AI agent to find a product and pay for it automatically once available. A day earlier, Ant International, Visa, and Mastercard announced a joint “Know-Your-Agent” (KYA) framework to identify and vet AI agents across card networks and wallets. The catch: new Visa research shows only 23% of US consumers trust generative AI to handle payments on their behalf, and a fresh $7.3 million funding round for agentic governance-risk-compliance platform HelmGuard signals that risk teams are racing to catch up with the technology, not ahead of it.
What Just Happened With Agentic Payments?
Blik, Poland’s dominant mobile payment network, confirmed it has processed the first agentic payment transaction on its rails: a user pre-authorized an AI agent to search for a specific product and complete payment automatically the moment it became available.
This is a meaningful shift from earlier “AI shopping assistant” demos, most of which stopped at generating a product shortlist or a draft cart that a human still had to check out manually. In Blik’s case, the agent held standing authorization to both search and pay within pre-set conditions, without a human confirming the final transaction. For finance teams, that single detail changes the risk conversation from “AI helps a customer shop” to “an autonomous system is initiating an actual movement of money,” which is a fundamentally different category of operational, fraud, and reconciliation risk.
What Is the Know-Your-Agent (KYA) Framework?
Know-Your-Agent, or KYA, is a proposed interoperability standard from Ant International, Visa, and Mastercard designed to identify, verify, and onboard AI agents consistently across card networks, digital wallets, and marketplaces.
KYA is explicitly modeled on Know-Your-Customer (KYC) obligations that banks already run for human account holders, extended to a non-human actor that can now initiate a payment. The framework aims to answer three questions before an agent is allowed to transact: which platform or company deployed this agent, what spending limits and merchant categories is it authorized for, and how can a receiving bank or merchant confirm the agent’s authorization has not been revoked or spoofed. Three of the largest players in global payments backing the same framework at the same time is a strong signal that card networks expect agent-initiated transactions to scale quickly enough that fragmented, network-by-network agent verification would become unworkable within a year or two.
Why Is Consumer Trust Still So Low?
New Visa research found that only 23% of US consumers trust generative AI to handle payment transactions on their behalf, even as AI-assisted shopping and product discovery adoption keeps climbing.
That gap between behavior and trust is the central tension finance and product teams are navigating right now. Consumers are comfortable letting an AI agent research, compare, and recommend, but handing over the actual payment step is a different psychological threshold — closer to handing someone a credit card than asking them for advice. Two things are likely driving the gap: consumers have limited visibility into what an agent is authorized to spend and on what, and there is no widely understood, bank-grade recourse process yet for an agent-initiated transaction gone wrong, comparable to a chargeback. Until frameworks like KYA translate into consumer-visible controls — spending caps a person can see and adjust, real-time transaction alerts, and a clear dispute path — trust is likely to keep lagging usage.
Why Is Funding Flowing Into Agentic GRC Platforms Right Now?
Agentic governance-risk-compliance platform HelmGuard raised $7.3 million in seed funding this week, using AI agents to automate governance, risk, and compliance monitoring inside regulated sectors including financial services.
The timing is not a coincidence. As agent-initiated payments move into production, compliance teams need tooling that can monitor agent behavior at the same speed the agents themselves operate — a rules engine or a quarterly audit cycle cannot catch a misbehaving agent that can execute thousands of transactions in an hour. Investors backing agentic GRC platforms are effectively betting that “AI to watch the AI” becomes a standard line item in compliance budgets over the next 12 to 24 months, in the same way fraud-detection software became a standard line item once card-not-present transactions scaled in the 2000s.
What Does This Mean for Finance and Treasury Teams?
Finance and treasury teams should treat agent-initiated payments as a new transaction category requiring its own authorization limits, monitoring, and reconciliation logic, rather than folding it into existing card-not-present or automated-payment policies.
Four practical steps are worth prioritizing now, ahead of broader adoption. First, define an explicit spending envelope for any AI agent a company authorizes to transact on its behalf — per-transaction cap, daily cap, and an approved merchant category list — the same discipline already applied to corporate card programs. Second, confirm with payment processors and card networks what agent-verification standard, such as KYA once finalized, they plan to support, since a business accepting agent-initiated payments will eventually need to distinguish a verified agent transaction from an unverified one at the point of sale. Third, build agent-specific fraud monitoring rather than assuming existing fraud models transfer cleanly, since an agent’s “normal” transaction pattern — rapid, narrow-purpose, time-triggered — looks anomalous under models trained on human purchasing behavior. Fourth, revisit dispute and chargeback procedures with the assumption that a customer may need to contest a transaction their own authorized agent initiated, which is a scenario most current dispute workflows were not built to handle.
What Changes for Accounting and Reconciliation?
Agent-initiated purchases complicate reconciliation because the transaction record no longer maps cleanly to a single human decision-maker, which is the assumption most expense and accounts-payable workflows are built on.
Finance teams running procurement or expense software should expect a near-term need to capture an additional data field alongside every transaction: which agent, under whose authorization, executed the purchase, and against which pre-approved policy. Without that field, an auditor reviewing a spend report a year from now has no way to distinguish a legitimate agent-initiated purchase from an anomaly, and internal controls built around “who approved this” break down when the answer is “an agent, acting on a standing policy” rather than a named employee. Finance software vendors serving mid-market and enterprise clients are the ones most likely to ship this capability first, since their customers face the compliance pressure earliest.
Key Takeaways on Agentic Payments
Is agentic payment technology now live for ordinary consumers? Partially — Blik’s transaction shows the capability is technically live on at least one major payment network, but broad consumer rollout is still gated by trust, regulatory clarity, and merchant readiness.
Does KYA replace existing KYC obligations for banks? No — KYA is designed to sit alongside KYC, adding a verification layer specifically for non-human agents acting on behalf of an already-verified human or business customer.
Are agentic payments currently regulated the same way as card payments? Not specifically — most jurisdictions are still applying existing card and payment-services rules to agent transactions rather than having agent-specific regulation in force.
Should a mid-size business start accepting agent-initiated payments now? Most payment and risk advisors recommend waiting for a published verification standard such as KYA to stabilize before actively marketing agent-payment acceptance, while still monitoring the space closely.
How Does This Fit Into the Broader Fintech Picture?
Agent-initiated payments are arriving alongside several other structural shifts in how money moves in 2026, and finance teams evaluating one typically need to evaluate all of them together.
Kurums.com’s guide to Embedded Finance Trends 2026 covers the broader restructuring of where and how payment functionality gets built into non-financial products, which is the same infrastructure layer agentic payments plug into. Businesses evaluating whether to hold reserves or settle in stablecoins alongside agent-payment rails should also see Stablecoins and Business Finance in 2026 for why adoption still trails infrastructure readiness — a dynamic that closely mirrors the consumer-trust gap in agentic payments. For the full range of banking, payments, and fintech regulation coverage, visit the Kurums.com Finance department hub.
Frequently Asked Questions About Agentic Payments
What is an agentic payment, exactly?
An agentic payment is a transaction initiated and completed by an AI agent acting under a standing authorization from a human or business, without a person approving that specific transaction at the moment it occurs.
How is this different from a recurring subscription payment?
A recurring payment executes a fixed amount on a fixed schedule that a person set in advance, while an agentic payment involves the agent making a real-time decision — what to buy, when, and sometimes from which merchant — within broader limits a person defined.
Who is liable if an AI agent makes an unauthorized or mistaken purchase?
Liability frameworks are still being worked out; card networks developing standards like KYA are expected to define clearer liability allocation between the agent platform, the card issuer, and the merchant over the next one to two years.
Can businesses block agentic payments from being used at checkout?
Yes, in most current implementations a merchant or payment processor can choose not to accept agent-initiated transactions, similar to how some merchants restrict certain card types today.
Is agentic GRC software only relevant to large financial institutions?
No — any business authorizing AI agents to transact on its behalf, including mid-size e-commerce and B2B companies, faces the same monitoring need, though enterprise financial institutions are adopting agentic GRC tooling fastest due to regulatory exposure.
Sources
Banking-as-a-Service Under the Microscope: What the 2026 Sponsor Bank Consent Orders Mean for Fintech Platforms
Regulators Are Naming the Bank, Not the Fintech
Kurums.com’s recent coverage of embedded finance’s regulatory reckoning outlined why sponsor banks and platforms both need to fix compliance gaps now. Two consent orders issued in the months since make the shape of that reckoning concrete: regulators are consistently naming the sponsor bank as the responsible party, even when the underlying failure originates in a fintech partner’s product or middleware.
Between 2022 and 2025, the FDIC, the Office of the Comptroller of the Currency, and the Federal Reserve issued consent orders against seven sponsor banks running Banking-as-a-Service programs. Two fresh cases in 2026 — Community Federal Savings Bank and Lineage Bank — confirm the pattern is accelerating rather than settling, and they carry specific lessons for every platform that depends on a sponsor-bank relationship to operate.
The OCC’s April 2026 consent order against Community Federal Savings Bank — an $866 million-asset, single-branch bank — cited BSA/AML failures tied directly to its rapid expansion into fintech-adjacent payment processing. Lineage Bank took a second FDIC consent order on June 24, 2026. In every case since 2022, the sponsor bank, not the fintech partner, is the named party, and regulators are now requiring independent testing and look-back reviews as standard remedies, not exceptional ones.
What Actually Happened at Community Federal Savings Bank?
The OCC made public an April 2026 consent order against Community Federal Savings Bank, a single-branch institution holding roughly $866 million in assets, over Bank Secrecy Act and anti-money-laundering failures tied directly to its rapid expansion into payment processing and fintech-adjacent business lines.
The core problem was a mismatch of scale: a small, single-branch bank took on the transaction-monitoring and customer-due-diligence burden of a national payments platform without proportionally scaling its BSA/AML infrastructure. That mismatch is common across the BaaS sector — sponsor banks are frequently small institutions chosen precisely because they are willing to move fast and share revenue with fintech partners, which is the same flexibility that leaves their compliance functions structurally under-resourced for the volume they end up processing.
Why Did Lineage Bank Receive a Second Consent Order?
Lineage Bank received a second FDIC consent order on June 24, 2026, indicating that remedial steps taken after its first enforcement action did not resolve the underlying compliance gaps regulators identified.
A second order is a materially different signal than a first one. It tells the market that a sponsor bank’s remediation plan — typically involving new compliance hires, updated policies, and third-party reviews — either wasn’t implemented with enough rigor or wasn’t sufficient to address the volume and complexity of the fintech programs running through it. For any platform whose sponsor bank has already taken one consent order, a second is now a realistic scenario to plan around, not a worst case to dismiss.
Who Is Actually Liable When a BaaS Program Fails Compliance?
The sponsor bank is named in every enforcement action to date, because regulators hold the chartered institution — not its fintech or middleware partners — ultimately responsible for Bank Secrecy Act, Know Your Customer, and consumer protection compliance across the program it sponsors.
This creates an asymmetry that catches fintech platforms off guard: the fintech designs the product experience and often builds the transaction-monitoring logic, but the bank absorbs the regulatory and reputational cost when that logic fails. Legal analysis of BaaS liability allocation increasingly frames this as a contractual gap rather than a regulatory one — indemnification clauses and audit rights in bank-fintech agreements often lag well behind the actual division of operational responsibility on the ground.
What Do Regulators Now Expect as Standard Remediation?
Regulators increasingly require an independent third-party risk management program with ongoing testing and look-back reviews as a standard consent-order remedy, not an unusual add-on reserved for the worst cases.
- Independent testing of BSA/AML controls, performed by a party with no role in building or operating the original program.
- Look-back reviews of historical transactions to identify suspicious activity that should have been flagged in real time but wasn’t.
- Formal third-party risk management programs that specifically govern the bank’s fintech relationships, not just its traditional vendor relationships.
- Documented escalation paths for when a fintech partner’s product changes in ways that affect the bank’s risk profile.
For platforms, this means sponsor banks are likely to push more compliance obligations — and more compliance cost — down to the fintech side of the relationship going forward, even absent a change in the underlying law.
How Should Fintech Platforms Assess Sponsor-Bank Risk Today?
Fintech platforms should treat their sponsor bank’s regulatory history as a direct operational risk to their own business continuity, since a bank losing its charter or exiting BaaS entirely can shut down a platform’s payment rails with little warning.
Public trackers such as sponsor-bank registers now catalog enforcement status and dates across roughly fifteen active US sponsor banks, giving platforms a way to benchmark their own bank’s regulatory standing against peers before signing a new agreement or renewing an existing one. Diversifying across more than one sponsor bank — long considered an operational nicety — is increasingly treated as a basic resilience requirement, comparable to how platforms already diversify payment processors.
What Should Platforms Negotiate Into Sponsor-Bank Agreements Now?
- Clear audit rights that let the platform see the bank’s BSA/AML testing results relevant to its own program, not just a summary attestation.
- Indemnification tied to actual operational responsibility, rather than boilerplate language that assumes the bank bears all regulatory risk regardless of who built the failing control.
- Advance notice provisions for any change in the bank’s enforcement status, so a platform isn’t blindsided by a public consent order affecting its own operations.
- A documented transition plan to a backup sponsor bank, tested before it is needed rather than improvised during a crisis.
How Does This Enforcement Pattern Compare to Earlier BaaS Cases?
The 2026 cases extend, rather than break from, a pattern established between 2022 and 2025, when the FDIC, OCC, and Federal Reserve issued consent orders against seven sponsor banks — but the remedies attached to the newer cases are noticeably more prescriptive than earlier ones.
Enforcement trackers covering the 2025–2026 period describe a marked shift toward more public and more specific consequences, including a Pennsylvania bank required to implement a third-party risk management program with independent testing and look-back reviews after being cited for unsafe BSA/AML practices. Earlier in the cycle, consent orders more often required general policy updates; the newer generation of orders names specific structural remedies — independent testing, documented look-back periods, formal third-party risk programs — that leave far less room for a bank to interpret compliance loosely.
What Does This Mean for Embedded Finance Growth Going Into 2027?
Tighter sponsor-bank oversight is likely to slow the pace of new BaaS launches without stopping embedded finance growth outright, since well-capitalized platforms with strong compliance functions can absorb the new diligence burden while thinner operators cannot.
The practical effect is consolidation. Sponsor banks facing regulatory pressure are becoming more selective about which fintech programs they onboard, favoring platforms that can demonstrate mature transaction-monitoring and KYC infrastructure of their own rather than depending entirely on the bank’s controls. For platforms currently shopping for a sponsor-bank relationship, this means slower onboarding timelines and more extensive due diligence than the market saw even two years ago — a cost that ultimately favors larger, better-capitalized embedded finance players over early-stage entrants.
Frequently Asked Questions
Can a fintech platform be directly fined in a BaaS enforcement action?
Direct fines have so far been issued against the sponsor bank, not the fintech partner, though the fintech can lose its banking relationship or face contractual liability under its agreement with the bank.
Why are small, single-branch banks common sponsor banks for large fintech platforms?
Smaller banks are often more willing to share revenue and move quickly on partnerships, but that same flexibility frequently means their compliance infrastructure is under-scaled for the transaction volume a national fintech program generates.
Why does a second consent order matter more than a first?
A second order signals that the bank’s initial remediation was insufficient, raising the likelihood of further restrictions, higher compliance costs, or an eventual exit from BaaS partnerships altogether.
Should platforms rely on a single sponsor bank?
Increasingly, no — diversifying across more than one sponsor bank is becoming standard practice to avoid a single enforcement action disrupting the platform’s payment operations entirely.
What Should Be on a Fintech Platform’s Compliance Checklist This Quarter?
Four concrete steps reduce a platform’s exposure to sudden sponsor-bank disruption without waiting for the next enforcement action to force the issue:
- Request the bank’s most recent exam findings summary, not just a compliance attestation letter, to gauge how close the relationship is to an enforcement event before it becomes public.
- Build transaction-monitoring capability that doesn’t depend entirely on the sponsor bank’s systems, so a bank-side control failure doesn’t automatically become the platform’s outage.
- Model the financial impact of a 90-day sponsor-bank transition, including customer communication and payment continuity, before it is needed under pressure.
- Track public consent-order trackers and sponsor-bank registers quarterly, treating a peer bank’s enforcement action as an early warning for shared risk factors across the sector.
None of these steps require waiting for new legislation. They reflect where regulators have already told the market they are looking, and platforms that act on that signal now will spend less time reacting to their sponsor bank’s next consent order than those that don’t.
Last Updated: August 29, 2026 · kurums.com Fintech Desk
Related reading: the 2026 fintech bank charter boom.
Embedded Finance’s Regulatory Reckoning: What Sponsor Banks and Platforms Must Fix Now
The Party Isn’t Over, But the Bill Just Arrived
Embedded finance — the practice of baking bank accounts, cards, lending, and payments directly into non-financial apps — has spent the last five years becoming one of the fastest-growing corners of financial services. E-commerce platforms issue their own cards. HR software processes payroll advances. Gig-economy apps offer instant payouts. Rideshare platforms extend fuel financing. None of these companies are banks, yet all of them now move money like one.
In August 2026, that convenience model is colliding with something it spent years avoiding: sustained regulatory scrutiny. U.S. banking regulators have sharply increased enforcement actions against the sponsor banks that sit quietly behind embedded finance products, and the fallout is starting to reshape how fintechs, platforms, and their banking partners structure these deals.
Sponsor banks now account for roughly a quarter of all FDIC and OCC formal enforcement actions. Three in four have already paid six-figure compliance penalties, and nearly a third are considering scaling back embedded finance programs altogether. For any company distributing financial products through a banking-as-a-service partner, liability no longer stops at the bank — it runs through the entire technology stack.
Why Regulators Turned Up the Heat
Embedded finance works through a three-layer structure that has always carried hidden regulatory risk:
- The platform — the e-commerce site, HR tool, or rideshare app that owns the customer relationship and puts a “financial product” in front of users who never think of themselves as bank customers.
- The middleware or banking-as-a-service (BaaS) provider — the technical layer that handles API connectivity, ledgering, KYC checks, and transaction routing between the platform and the bank.
- The sponsor bank — the chartered institution that actually holds the deposits, and with them, the full weight of federal banking law.
For years, sponsor banks treated this as a revenue line and largely outsourced oversight to their BaaS partners. Regulators have decided that arrangement no longer holds up. Since 2024, sponsor banks involved in embedded finance partnerships have been the subject of roughly a quarter of all FDIC formal enforcement actions and more than one in five OCC actions — a concentration far out of proportion to how small a slice of the banking sector these institutions represent. The policy shift accelerated further through 2025 as examiners applied continuous-monitoring standards the OCC first floated in 2024, treating a bank’s failure to actively supervise its fintech partners as a standalone violation, independent of whether consumers were actually harmed.
What the Numbers Say About the Damage
The financial and operational toll on sponsor banks is now well documented industry-wide:
- 75% of sponsor banks report losing more than $100,000 to compliance violations tied to their embedded finance partnerships.
- 80% say they struggle to monitor multiple fintech partners operating across different jurisdictions in real time.
- 29% are actively considering scaling back or shutting down their embedded finance programs entirely rather than absorb the compliance burden.
That last figure is the one worth sitting with. Embedded finance was supposed to be a low-cost distribution channel for banks — access to millions of platform users without the cost of building consumer-facing products. If nearly a third of sponsor banks are now weighing an exit, the economics of the entire model are being renegotiated in real time, and platforms that built revenue lines around “invisible banking” need a plan B.
Where the Compliance Gaps Actually Live
Regulators examining sponsor bank relationships in 2026 have converged on a handful of recurring failure points, and they are instructive for any business built on embedded finance rails:
1. Beneficial ownership blind spots
Accounts opened through embedded finance flows — particularly those with foreign beneficial owners — are receiving heightened attention. Examiners expect BSA/AML gap analyses that specifically test whether platforms and their BaaS providers can identify who ultimately controls an account, not just who opened it through an app.
2. Continuous monitoring, not point-in-time checks
The OCC’s 2024 standards, now actively enforced, require ongoing oversight of fintech partners rather than an annual review. Banks that treat partner risk assessments as a once-a-year exercise are being cited for supervisory failures even in the absence of a specific consumer complaint.
3. Liability that “disappears” between layers
The most common structural problem examiners flag is a contract that assumes someone else in the chain is responsible for a given control. When the platform assumes the BaaS provider handles KYC, and the BaaS provider assumes the bank handles suspicious activity monitoring, gaps open up that no single party is actively watching.
What This Means If You’re Not a Bank
Most companies reading this aren’t chartered banks, and many aren’t even fintechs in the traditional sense — they’re HR platforms with a payroll-advance feature, marketplaces with a buy-now-pay-later option, or B2B software with an embedded card program. That’s exactly the population regulators are now scrutinizing, because it’s where financial exposure has quietly accumulated outside the traditional banking perimeter.
Three practical shifts are worth making now, regardless of company size:
- Treat compliance as core architecture, not a vendor’s problem. If your product touches customer funds, your legal and finance teams need visibility into how your BaaS partner and sponsor bank actually monitor transactions — not just a service-level agreement that says they do.
- Ask for evidence of continuous monitoring, not annual attestations. A sponsor bank relationship that hasn’t been reviewed since onboarding is now a regulatory liability, and increasingly, a commercial one — several sponsor banks are re-pricing or exiting weaker partnerships first.
- Build a contingency plan for program continuity. With nearly a third of sponsor banks weighing an exit from embedded finance, any company whose revenue depends on an embedded card, lending, or payments feature should know how quickly it could migrate to a new banking partner if its current one pulls back.
The Bigger Picture: Embedded Finance Is Maturing, Not Dying
None of this signals the end of embedded finance as a business model. Consumer and business demand for financial services delivered inside the software people already use every day isn’t going away — if anything, the current reckoning is a sign the category has grown large enough to warrant the same scrutiny applied to traditional banking. What’s ending is the era in which embedded finance could be treated as a plug-and-play feature bolted onto a product roadmap with minimal legal or compliance investment.
The companies that come out of this period strongest will be the ones that treat regulatory exposure as a design constraint from day one — mapping liability across the full technology stack, documenting oversight rather than assuming it, and choosing banking partners based on the strength of their compliance programs rather than just their API and pricing. For finance and operations leaders evaluating an embedded finance feature, product, or partnership in the second half of 2026, that diligence is no longer optional — it’s the price of staying in the game.
Cross-Border Payments in August 2026: Why Stablecoins Aren’t Beating Correspondent Banking on Cost Yet
The cross-border payments stack is being taken apart, piece by piece
Correspondent banking’s grip on cross-border payments is loosening fast. In August 2026 alone, Visa joined Singapore’s stablecoin-settlement pilot, OpenPayd went live on Circle’s Payments Network, and Fedwire completed its move to ISO 20022 — all pointing the same direction: fiat rails and stablecoin rails are being wired together rather than one replacing the other. But a Banca d’Italia study released the same month found stablecoin remittances cost anywhere from 0.30% to 8.96%, no cheaper on average than legacy providers, once exchange fees and FX spreads are counted. The real story isn’t “stablecoins kill Western Union” — it’s a fragmenting, multi-rail infrastructure where speed is now table stakes and cost advantages are corridor-specific, not universal.
For a decade, the pitch for fixing cross-border payments was simple: rip out correspondent banking, add blockchain, watch fees and settlement times collapse. That pitch is now colliding with evidence. This month brought both the clearest signal yet that stablecoin rails are becoming permanent fixtures of mainstream payments infrastructure, and the clearest data yet that they don’t automatically make transfers cheaper. Understanding why both things are true at once is the actual story finance and treasury teams need heading into the rest of 2026.
What actually happened in August 2026
Three announcements this week illustrate how quickly the plumbing is changing. Visa joined a Monetary Authority of Singapore-led initiative — reported by Finextra as the “BLOOM” project — to pilot stablecoin settlement alongside traditional card rails, an explicit attempt to connect conventional payment systems with tokenized-asset settlement rather than treat them as competitors (Finextra, August 26, 2026). On the same day, PYMNTS reported that banks and fintechs are “unbundling the cross-border stack,” separating what used to be a single correspondent-banking black box into distinct layers — FX, compliance, settlement, liquidity — that specialist providers now compete to own. The article cited Visa’s BLOOM participation, OpenPayd’s integration with Circle Payments Network, and a cluster of wholesale central bank digital currency and tokenization pilots — Project Agorá, Project Pangea, Qivalis, and UniKA — all testing tokenized settlement across different currency corridors (PYMNTS, August 26, 2026).
OpenPayd’s move is worth dwelling on. As of August 25, 2026, the London-based banking-as-a-service provider went live on Circle’s Payments Network (CPN), which functions as a coordination layer connecting regulated financial institutions to route payments through USDC and EURC rather than a chain of correspondent banks. According to OpenPayd and Circle’s joint announcement, corridors such as euro-to-Brazilian-real and British pound-to-Mexican-peso are now settling in seconds. That is a genuinely different experience from a traditional SWIFT payment through two or three intermediary banks, which can still take one to three business days depending on the corridor and cut-off times.
Meanwhile the “boring” rail also moved: Fedwire, the Federal Reserve’s real-time gross settlement system, completed its migration to the ISO 20022 messaging standard on July 14, 2026 — a change reported to cut payment rejections tied to incomplete or malformed data by roughly 35%, largely because the richer message format forces structured, machine-readable beneficiary and purpose-of-payment data instead of free-text fields banks have historically mangled. A related, easy-to-miss deadline: structured or hybrid postal addresses become mandatory in cross-border payment messages in November 2026, with every payment required to carry at minimum a town name and country in machine-readable fields. For any treasury or payments team still passing addresses as unstructured strings, that’s an operational fix that needs to happen well before the deadline, not after a payment gets bounced.
The instant-payments layer: linking domestic rails instead of replacing them
A second, less flashy but arguably more consequential trend is the linking of domestic real-time payment systems across borders. Singapore’s PayNow and Thailand’s PromptPay — both near-universal domestically — are being piloted as a connected corridor, and similar bilateral links are being tested between Canadian and Mexican instant-payment rails. In the U.S., FedNow surpassed 1,500 participating institutions across all 50 states by late 2025, and The Clearing House’s RTP network has signaled plans to extend cross-border reach in the coming months. The Financial Stability Board’s own target — that 75% of cross-border payments should reach the beneficiary within one hour by 2027 — is now less than 18 months away, and instant-rail interlinking, not blockchain, is the primary mechanism regulators are betting on to hit it.
This matters for how you read the “stablecoins vs. banks” narrative that dominates trade press. The two approaches aren’t strictly competing: interlinked instant-payment rails handle bank-to-bank, regulator-supervised flows with settlement finality baked in, while stablecoin rails handle flows where at least one leg lacks reliable instant-payment infrastructure — much of Sub-Saharan Africa, parts of Latin America, and corridors where correspondent banking has thinned out. The World Bank has documented average costs of roughly 6.4% to send $200 across borders globally, with Sub-Saharan African corridors running closer to 9% — precisely the corridors where correspondent relationships have been quietly disappearing for over a decade. Bank for International Settlements data shows active correspondent banking relationships fell by roughly 30% globally between 2011 and 2022, with some regions — the South Pacific among them — losing more than 60% of active correspondents, driven by de-risking as compliance costs outpaced the profitability of maintaining thin-margin relationships in smaller markets.
The under-covered part: stablecoins are not a blanket cost win
Here is where most coverage of “stablecoins fixing remittances” gets ahead of the evidence. In late July 2026, Banca d’Italia (the Bank of Italy) published an empirical study that tracked 200 real USDC transfers across ten remittance corridors, measuring true end-to-end cost — not just the on-chain transaction fee, but the full path including exchange purchase fees, funding costs, and FX conversion spreads on both ends. The results, reported by CoinDesk, Global Finance Magazine, and Crowdfund Insider, found total costs ranging from 0.30% to 8.96% depending on the corridor — with Italy-to-Argentina the cheapest route tested and Argentina-to-Italy, running the same corridor in reverse, the most expensive at nearly 9%. USDC beat traditional remittance providers on only three of the ten corridors tested: Italy-to-Argentina, Italy-to-South-Africa, and Brazil-to-Italy. On the rest, stablecoin costs landed in the same range as incumbent money transfer operators.
The mechanism explains why: blockchain settlement itself is nearly free and fast — the Bank of Italy team recorded on-chain settlement under 15 minutes in most tests. But almost none of the actual cost sits on-chain. It sits in converting local fiat into stablecoins on the sending side, and converting stablecoins back into local fiat (often cash, for remittance recipients) on the receiving side. Those two off-ramp legs are still handled by exchanges, local banks, or cash-payout agents charging conventional FX spreads and service fees — the exact friction stablecoins were supposed to eliminate. This is the study every fintech pitch deck claiming “1-2% all-in stablecoin remittances” needs to be checked against before the number gets repeated as fact.
Where the money transfer operators are actually placing bets
Legacy money transfer operators aren’t sitting this out, and their moves show they’ve read the same cost data everyone else has. Western Union launched USDPT, a dollar-backed stablecoin issued by Anchorage Digital Bank and built on Solana, in May 2026. Rather than pitching USDPT as a cheaper remittance mechanism on its own, Western Union paired it with what it calls the Digital Asset Network (DAN) — infrastructure that lets USDPT and other digital-asset balances be cashed out at any of Western Union’s roughly 360,000 payout locations across more than 200 countries and territories. The bet isn’t that blockchain settlement alone saves money; it’s that owning the last-mile cash-out network — the exact layer the Bank of Italy study identified as the real cost driver — is the actual moat. A “Stable by Western Union” consumer spending product and a USD-denominated card aimed at users in high-inflation economies are both rolling out through the rest of 2026, extending the same logic: hold value in a stable dollar instrument, but rely on Western Union’s physical and card-network reach to move it into something spendable.
MoneyGram has taken a similar dual-rail approach, integrating stablecoin wallet functionality while keeping its cash agent network as the core value proposition in markets where bank access is limited. Neither incumbent is betting the business on stablecoins replacing their networks — both are treating stablecoins as an additional settlement option layered onto physical reach that new entrants would take years to replicate.
Regulation is now the pacing item, not the technology
The technical capability to move money nearly instantly across borders using either interlinked instant-payment rails or regulated stablecoins now clearly exists. What’s constraining rollout is regulatory sequencing, and 2026 has been the year several major regimes actually came into force rather than remaining proposals. In the European Union, MiCA (Markets in Crypto-Assets regulation) enforcement reached a hard deadline on July 1, 2026: stablecoin issuers had to be fully authorized by that date or face delisting from EU markets, with tokens required to be backed 1:1 by liquid reserves and redeemable at par on demand. In the United States, the GENIUS Act — signed into law in July 2025 — created the first federal licensing and reserve framework for payment stablecoins; the OCC published its proposed implementation rule on March 2, 2026, and Treasury’s FinCEN and OFAC issued a joint anti-money-laundering and sanctions proposed rule on April 8, 2026, with the full regime not fully operational until January 2027.
The practical problem for anyone running cross-border payment flows: GENIUS Act reserve requirements and MiCA reserve requirements don’t match, and Asian regulators — Singapore’s MAS among them — are running their own licensing sandboxes with yet another rulebook. A payments or treasury team building on stablecoin rails today isn’t choosing “the” stablecoin infrastructure; it’s choosing a jurisdiction-specific compliance posture that needs active maintenance as these regimes keep diverging through 2027.
What this means for finance and treasury teams right now
A few concrete takeaways follow from where the infrastructure actually stands in August 2026, as opposed to where the marketing says it stands. First, speed is no longer a meaningful differentiator — interlinked instant rails and stablecoin rails have both made near-real-time settlement achievable on a growing list of corridors, so evaluate providers on total landed cost and reliability, not “instant” claims that are now close to baseline. Second, cost advantage is corridor-specific and must be verified per route, not assumed from a vendor’s blended average; the Bank of Italy’s ten-corridor dataset is a useful benchmark methodology to request from any stablecoin provider pitching your business. Third, the ISO 20022 structured-data requirements — the November 2026 structured-address mandate specifically — are operational deadlines: rejections are already down 35% on Fedwire for institutions that adapted their data formatting, and firms that haven’t updated beneficiary and address fields risk failed or delayed payments once the deadline lands. Fourth, regulatory fragmentation between GENIUS Act, MiCA, and Asian licensing regimes means multinational treasury operations should expect to manage multiple compliant stablecoin relationships rather than standardizing on one, at least through the transition into 2027.
The honest framing is neither the triumphant “correspondent banking is dead” narrative nor the skeptical “stablecoins are hype” counter-narrative. It’s a genuinely multi-rail environment: correspondent banking is contracting but not disappearing, interlinked instant-payment systems are absorbing more bank-to-bank flow, and regulated stablecoins are filling gaps in corridors where correspondent relationships have thinned fastest — while still carrying real, corridor-dependent costs the Bank of Italy has now put numbers against. The organizations building durable advantage aren’t picking a single rail and betting on it; they’re the ones — Western Union pairing a stablecoin with its cash network, OpenPayd pairing CPN with its banking-as-a-service platform — treating the new rails as one more tool in a stack that still needs the old ones.
Stablecoins and Business Finance in 2026: Why the Rails Are Ready but Adoption Isn’t
The stablecoin market has grown to roughly $308 billion, Visa and Mastercard are fighting over who owns stablecoin settlement rails, and U.S. regulators finally started writing the detailed rules of the GENIUS Act in August 2026. Yet PYMNTS data shows only 13% of middle-market firms that tested stablecoins have actually gone live — the technology is arriving faster than the treasury back office can absorb it.
For years, “crypto in corporate finance” mostly meant a handful of public companies buying bitcoin for the balance sheet. In 2026, the more consequential story is quieter and more plumbing-focused: stablecoins, tokenized treasuries, and blockchain settlement rails are being built directly into how ordinary businesses move money, and the payment giants that businesses already depend on are scrambling to own the infrastructure before someone else does.
The scale is no longer a rounding error
Total stablecoin market capitalization stood at roughly $308 billion as of mid-August 2026, up about 14% year-over-year, after peaking near $321 billion earlier in the spring. Treasury Secretary Bessent and Citigroup analysts have both floated projections putting the market near $420 billion by year-end. Tether’s USDT and Circle’s USDC together account for roughly 82% of that total — meaning that for all the talk of a crowded stablecoin market, the actual usage is concentrated in two issuers most finance teams have already heard of.
What’s changed is where that supply is going. Stripe reported processing $223 million in stablecoin payments within weeks of launching support, across more than 70 countries — a clear signal that stablecoin acceptance is being built into mainstream payment infrastructure rather than staying confined to crypto-native platforms. Polygon alone processed $9.9 billion in stablecoin payment volume in the first half of 2026, already exceeding its entire 2025 total.
Regulatory clarity actually arrived — on a schedule
The single biggest structural change in 2026 is that U.S. stablecoin regulation stopped being theoretical. The GENIUS Act, signed into law in July 2025, moved into its implementation phase this year: the Treasury issued a Notice of Proposed Rulemaking on August 18, 2026, spelling out the Section 3 licensing regime for stablecoin issuers, with a 60-day public comment window. The Office of the Comptroller of the Currency is targeting final rules by November 2026, with an effective date of January 18, 2027, and a hard deadline of July 18, 2028 for unlicensed foreign stablecoins to exit the U.S. market entirely.
Secretary Bessent’s framing — that the rules give “the regulatory certainty businesses need to innovate and grow” — is the kind of statement that usually reads as boilerplate, but in this case it tracks with what corporate treasurers have been asking for. Separate PYMNTS survey data found 77% of CFOs cite crypto compliance uncertainty as a top barrier to adoption, ahead of technology concerns or cost. A firm licensing timeline, even one that stretches into 2027 and 2028, is itself a form of progress for finance teams that have spent years unable to get a straight answer from counsel about what’s actually permitted.
If your business is evaluating stablecoin payment acceptance, the GENIUS Act’s phased timeline means the compliance ground will keep shifting through 2027. Build any integration around the issuer’s licensing status, not just its market share — USDC and USDT dominate today, but “unlicensed foreign stablecoin” exits are mandated by mid-2028, and you don’t want working capital sitting in a token that has to unwind under deadline pressure.
The payments giants are fighting over the rails, not the coins
The clearest evidence that stablecoins have gone mainstream isn’t crypto-market chatter — it’s the M&A and consortium activity among the companies that already process the world’s card payments. Mastercard agreed in March 2026 to acquire stablecoin infrastructure firm BVNK for up to $1.8 billion; BVNK processes roughly $30 billion a year across more than 130 countries, with stablecoin pay-in volume up 230% in 2025 alone. That deal reportedly pushed Visa to go shopping for its own stablecoin settlement partner, while separately expanding PYUSD settlement support through Paxos.
Perhaps more telling than either acquisition is that Visa, Mastercard, Stripe and Coinbase have all backed a shared stablecoin standard — the “Open USD” (USDG) consortium — rather than each pushing a proprietary token. Visa and Mastercard have also both joined Circle’s “Arc” blockchain initiative, aimed at real-time settlement and what the industry is calling “agentic commerce,” where AI agents transacting on a business’s behalf need instant, low-friction settlement rails. The strategic logic is straightforward: no single payments company wants to bet its network on being locked out of whichever stablecoin standard wins, so the incumbents are hedging by co-owning the standard itself.
Where the adoption story gets honest
Here’s the part of the 2026 fintech narrative that doesn’t make it into most vendor press releases: actual production use inside ordinary businesses is running well behind the infrastructure buildout. PYMNTS Intelligence research found that more than 40% of middle-market firms have discussed or piloted stablecoin use, but only about 13% report having moved it into live production — a real, measurable adoption gap between interest and execution. A Kansas City Fed analysis from April 2026 went further, estimating that payments account for less than 1% of total stablecoin usage today; the overwhelming majority of stablecoin supply still sits idle inside crypto markets rather than circulating through actual commerce.
The bottleneck, per multiple 2026 surveys, isn’t blockchain technology itself — it’s the unglamorous back office. Fitting stablecoin rails into existing ERP and treasury management systems, building reconciliation processes that satisfy an auditor, running sanctions and AML screening on wallet addresses the way a bank would screen a wire transfer, and maintaining segregation-of-duties controls that a blockchain transaction doesn’t enforce by default — these are the actual gating items, and they take longer to solve than any pilot integration with a payment processor’s API.
Don’t mistake payment-processor stablecoin support for organizational readiness. A business can technically accept stablecoin payments through Stripe or a similar processor in an afternoon, but reconciling that revenue against existing accounting systems, and satisfying an auditor that AML controls were applied, is a separate project — often the one that actually determines whether a pilot becomes production.
Corporate treasuries and tokenized assets are moving in parallel
Separately from payment rails, a growing number of public companies are holding crypto directly on the balance sheet. As of the most recent full count, 61 public companies run an explicit bitcoin treasury strategy, with collective holdings around 848,100 BTC — roughly 4% of all bitcoin that will ever exist. Industry commentary has started calling 2026 the “altcoin treasury year,” as firms that added bitcoin now extend the same logic to other tokens, a trend some observers attribute as much to board-level competitive pressure as to any specific financial thesis.
Tokenized real-world assets are the other fast-moving lane. BlackRock’s tokenized Treasury fund, BUIDL, passed $2.5 billion in assets under management by late May 2026, with Franklin Templeton, JPMorgan, Fidelity and Apollo all expanding competing tokenized products. Unlike the speculative tokenization pilots of a few years ago, the 2026 generation of these products is explicitly built for compliance from the ground up — allowlists restricting who can hold the token, transfer restrictions, investor caps, and audit trails embedded directly in the token’s logic rather than bolted on afterward.
The economics that actually move a CFO
Strip away the regulatory and M&A narrative, and the reason this keeps advancing is a fairly blunt cost argument. Traditional cross-border bank rails run 1.5–3% in fees with settlement measured in two to five business days; stablecoin rails typically run under 1% with settlement measured in minutes or, on faster networks, seconds — Solana finality under 400 milliseconds, Ethereum around 15 seconds, Tron in the 1–2 second range. Against a global average remittance fee benchmark of 6.49%, a sub-1% alternative is not a marginal improvement, it’s close to an order-of-magnitude difference. For any business with meaningful cross-border supplier payments or international payroll, that gap is the actual business case — independent of whatever else is happening in the broader crypto market.
The realistic 2026 picture, then, is neither the breathless “stablecoins are eating the payments industry” framing nor the dismissive “it’s all speculation” take. It’s an infrastructure layer being built faster than most finance teams can operationally absorb it, with genuine cost and speed advantages waiting on the other side of a compliance and systems-integration problem that, per the current data, only about one in eight companies has actually solved so far.
A practical starting point for finance teams
For a business finance or treasury team deciding whether to move past the discussion stage in 2026, the sequencing that separates the successful 13% from the stalled 87% is fairly consistent. Start with a single, narrow use case — typically cross-border supplier payments or contractor payroll, where the fee and settlement-speed gap is largest and easiest to quantify — rather than a general “accept stablecoins” mandate. Confirm the reconciliation path into existing accounting software before running a single live transaction, since retrofitting reconciliation after the fact is where most pilots stall. Treat wallet-address screening as a non-negotiable control equivalent to wire-transfer AML checks, not an optional add-on. And track the GENIUS Act’s rulemaking calendar directly — the November 2026 OCC final rules and the January 2027 effective date will likely determine which issuers are viable long-term counterparties, and building around a token that later gets swept into the mandatory 2028 foreign-issuer exit is an avoidable mistake.
None of this requires a business to have a view on bitcoin as an asset. It requires treating stablecoin rails the way any other new payment infrastructure gets evaluated: on cost, settlement time, compliance burden, and counterparty durability — the same criteria that decided the last generation of payment-rail decisions, just with a faster clock this time.