Elavon plans to connect its payment capabilities to two SAP applications. The U.S. Bank subsidiary announced on October 26, 2026 that it plans integrations with SAP Digital Payments Add-On and SAP Commerce Cloud’s Open Payment Framework. Elavon also joined the SAP PartnerEdge program. The company described planned work, not a completed rollout.
Where the payment connection sits
SAP says its Digital Payments Add-On connects consumer applications, including online shops and ERP systems, with non-SAP payment service providers. It supports payment card and online-payment processing. SAP’s documentation says administrators must set up the add-on account and the connection to the payment providers they intend to use.
SAP describes its Open Payment Framework as a SaaS solution for managing payment integrations in SAP Commerce Cloud. The framework has its own integration and administration guidance.
Elavon’s announcement names both products as targets for its planned integration. It says the connection is expected to bring payment capabilities into SAP workflows covering finance, commerce, supply chain and other operations. Those benefits are Elavon’s expectations; the announcement does not establish a measured reduction in cost or implementation time.
What enterprise teams need to check
For an enterprise already using SAP, the practical question is which application, payment method and market the eventual integration will support. SAP’s general documentation points users to an integration overview for supported functions and providers. That documentation should not be treated as proof that Elavon’s announced connection is already available.
Elavon says the companies plan to expand the integration over time to additional SAP solutions, payment methods and markets. The announcement does not give a launch date or a list of supported markets for the planned connection. Teams assessing it will need the eventual product documentation and commercial terms before deciding how it fits an existing payment flow.
The distinction between payment software and the underlying processing relationship still matters. A platform may put a payment step closer to a business workflow, while processing, settlement, reporting and operational responsibilities depend on the actual service agreement. For a wider explanation, see embedded payments and payment gateway vs PSP.
