Circle and SAP-backed Tereina add USDC and EURC send/receive inside SAP payments
The companies said customer testing will begin over the coming months for global payments and treasury operations.
Circle is integrating USDC and EURC into SAP customers’ payment workflows through a partnership with SAP-backed Tereina, aiming to let enterprises send and receive stablecoins from inside SAP financial software. The companies said they will test the integration with customers over the coming months, but did not provide a production go-live date or name pilot users.
Circle said it is bringing its stablecoins into SAP enterprise payment workflows via a partnership with Tereina, a financial services company described as backed by SAP. The stated goal is straightforward: let businesses send and receive USDC and EURC from within the SAP financial software applications they already use to manage payments, rather than pushing them into a separate crypto-native stack.
Mechanically, the integration is framed as embedded stablecoin rails inside existing enterprise payment operations. Tereina is described as providing payment infrastructure that companies can embed into business software so they can make payments without switching to a separate financial platform, and Circle is plugging USDC and EURC into that embedded flow.
Circle and Tereina also attached a scale claim to the distribution channel. The announcement said SAP’s ecosystem generates 84% of global commerce, a figure presented as context for potential reach if the integration is rolled out broadly across SAP’s customer base.
Enterprise Stablecoin Rails: Dual-Currency Positioning and Distribution Implications
Circle is not pitching this as a generic “stablecoin payments” add-on. The product language splits the use case by currency: “USDC will be the preferred stablecoin for dollar-denominated transactions, while EURC will be available for euro-denominated payments.” For traders tracking stablecoin adoption, that dual-currency framing matters because it positions Circle’s rails as a treasury and settlement tool across two major invoicing currencies, not just a USD-only corridor.
The distribution angle is the bigger tell than the feature list. SAP finance software sits in the middle of how large companies run accounts payable, receivable, and treasury workflows. If stablecoin send/receive is available inside those workflows, Circle is effectively trying to win at the point where payment decisions are executed, which is a different adoption path than asking enterprises to onboard to new wallets, new dashboards, and new operational playbooks.
That said, the announcement is still an integration headline, not a volume print. There were no disclosed transaction metrics, no named enterprise pilots, and no detail on how quickly SAP customers could move from testing to production use.
Customer Testing Window, Missing Implementation Details, and the Arc Strategy Link
Circle and Tereina said they plan to “test the stablecoin integration with customers over the coming months, including for global payments and treasury operations.” That timeline is directionally useful, but it leaves the market without the usual operational details that determine whether an enterprise payments integration becomes sticky or stalls in compliance and procurement.
Key unknowns remain unresolved in the packet: which SAP financial software products or modules will support USDC/EURC send/receive, whether the integration will become generally available after testing, and what geographies are in scope. The announcement also did not specify the settlement rails, including whether flows route through Circle’s Arc chain, other blockchains, or multiple networks, and it did not provide information on fees, spreads, or who carries compliance and KYC responsibility in the workflow.
The timing also links this move to Circle’s broader payments push. Circle launched the mainnet of Arc less than a month before the SAP/Tereina announcement, describing Arc as a layer-1 blockchain focused on stablecoin payments and financial markets. Arc uses USDC for transaction fees and supports more than 20 fiat-backed stablecoins, including USDC and EURC, which makes the SAP distribution play look directionally consistent even though the integration’s underlying rails were not disclosed.
My Take: This Is a Distribution Bet, Not a Volume Print—Yet
The filing-level detail traders should anchor on is the testing language, not the SAP scale claim. “Over the coming months” is a real commitment to customer work, but without named pilots, a production date, or even a disclosed rail, the near-term impact is more likely to trade as narrative than as something that immediately changes on-chain or settlement volume.
The threshold that matters is whether this moves from an embedded capability to a production rollout with identifiable customers, clear compliance ownership, and disclosed settlement routes. If those pieces land and the integration becomes a default option inside SAP payment workflows, the setup starts to look structural rather than announcement-driven.
