Fields at the first Create/Change/Display Authorization Services screen:

Code

Typically set to EXT or EXC, but can be set to anything.

Application

Select Auth/Deposit.

Request token

Select this field to perform credit card tokenization; otherwise, leave unselected. You can select this field only if the Use Credit Card Tokenization (L18) system control value is selected.

Void auth at deposit

Select this field to void any unused portion of a credit card authorization at deposit time. For stored value card authorizations, the setting of Retain Unused Stored Value Card Authorization After Deposit (J21) applies.

Send reversal

Select this field to perform a credit card authorization reversal when you process a cancellation associated with a credit card payment or deactivate a credit card payment.

Fields at the second Create/Change/Display Authorization Services screen:

Media type

Select Communication.

Batch/Online

Select Online or Batch.

Immediate response

Must be selected.

Primary authorization service

Must be set to .IL. See .IL Service Bureau Setup for required settings.

Communication type

Payment Link must be selected, to indicate messages sent the external payment layer are processed directly.

Response check frequency

Indicates the number of times to wait for the Response time for a response. For example, if the Response check frequency is 5 and the Response time is 1000, the system checks every second (1000 milliseconds) a total of 5 times, unless it receives a response before this interval ends. The recommended setting is 5.

Response time

Defines the number of milliseconds Order Management System waits for a response from the service bureau. The recommended setting is 1000 milliseconds. Note: Order Management System does not wait the entire response time if it is not necessary.

Country codes

If needed, define a cross reference between your country code and the country code used by the service bureau.

Note: This option also indicates whether a service bureau performs address verification processing for the country.

See Defining Authorization Service Countries.

Currency codes

If needed, define a cross reference between your currency code and the currency code used by the service bureau; see Defining Authorization Service Currencies.

Merchant ID Override

If needed, define a merchant ID override for the different entities in your company; see Defining Merchant ID Overrides.

Paytype codes

If needed, define a cross reference between your pay type code and the pay type code used by the service bureau; see Defining Vendor Paytype Codes.

Response codes

Define the reasons that the service bureau approves (authorizes) or declines a transaction. The codes are assigned to each transaction by the service bureau when approving or declining the request; see Defining Vendor Response Codes.

A response code of SU, indicating service unavailable, must be created.

The additional External Service Settings at the Work with External Authorization Service Screen are accessible only to users with External Authorization Service Access (B25) authority.

All fields on the screen are required, with the exception of the External Service flag.

Tracking changes to external service settings: Changes that users make to external service settings are tracked in the User Audit table, and listed on the User Authority Change report. See Tracking User, Authority, and Password Updates for more information.

For more information: See the External Payment Layer RESTful Service white paper on My Oracle Support for more information on updating these settings.

External Service

Select this field to have request messages generated for the external payment service.

External URL Prefix

The prefix that forms the beginning of the URL where messages are sent.

Must begin with https.

The message type defines the endpoint suffix that is appended to the prefix, creating the entire URL. For example, for a credit card authorization request, the entire URL might be https://remote.auth.com:1234/authorization, where remote.auth.com is the remote server, 1234 is the port, and authorization identifies an authorization request.

The following endpoints are supported:

• /balanceInquiry

• /authorization

• /reversal

• /getToken

• /generateGift

• /activateGift

• /rechargeGift

• /deposit

• /return

Authentication User

The user ID for authentication of the messages to the external service.

Authentication Password

The password for authentication of the messages to the external service. Must be at least 6 positions long, include both numbers and letters, include a special character, and cannot end with a number.

Use Credit Card Tokenization (L18)

Select this system control value to replace the credit card number in the Order Management System database with a token provided by the external system. In addition, the number will be encrypted if you have credit card encryption enabled.

Require Credit Card Token (L40)

Select this system control value to require a token for a credit card number. This ensures that credit card numbers are never stored in the Order Management System database and follows full PCI compliance and maximum security of sensitive data.

If the Credit Card Tokenization Process is unable to replace the card number with a token, the system:

• During Order Entry/Maintenance, Customer Memberships, and Change Invoice Payment Method: displays the Tokenization Warning window, requiring you to enter a different form of payment.

• During web order processing: replaces the credit card number with the text TOKENIZATION FAILED and places the order in an error status with the reason Invalid Credit Card. You can correct the credit card payment method and resend the card for tokenization in batch order entry.

Unselect this system control value to allow the system to accept a credit card number that has not been replaced with a token. The credit card number will be replaced by a token during authorization processing or when you use Work with Batch Tokenization (WBTK).

Note: If you change the setting of this system control value, you must stop and restart the ORDER_IN integration layer job before your change takes effect for orders received through the Generic Order Interface (Order API).