Every Fix for Institutional Stablecoins Adds Back a Checkpoint

The case for stablecoins in wholesale finance has always rested on subtraction. Take out the correspondent bank. Take out the settlement window. Take out the reconciliation lag between the cash leg and the asset leg. What you have left is value that moves in seconds, at any hour, without a queue of intermediaries taking a cut on the way through.

So it is worth noticing that almost every control an institution is told to build around a stablecoin puts a checkpoint back in. A custodian API call before the smart contract will mint. A multi-layered protocol check before a token crosses to another chain. A KYC verification on the person receiving the payment, not just the one sending it. A permissioned token standard that restricts who is allowed to hold the asset at all.

That tension runs through a new white paper from A-Team Group, commissioned by Apex Group, on the institutional adoption of stablecoins. The report is organised as a strategy guide, moving from benefits to obstacles to implementation. Read against the grain, it is something more interesting: a fairly precise inventory of which frictions institutional finance is prepared to give up, and which ones it will pay to keep. We focused on the operational and compliance sections rather than the market-sizing material, because that is where the report is most specific.

Why the timing question got harder, not easier

Regulatory clarity was supposed to be the thing standing in the way. It largely arrived. The GENIUS Act was signed in the United States, MiCA came into force in Europe, and frameworks landed across the Middle East, Japan, Hong Kong and Singapore. Yet a Federal Reserve FEDS Note published in April 2026 by Francesca Carapella, Arazi Lubis and Alexandros Vardoulakis put the stablecoin market at roughly $317 billion as of April 6, 2026, up more than 50% since early 2025 but with market capitalisation flattening through the fourth quarter of 2025 and the first quarter of 2026.

The same note records that stablecoin transaction volumes on Ethereum rose about 50% after the GENIUS Act was signed. Volume moved. Supply plateaued. That gap is the shape of a market where the rules are settled and the plumbing is not, which is exactly the picture the A-Team report paints from the institutional side.

The biggest obstacle is a general ledger, not a blockchain

When A-Team Group polled the audience at one of its webinars on the single hardest part of adopting stablecoins, the answer was not custody, or price stability, or smart contract risk. It was integrating with legacy technology stacks.

The report traces this to a habit rather than a technical limit. Banks have spent decades layering systems on top of one another instead of replacing them, leaving accounting, valuation and payment initiation spread across entrenched infrastructure built around SWIFT ISO 20022 messaging. Having sunk that cost, the path of least resistance is to make the existing estate talk to the new asset rather than the reverse.

The problem is that those systems were never designed to carry a stablecoin position. The report frames the real work as getting stablecoin capital to sit properly inside existing accounting systems and satisfying the risk committee that the format does not create an unmanaged route to capital loss. That is a conversation with accountants and cybersecurity teams, and it happens long before anything is minted.

This echoes a pattern we looked at in the first bank to put dollars on a public blockchain publishing a list of everything that still worries it: the residual concerns cluster around operations and controls, not the underlying ledger.

Two ways to create a token that should not exist

The report splits token creation risk cleanly, and the split is useful because the two halves have different fixes.

Primary minting risk sits at initial issuance on the home chain, where the wrong number of coins can be created or destroyed through compromised keys, a broken issuance process, or simple human error. The report cites the PayPal stablecoin incident that briefly minted to $300 trillion as the illustrative case. The remedy is not procedural. It is putting the check inside the contract: a secure mint process that requires both a command from the issuer and a programmatic verification against the custodian's API, ideally supported by proof of reserve running in near real time, checked every minute or so rather than daily. Built properly, overminting becomes impossible rather than merely detectable.

Secondary minting risk appears the moment a token needs to be somewhere else. Moving stablecoins across chains for delivery-versus-payment, yield or cross-border payment usually means a bridge, and in most capital markets designs the bridge holds minting rights on the destination chain. Compromise the bridge and it can issue tokens that are indistinguishable from real ones, no matter how clean the original issuance was. The report points to the Cross-Chain Interoperability Protocol, adopted by SWIFT, as one mitigation, and to reference ledgers acting as a single registry of record as another. Apex Group has adopted the T-REX Ledger as its default multi-chain orchestration layer, part of a stated ambition to reach $100 billion in tokenised assets by June 2027.

Note what both fixes have in common. Each one inserts a verification step into a transfer that was, in principle, already final.

Atomic settlement stops being atomic at the identity check

The compliance section is where the report is at its sharpest, because it names a contradiction most vendor material avoids.

Strict KYC regimes, Switzerland among them, require identification not only of the customer being onboarded but often of the beneficiary of a stablecoin transaction. As the report puts it, re-verifying the beneficiary defeats the purpose of using stablecoins for instant atomic settlement, because it reintroduces precisely the friction the technology was meant to remove.

Sanctions screening compounds it. Whitelisting wallets or adding transaction-monitoring capability may not satisfy an obligation to identify the owner of a wallet, for the straightforward reason that a wallet is not an identity. Control of a private key is not verified ownership, and a compromised wallet can mean assets are gone for good.

The proposed answer is to move the identity into the token. Permissioned standards such as ERC-3643 let issuers define who may hold the asset, enforce transfer restrictions, recover tokens from lost or compromised wallets, and keep visibility of the holder base through on-chain identity. Whitelisting then attaches to a KYC credential issued by an approved entity rather than to a wallet address. The report notes a permissioned USD1 pilot announced by World Liberty Financial with Apex Group as an example of the model in practice.

