In October 2025, a technical error at Paxos, the issuer of PayPal's PYUSD stablecoin, created 300 trillion tokens, equivalent to $300 trillion at the dollar peg, before they were burned within 30 minutes.
Although the error was corrected, it shows how quickly an incorrect minting instruction can produce a position of extraordinary scale, and why institutional adoption depends on controls that operate as part of the transaction itself.
Stablecoins can move value across borders within seconds and operate around the clock. The systems governing their issuance and transfer must apply the same standard of control expected throughout regulated financial markets.
The biggest obstacle is already inside the institution
In an A-Team Group audience poll, financial institutions identified integration with legacy technology stacks as the biggest obstacle to stablecoin adoption. Banks have spent decades adding systems rather than replacing them, creating layers of infrastructure that cannot readily process on-chain assets.
Existing accounting and payment systems may depend on SWIFT ISO 20022 messages, while stablecoins operate on blockchain networks. The challenge goes beyond connecting them: banks must reconcile account-based records and payment messages with on-chain records of ownership and transfers. Institutions must preserve accounting accuracy and maintain control over capital movements. Their risk and cybersecurity teams also need sufficient evidence that stablecoin activity does not expose the firm to new sources of loss.
Institutions cite regulatory fragmentation as the second biggest challenge. Differences in anti-money laundering requirements mean that a cross-border stablecoin model may need to operate differently in each jurisdiction. Legal finality creates further uncertainty because a redemption considered final in one market may not receive the same treatment elsewhere.
Minting controls must be built into the transaction
Primary minting risk arises when a stablecoin is created or destroyed on its home blockchain. A compromised key, human error, or a faulty instruction can result in the wrong number of coins entering circulation.
Reserve assets should be verified daily and, ideally, in near real time through custodian systems. This allows the minting contract to confirm that the collateral is physically present when coins are created or destroyed, rather than relying only on periodic reporting.
Secure minting connects each mint or burn instruction to that reserve data. If the required assets are not present, the smart contract rejects the instruction.
Cross-chain transfers create a different form of minting risk. When a stablecoin moves through a bridge, that bridge may receive minting rights on the target blockchain. If the bridge is compromised or manipulated, it may mint invalid coins on the target blockchain even when the primary issuance remains secure. Established, multi-layered protocols can mitigate this risk. One example is the Cross-Chain Interoperability Protocol, which has been adopted by SWIFT and conducts extensive checks during transfers.
A reference blockchain such as the T-REX Ledger provides another approach. It can act as a stablecoin registry and single source of truth, with the ability to track stablecoin identities on-chain and apply the compliance rules required in each market.
Compliance can remove the speed it is meant to protect
Know Your Customer ("KYC") requirements can reintroduce friction into a transaction intended to settle atomically. In Switzerland, KYC may be required for the beneficiary of a stablecoin payment in addition to the person being onboarded. Repeating these checks delays a transaction intended to take place almost immediately and reduces one of the central benefits of digital cash.
The United Arab Emirates provides a different model by permitting one bank, in certain circumstances, to rely on KYC completed by another. Wider acceptance of reusable verification could reduce repeated checks without weakening regulatory oversight.
ERC-3643 links the right to hold or transfer a token to a verified on-chain identity. It can apply transfer restrictions and maintain visibility over ownership, while supporting token recovery when a wallet is compromised. Wallet whitelisting alone cannot provide the same degree of certainty because control of a private key is not the same as verified ownership.
Embedded supervision develops this model through direct work with regulators. Institutions can work with authorities such as the Bermuda Monetary Authority to agree compliance conditions that are then applied through smart contracts. Identity and sanctions checks can be performed against the relevant data sources, with each decision made by the system remaining explainable and auditable. The institution does not set its own regulatory threshold.
A focused route to delivery
Implementation should be assigned to one product manager, one engineering lead, and one go-to-market lead working against one or two defined use cases. This structure creates clear ownership and prevents a large committee from delaying delivery before the commercial case has been tested.
Institutions issuing stablecoins also need partners capable of supporting reserve management and secure minting, alongside custody and continuous operations. Through Apex Digital 3.0, we support the digital asset lifecycle from fund tokenisation and digital treasury through to stablecoin infrastructure.
We have adopted the T-REX Ledger as our default multi-chain orchestration infrastructure. This commitment supports our initial target of $100 billion in tokenised assets by June 2027.
Institutional adoption will not be judged by transaction speed alone. It will depend on whether each transaction remains fully backed and compliant, with a clear audit trail when markets operate around the clock.