How You Configure a Communication Channel to a Payment System

To transmit payment information to or receive payment information from a payment system, you must configure the channel used to communicate with the payment system. This topic discusses the following concepts:

  • Proxy server

  • Secure sockets layer (SSL) protocol

  • Unsecured protocols

Proxy Server

Payments must communicate through a proxy server to its payment system. You can use the standard Java networking proxy system properties that are in the configuration files when Oracle Fusion Applications were initially set up. Alternatively, you can specify proxy settings for a transmission protocol on the Create Transmission Configuration page by entering a value for the Proxy Host parameter.

Secure Sockets Layer Protocol

When Payments communicates with a payment system, the information exchanged may be sensitive information, such as credit card numbers. If the communication isn't secure, it poses a security risk. The security risk increases when communication to the payment system is across a public network, such as the Internet.

To set up a payment system servlet with a secure sockets layer, enable HTTPS on the application server where the servlet resides. If funds capture process profiles aren't defined for the payment system, change the Transmission Servlet Base URL on the Edit Payment System page to start with HTTPS. If funds capture process profiles are defined, change the value for the Destination URL parameter on the Edit Transmission Configuration page to start with HTTPS.

For secure communication with the payment system, ensure that the most current certification authority (CA) certificates are in the Oracle Fusion secure sockets trust store file. If Payments rejects the payment system's secure sockets certificate, you may have to insert the certificates manually.

The following table lists security actions that are applicable to Cloud and on-premise.

Action

Cloud

On-premise

Set up a payment system servlet with a secure sockets layer.

Not applicable.

Enable SSL on the servlet's application server.

Insert certification authority certificates.

File a service request with the help desk.

Enter a value in the Value field for the Wallet Location parameter on the Create or Edit Transmission Configuration page.

Unsecured Protocols

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.