The scaling question is whether those credentials travel. A few jurisdictions, the United Arab Emirates among them, already allow one bank to rely on another bank's KYC. If a credential issued by a trusted institution can be accepted across a market, the check happens once instead of at every hop, and the report treats that reusability as a precondition for genuinely atomic transactions. If credentials stay trapped inside single institutions, permissioned tokens simply relocate the friction rather than reducing it.

The obstacle with no technical fix

Regulatory fragmentation ranks second on the institutional obstacle list, and unlike the others it does not yield to better engineering.

The specific concern the report attributes to global commercial banks is legal finality. A redemption treated as final under the law of one jurisdiction may not carry the same finality where it is received. That is not a settlement speed problem. It is a question of which court decides that the money has actually moved, and it creates risk, treasury and operational exposure for any firm running a cross-border model. Until regulators converge, particularly on core AML requirements, every jurisdiction has to be handled on its own terms with its own tailored standards. Anyone mapping that divergence across markets can use our Stablecoin Regulation Tracker to see how the frameworks currently differ.

Issue or use, and why the answer sets everything else

Underneath all of it, the report identifies one decision that determines an institution's exposure to every problem above: whether to issue a stablecoin or build on an existing one.

Issuing means owning the technology, running 24/7 infrastructure support, and managing reserve liquidity and integration. It also means owning reserve income, which in most structures accrues to the issuing entity and is the clearest revenue case in the whole report. Using an established token such as USDT or USDC, or a stablecoin-as-a-service arrangement, gives access to cross-border payment efficiency and on-chain liquidity without the full operational and regulatory weight of issuance.

Read alongside the obstacle list, the choice looks less like a product decision than a decision about how much compliance machinery a firm wants to build and supervise. The report's organisational advice points the same way: rather than routing stablecoin questions through large committees, name a single product manager, a single engineering lead and a single go-to-market lead, and point them at one or two specific use cases.

On yield, the report is careful. Some regimes, Bermuda among them, permit yield-bearing structures that pass part of the reserve return to holders, while many others restrict direct yield distribution to keep stablecoins distinct from deposits and investment products. Institutions looking for return are therefore pushed toward tokenised money market funds, DeFi deployment or tokenised deposits instead. That coexistence of instruments is a theme we explored in stablecoins versus tokenised deposits.

What this means for each side of the table

For banks, the binding constraint is internal. Alignment across treasury, risk, compliance and IT determines whether a stablecoin project gets past pilot stage, and the integration work with existing accounting and payment systems is the largest line item. The report also names competitive pressure from neobanks, what it calls the Revolut moment, as a driver pushing incumbents to act sooner than their own risk appetite might suggest.

For issuers, controls are becoming the product. Proof of reserve verifiable in near real time, secure mint processes checked against custodian APIs, and auditable decisions when the system rejects a mint or blocks a transfer are described as the difference between institutional-grade implementations and less mature offerings.

For regulators, the report describes embedded supervision, where compliance conditions are defined and verified inside the smart contract itself and checked against identity and sanctions data sources, with the Bermuda Monetary Authority named as an example. It also stresses explainability: any automated rejection needs to be reconstructable after the fact.

For corporate treasurers, the operational case is the one that matters, since direct yield is restricted in most regimes. Instant liquidity movement between entities, delivery-versus-payment settlement for tokenised assets, and reduced pre-funding are the concrete gains.

For service providers and custodians, demand is shifting toward reserve management, proof-of-reserve reporting, licensing advisory and secure minting, the operational layer around the token rather than the token itself.

The real question is which frictions earn their keep

The strongest reading of this report is not that stablecoins are ready or unready for institutional use. It is that the honest version of an institutional stablecoin is a stablecoin with selected frictions deliberately restored, and the design work is choosing which ones.

A custodian API check before minting costs milliseconds and removes a class of catastrophic issuance error. That trade is easy. Beneficiary re-verification at every hop can cost hours or days and reintroduces the exact delay that justified the project. That trade is not easy at all, and it does not become easy through better software. It becomes easy only if KYC credentials can be issued once and recognised across institutions, which is a governance question rather than an engineering one.

Which suggests the sequence most adoption forecasts have backwards. The gating factor for institutional stablecoins is not regulatory clarity, which has largely arrived, and not settlement technology, which mostly works. It is whether the identity layer becomes portable, and whether legal finality means the same thing on both ends of a transaction. Everything in the report that has a clean technical answer is already close to solved. Everything that requires institutions to accept each other's work is not.

Source: The institutional adoption of stablecoins: Strategic value, challenges, and implementation frameworks, A-Team Group (Trading Tech Insight and Digital Assets & Tokenisation Insight), commissioned by Apex Group, August 2026.

Additional data: Stablecoin market size, growth and post-GENIUS transaction volume figures are from "Stablecoins in 2025: Developments and Financial Stability Implications," FEDS Notes, Board of Governors of the Federal Reserve System, April 8, 2026, by Francesca Carapella, Arazi Lubis and Alexandros Vardoulakis.

Methodology: We focused on the sections of the white paper covering operational obstacles, minting risk and compliance implementation, and set aside the market-sizing and vendor-profile material.

This article is for informational purposes only and does not constitute financial, investment, or legal advice.