To transmit data to or from a payment system, you need a transmission protocol and a transmission configuration. First, you must have a transmission protocol, which defines the method of transmission. Transmission configurations, which specify concrete transmission details, must be associated with one transmission protocol.
To illustrate, Oracle Payments supports a generic transmission protocol for flat files called File Transfer Protocol for Static File Names. This protocol is a generic method to electronically transmit data, whereas FTP to Paymentech is a specific transmission configuration that specifies how to transmit data to a specific location using FTP as the method.
On the funds capture side, the transmission protocol and configuration are associated with the funds capture process profile, whereas on the funds disbursement side, the transmission configuration is associated with the payment process profile.
Oracle Payments seeds transmission protocols, which are used by all funds capture process profiles and may be used by payment process profiles. These common seeded protocols, such as FTP, are comprised of the following:
a code entry point, which the payment system servlet uses to accomplish transmission
a list of parameters, such as network address and port, for which the transmission configuration must supply values
transmission protocol entry points, which are independent of payment servlets and may be invoked from the Oracle Payments engine
You can view the seeded transmission protocols in Oracle Payments setup pages.
Each transmission protocol has parameters that require values. The values defined for the parameters comprise the transmission configuration for the transmission protocol. For example, the payment system, Paymentech, may require a Socket IP Address of X and a Socket Port number of Y, among other values. Together XY, and the other values, represent Transmission Configuration A for a given transmission protocol.