Requirements:
• Your Smartpay Fuse account must be configured for tokenization.
• You must run the authorization and tokenization directly through Smartpay Fuse.
• Alternative payments are supported through the Smartpay Fuse alternative payment method platform. If you are using legacy alternative payment methods such as PayPal or bank transfer, you will need to migrate to newer solutions.
Version 1.0.1
SAP DPA runs in the SAP Cloud Platform using APIs. This means you can connect painlessly to multiple applications, saving you money and hassle from having to maintain multiple point-to-point connections. You can hit the ground running, with integration straight out of the box into various SAP and non-SAP order/sale-to-cash processes (B2B, B2C, online shops, etc.). Smartpay Fuse makes the choice easy, with a ready to go de-coupled integration to the SAP DPA. We designed it this way so you can connect SAP and non-SAP consumer applications alongside the Smartpay Fuse payment management platform and be confident that end-to-end processing of digital payments is secure.
Token Preparation
Token Preparation with Authorization
Payment Authorization
Payment Authorization Cancellation
Payment Reauthorization
Charge
Sale
Payment Credit
Blind Payment Credit
Cards, PayPal, Klarna, Sofort, iDEAL
The SAP digital payments add-on (DPA) enables you to connect SAP and non-SAP consumer applications with non-SAP payment service providers (PSPs). The SAP DPA solution is an alternative to current custom PSP integrations and provides ready-to-use PSP connectivity.
The SAP DPA integration consists of two distinct elements: DPA core and the DPA adapter.
The DPA core is found within SAP architecture and the SAP DPA adapter is held within Smartpay Fuse. The initial authorization and tokenization is required to run directly through Smartpay Fuse. Following authorization and tokenization, all calls coming through DPA go to the SAP DPA core. The SAP DPA core then communicates with the SAP DPA adapter
Description.
Description.