Connection of External Systems

Payment Engine provides connections to the feeder and forwarding systems for input and output of payment transaction data as part of its core functionality. Using the SAP NetWeaver platform, you can connect other systems to Payment Engine through Business Application Programming Interfaces (BAPIs) and remote function calls (RFCs). Thus, you can make use of account-management (AM), embargo, and money-laundering systems as well as middleware or front-end applications.

Moreover, you can use enterprise services for payment transactions. For more information, see Enterprise Services for Payment Engine.

The following figure shows an example of a system landscape for Payment Engine including an account-management system (AMS).

This graphic is explained in the accompanying text.

Payment Engine Overview

For more information about the communication between Payment Engine and external feeder systems and forwarding systems, see File Handler (FS-PE-FH).

You can also submit payment transaction data from external systems in online mode over the payment order interface.

The following figure shows the potential integration of Payment Engine in the front end and middleware as well as possible real-time or other interfaces across the SAP NetWeaver integration and application platform.

This graphic is explained in the accompanying text.

Payment Engine Integration

Prerequisites

You connect external systems through proxy or application programming interfaces (APIs) that require implementation of Business Add-Ins (BAdIs).

Note Note

Payment Engine provides a proxy interface infrastructure and a number of BAdIs for external connection implementations.

End of the note.

Process

You implement the following connection options through interfaces using BAdIs for your specific applications:
- Connection to account-management systems through a proxy interface
  For more information, see Connection to an Account Management System.
- Connection to an embargo or other system through an API
  For more information, see Connection to an Embargo System.
- Connections to other systems and customer-specific or country-specific extensions by using these BAdIs as models
You implement your specific methods using the BAdI models.
You carry out applicable activities in Customizing for Payment Engine.
You use BAPIs and RFCs to communicate with the connected system.

The figure below illustrates the implementation of extensions and interfaces using BAPIs and RFCs over the NetWeaver platform.

This graphic is explained in the accompanying text.

Payment Engine Extensions and Interfaces