1. Implementing Payables Invoice to Pay
  2. How You Set Up Transmission Configurations

How You Set Up Transmission Configurations

In Oracle Fusion Payments, setting up transmission configurations is mandatory if your company wants to transmit payments to a payment system or a bank.

To enable your company to exchange information with your payment system or bank, a preexisting agreement must exist as to how information is structured and how each side sends and receives it.

Setting up transmission configurations involves the following actions:

  • Understanding protocols

  • Understanding transmission configurations

  • Understanding tunneling configurations

  • Considering best practices

  • Setting up transmission configurations

Understanding Protocols

A transmission protocol is a set of rules or procedures for transmitting data between electronic devices, such as computers. To transmit data, such as a payment file or a settlement batch from Payments to an external payment system, you must define the transmission protocols that the payment system can receive.

Payments offers industry-standard predefined transmission protocols, such as SFTP, HTTP, HTTPS, and AS2. These protocols include the following:

  • A protocol implementation class, which implements the technical details of communication in a generic manner

  • A list of parameters, such as network address and port, for which the transmission configuration must supply values

The transmission protocol defines which parameters are expected in the communication between your company and its payment system or bank.

Understanding Transmission Configurations

A transmission configuration is a group of specific transmission details, which is associated with a specific transmission protocol. A transmission configuration defines a value for each parameter in a transmission protocol. The values in a transmission configuration are specific to one payment system or financial institution. For example, a transmission protocol may require parameters, as well as a Socket IP Address, and a Socket Port Number. Your payment system, which accepts that protocol, gives you the values that it expects to receive for those parameters. You enter those values in the Socket IP Address and Socket Port Number fields.

Understanding Tunneling Configurations

A tunneling configuration is a type of transmission configuration that helps transmit data through a transmission servlet that can securely connect to your payment system or bank without exposing internal data. The transmit servlet acts as a relay or bridge between the different segments of your network infrastructure, some of which are more suitable, such as a DMZ zone, from which to open connections to external systems.

Considering Best Practices

Before selecting a protocol for payment processing, do the following:

  • Find out what your processing bank supports.

  • Favor transmission protocols predefined in Payments.

  • Use funds capture process profiles or payment process profiles for greater ease in configuring transmission and formatting.

Before selecting a transmission configuration for payment processing, note the following:

You may need two transmission configurations as follows if you use a protocol normally blocked by your network security rules:

  • A tunneling configuration to exit the fire wall

  • A transmission configuration for the payment system server

Your transmission configuration must point to the tunneling configuration.

Caution: It is always a configuration error for the tunneling configuration to point to any other tunneling configuration, including itself.

Setting Up Transmission Configurations

In the Setup and Maintenance work area, use the following to select a protocol, which is the method of transmission, and click Create on the Manage Transmission Configurations page.

  • Offering: Financials

  • Functional Area: Payments

  • Task: Manage Transmission Configurations

On the Create Transmission Configuration page, enable electronic connectivity with your payment system or bank by specifying values for each parameter for the protocol you selected.

The transmission configuration is subsequently assigned to a payment system or bank in the funds capture process profile for funds capture transactions or in the payment process profile for disbursements.

Note: When an environment is refreshed (Production-to-Test or Test-to-Test), you must perform these payments transmission-related updates in the target environment before running any payment batches:
  • Migrate Payment Wallet - During Production-to-Test (P2T) process, payments wallet stored in OPSS isn't migrated from source to target environment. As part of post P2T tasks, user must perform the wallet migration using the steps provided in Payments Wallet Migration Post P2T / T2T Refresh (Doc ID 2407678.1)
  • Update Transmission Configuration - As part of post P2T tasks, user must update payments transmission configuration to point to the bank's nonproduction server. Running a payment batch without making these changes will accidentally transmit the payment file from target environment to the bank's production server.

Related Topics