For most of their history, stablecoins have been discussed as something you hold. A balance, an asset, a position on a chain. The most recent signals from the market point in a different direction. Stablecoins are entering mainstream payments not as something businesses hold, but as a settlement leg hidden inside an ordinary transaction.

On September 28, 2026, Coinbase and Citi expanded their payments collaboration so that institutional clients using Spring by Citi can accept stablecoin payments without holding or managing stablecoins directly. Coinbase converts the digital currency into fiat, and Citi settles the merchant in traditional currency. The customer pays, the merchant is paid, and neither necessarily touches a token.

The significance is not only that another large bank is supporting stablecoin payments. It is that the stablecoin can disappear from the user experience entirely.

That abstraction is genuinely useful. Removing the need to hold, convert, or manage a digital asset lowers one of the largest practical barriers to adoption, and it lets institutions offer stablecoin acceptance without asking customers to understand anything new. But abstraction changes where complexity sits. It does not remove it.

Behind a single checkout, a multi-step flow is taking place. A stablecoin is accepted, converted into fiat, and settled through the bank, and more than one institutional system records a different stage of the same transaction. The simplicity is real on the surface. Underneath, the payment has more moving parts than a conventional one, not fewer.

This is the tension institutions have to manage. For the merchant, that should remain one payment. For the institution, it still has to be governed as one payment.

That means the pieces cannot be allowed to drift apart. The authorization, the applicable compliance decisions, the transaction limits, the conversion events, the settlement state, and the resulting records all need to stay connected across the lifecycle — even when different providers execute different parts of the flow. When those elements live in separate systems with no common thread, the institution is left reconstructing what happened after the fact, which is precisely the problem abstraction was supposed to spare everyone.

This is the role orchestration plays.

ModernRails provides that layer. It maintains a consistent payment instruction and lifecycle across settlement methods, routing the transaction through institution-defined controls and external services as required, so the separate stages resolve into one coherent record rather than a set of disconnected events. Whether a payment settles through a conventional rail or a stablecoin leg the customer never sees, it is governed and recorded as a single payment.

For institutions building toward abstracted settlement, that has practical consequences:

• Controls and compliance decisions apply consistently, even when parts of the flow are executed by outside providers
• Conversion, settlement, and recording stages stay linked to one payment instruction
• A complete, reviewable record is preserved end to end, not assembled afterward
• New settlement methods are absorbed into the same lifecycle rather than governed as separate systems

The direction of travel is clear. As stablecoins move into mainstream payments, they will increasingly do so invisibly, tucked beneath interfaces that look no different from the ones customers already use. That is a good thing for adoption. It raises the bar for infrastructure. The more invisible the payment rail becomes to the user, the more important it is that the institution maintains one coherent record of what happened underneath it.