Transmission Protocols

Computers use transmission protocols to communicate with each other across a network. To transmit data, such as payment files from Oracle Fusion Payments to a payment system, the implementor defines protocols that the payment system can receive.

Payments offers industry-standard transmission protocols, such as FTP, HTTP, and HTTPS, predefined. They are composed 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 called from the Payments engine

While the transmission protocol defines which parameters are expected in the communication, the transmission configuration defines what value is supplied for each parameter. Transmission configurations and payment systems are associated on the funds capture process profile for funds capture or on the payment process profile for disbursements.

Note: This note applies only to on-premises customers, and never to Oracle Cloud customers. The preferred file-based transmission protocol is Secure File Transfer Protocol (SFTP). File Transfer Protocol (FTP) is unsecured and should only be used to meet legacy third-party requirements. FTP must be used over a secure link such as a virtual private network or a leased line with data link level encryption enabled.