October 2026 Payment Infrastructure Updates for Treasury

Quick Answer: Circle and Tereina announced plans to bring USDC and EURC into SAP payment workflows. Modern Treasury applied for a US national trust bank charter, while the ECB described its proposed digital euro acceptance model. Treasury teams should assess each development by its current status, legal entity roles, total cost, and time to usable funds.

Three October announcements put payment design back inside the systems and contracts that finance teams already manage. Circle and Tereina are working on stablecoin payments in SAP. Modern Treasury has asked the US regulator for permission to establish a trust bank. The European Central Bank has explained how private payment providers could distribute a digital euro. Each announcement points to a different operational question, and each is at a different stage.

A provider review should start with the payment obligation. When does the beneficiary receive usable funds? Who holds the asset while it moves? What will the controller see in the ledger? A transfer can settle on one rail while conversion, payout, and reconciliation remain unfinished. The answers determine whether a new method improves the full workflow.

1. Circle and Tereina bring stablecoins toward SAP payment workflows

On October 7, Circle and SAP-backed Tereina announced a partnership to integrate USDC and EURC into Tereina's payment infrastructure, starting with SAP Cloud ERP. Circle says eligible businesses will access the integration through SAP Pay. USDC is intended for eligible dollar workflows, with EURC available for euro activity. The companies plan customer proof-of-value programs over the coming months.

That timing matters. The announcement describes a route into existing enterprise software, but it does not name production customers or provide transaction volumes and end-to-end settlement results. A treasury team cannot yet use the release to estimate its own payment speed or savings. It can, however, define what a useful pilot would measure.

For a supplier payment, the test should begin when an approved invoice becomes a payment instruction and end when the supplier can use the proceeds. Record conversion costs, rejected or returned payments, and the time needed to match the transfer to the payable. The ERP connection earns its place if it preserves approval and audit evidence while reducing manual reconciliation. Faster token movement alone would leave much of the finance team's work intact.

There is a fair reason to test this path early: finance staff already rely on their ERP for payment approval and accounting. Keeping the new rail inside that environment could reduce handoffs. The pilot still needs to show that those handoffs actually disappear and that the beneficiary outcome improves.

2. Modern Treasury applies for a national trust bank charter

On October 5, Modern Treasury said it had applied to the US Office of the Comptroller of the Currency to establish a limited-purpose national trust bank. If the regulator approves the application and grants final authorization, the separate entity would provide federally supervised digital asset custody and related fiat services alongside Modern Treasury's existing payment platform. The company says the proposed bank would make no loans and issue no stablecoins.

The application is a plan for a new entity, not permission to operate it. Modern Treasury says its current software and payment services continue separately while the application is reviewed. A buyer evaluating the platform today should therefore map the entities under its current contracts. If the bank later opens, the buyer can review which activities move to the new entity and which stay with the existing provider.

For corporate treasury, the custody boundary is practical. The team needs to know who holds the digital asset, who executes the fiat leg, whose records establish ownership, and who handles a failed or disputed transfer. A single interface may present these steps together. The contracts and account statements must still identify the responsible entity at each step. This is especially relevant when a payment provider combines software, custody, conversion, and settlement services.

3. The ECB sets out a digital euro acceptance model

In an October 6 speech, ECB Executive Board member Piero Cipollone described the digital euro as a proposed form of central bank money for everyday retail payments. The ECB envisages use online and offline. Banks and other regulated payment service providers would distribute it, manage customer relationships, and build related services. The ECB would supply the core infrastructure.

The speech focused on a common acceptance layer across the euro area. The ECB has signed agreements with the European Card Payment Cooperation, nexo standards, and the Berlin Group to reuse existing technical standards. For merchants and payment providers, this points to questions about checkout integration, acceptance at physical locations, and reconciliation across channels. The final legal framework and commercial arrangements are still being discussed, so implementation plans need to remain conditional.

The ECB also described proposed holding limits and links to bank accounts. Those design choices would affect how a payment is funded and how excess funds return to an account. They warrant attention from product and finance teams that manage retail acceptance. The speech does not announce a live digital euro or establish a corporate treasury payment rail.

4. What finance teams should take into a provider review

These updates call for different decisions. Circle and Tereina offer a future pilot to evaluate in the ERP. Modern Treasury's proposed custody entity depends on regulatory approval. The ECB's model gives payment providers and merchants design details to monitor while legislation and operating terms take shape. Treating all three as available products would distort a comparison.

Ask each provider to trace one representative transaction from approval through beneficiary receipt and reconciliation. Request the legal entity map for custody, conversion, execution, and support. Compare total cost using the amount the beneficiary can actually spend, including FX and payout charges. Finally, separate capabilities available under a current contract from pilots, applications, and proposed designs.

The strongest argument for moving early is the chance to shape an integration before it becomes a standard option. That can justify a bounded pilot. It cannot replace evidence on payment completion, controls, and accounting. Finance teams close obligations against the full record, and that record is the right measure of payment infrastructure.

Disclaimer: This article is for information only and is not legal advice.

Sources

• https://www.circle.com/pressroom/tereina-an-sap-backed-company-and-circle-bring-usdc-and-eurc-into-enterprise-workflows-starting-with-the-sap-ecosystem-behind-84-of-global-commerce
• https://www.moderntreasury.com/newsroom/press-releases/modern-treasury-applies-to-establish-national-trust-bank
• https://www.ecb.europa.eu/press/key/date/2026/html/ecb.sp261006~0da978f159.pl.html