Circle and Tereina bring stablecoin payments into enterprise software

Circle and Tereina announced on 7 October 2026 that USDC and EURC would be integrated into Tereina’s payment infrastructure, initially focused on SAP Cloud ERP. Circle’s release describes access through SAP Pay for eligible businesses, with customer proof-of-value programmes planned over the following months. This is an enterprise integration announcement, not evidence that every SAP customer has adopted stablecoins.

The integration problem moves inside the business

The useful change is where a finance team encounters the payment option. A separate wallet application can create another approval process and another record to reconcile. Bringing an option into an existing business application may reduce that separation, but the implementation still needs to connect an invoice, an authorized instruction and a final accounting entry.

Consider an illustrative importer paying a supplier. The commercial question is not simply whether a token transfer settles quickly. It is whether the supplier receives the agreed currency, whether an exchange conversion is necessary, who pays network and service fees, and which evidence closes the invoice. Those questions should be written into the acceptance test before anyone compares processing times.

Treasury controls remain the main design work

A sensible evaluation would map permissions from the enterprise application to the payment provider. Who may add a beneficiary? Can one employee both change the destination and release funds? What happens when an invoice is disputed after the transfer? A payment rail does not remove these decisions; it makes their quality more visible.

Currency selection also deserves attention. A dollar invoice and a euro invoice are different liabilities even when both use stablecoins. Choosing the token should follow the obligation and the recipient’s redemption options. A familiar currency label is not enough to establish that a particular business has a usable off-ramp or the right contractual relationship.

What the announced programmes need to show

The companies describe planned implementation work, rather than publishing independently verified savings for a representative customer population. Useful evidence would include exception rates, elapsed time from instruction to usable supplier funds, reconciliation effort and the cost of failed or returned payments. Reporting only the blockchain leg would leave out much of the business process.

For readers evaluating the announcement, the milestone is distribution through software already used for financial operations. The unresolved question is whether that distribution becomes repeatable, controlled execution across real counterparties and jurisdictions. Product availability, legal eligibility and commercial terms should be checked directly for each business rather than inferred from the scale of the surrounding software ecosystem.