Administration Guide for Oracle Billing Insight > Configuring the Payments Module > Configuring Payment Gateways >

Credit Card Gateway Parameters for CyberSource


Table 67 describes the parameters you must specify when configuring a credit card gateway for CyberSource.

Table 67. Parameters for Configuring a CyberSource Payment Gateway
Parameter
Description

DDN

Name of the selected application DDN.

Payment Type

ccard

Gateway

cybersource

Batch Size for Payment Reminder Table

Specifies the number of payment reminders to be read into memory from the Oracle Billing Insight database for the pmtReminder job. Note that specifying a batch size that is too small increases the number of times the database is accessed, and specifying a batch size value that is too large could result in an excessive amount of memory being used.

A batch size of 100 is suggested for a medium-sized database, and a batch size of 1000 is suggested for a large database.

You can enter a batch size of zero to disable batched table reads, however, doing so requires a lot of memory. Entering zero means that one partition ID is created for all payments, and that all payments are processed at once instead of in batches. The resulting batch file does not have multiple batch records, which some banks prefer.

Send Email Notification when Payment Jobs are Done (With or Without Error)

The value Y enables and N disables sending of email about the status of the Payment jobs that support job status notification. Additional email information is specified in the following fields.

Mail-to Addresses (Separated by ";" Semicolon) for Job Status Notification

One or more email addresses that must be sent job status notification, separated by semicolons.

JNDI Name of IAccount

Implementation of IAccount, which must match the enrollment model, single or multiple DDNs for each user account, used by applications that use this payment gateway (DDN). Select the JNDI name edx/ejb/AdminAccount.

Implementation of IUserAccountAccessor

The name of the class that handles getting Oracle Billing Insight user information, which is determined by the type of enrollment supported.

Select the class com.edocs.common.payment.plugin.DefaultUserAccountAccessor.

Implementation of IPaymentAccountAccessor

The name of the class that handles getting Payment user information. Select the class com.edocs.common.payment.payenroll.payacct.DefaultPaymentAccountAccessor.

Enable Convenience Fee Payments for End User

Indicates whether to enable convenience fees in the Self-Service application: Y, Yes or N, No.

Enable Convenience Fee Payments for CSR

Indicates whether to enable convenience fees in the Assisted Service application: Y, Yes or N, No.

Convenience Fee Configuration Class

The name of the custom class for calculating the convenience fee. The default value is: com.edocs.common.payment.cassette.plugin.DefaultConvenienceFeeConfig.

Include Convenience Fee in Refunds?

Indicates whether to include convenience fees in refund transactions: Y, Yes or N, No.

Make Authorize Reversal Payments

Indicates whether authorize reversal payments can be made: Yes or N, No.

Batch Size for Credit Card Payment Table

Specifies the number of scheduled credit card payments to be read into memory from the Payment database for the pmtCreditCardSubmit job. Note that specifying a batch size that is too small increases the number of times the database is accessed, and specifying a batch size value that is too large might result in an excessive amount of memory being used.

A batch size of 100 is suggested for a medium-sized database, and a batch size of 1000 is suggested for a large database.

A batch size of zero can be entered to disable batched table reads, but is not recommended because it requires a lot of memory. Entering zero means that one partition ID is created for all payments, and that all payments are processed together, instead of in batches. The resulting batch file will not have multiple batch records, which some banks prefer.

Gateway Host Name

The URL to CyberSource payment gateway host that processes credit card transactions for this payment gateway.

  • Test value. https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor
  • Production value. https://ics2wsa.ic3.com/commerce/1.x/transactionProcessor

Gateway Host Port

The TCP port number to be used when contacting the CyberSource payment gateway host. Use the default value, 443.

Gateway Timeout Period for Transaction

The number of seconds the pmtCreditCardSubmit job will wait for a transaction to complete with the CyberSource payment gateway host before timing out. Use the default value of 60.

Proxy Address

The address of the proxy server. If you are using the proxy network connection, then enter your proxy setting. This parameter is optional.

Proxy Port

The port number of the proxy server: 80. If you are using the proxy network connection, then enter your proxy setting.This parameter is optional.

CyberSource access key

The access key value generated for the page encryption key when configuring the profile in the CyberSource Business Center.

CyberSource profile ID

The profile ID generated when you created the new profile in the CyberSource Business Center

CyberSource security key

The secret key value generated for the page encryption key when configuring the profile in the CyberSource Business Center.

CyberSource Standard Transaction Endpoint

The URL where the payment token creation request will be sent. When page encryption is enabled, card-sensitive data will be sent to this URL directly.

For test transactions, specify:

https://testsecureacceptance.cybersource.com/silent/pay

For live transactions, specify:

https://secureacceptance.cybersource
.com/silent/pay

CyberSource Update Payment Token Endpoint

The URL where the payment token update request will be sent. When page encryption is enabled, card-sensitive data will be sent to this URL directly.

For test transactions, specify:

https://testsecureacceptance.cybersource.com/
silent/token/update

For live transactions, specify:

https://secureacceptance.cybersource
.com/silent/token/update

Implementation of ICyberSourcePlugIn

The plug-in allows modification of whether a credit card payment is submitted, plus other actions dependent on the payments selected for settlement. For example, to deny a credit card payment dependent on additional business rules.

For information about implementing this class, contact Oracle Professional Services. The default is:

com.edocs.common.payment.cassette.creditcard.DefaultCreditCardPlugin

Flexible Field 1 (for Plug-in)

You can specify an additional field for use with the plug-in. This parameter is optional.

Flexible Field 2 (for Plug-in)

Can specify an additional field for use with the plug-in. This parameter is optional.

Number of Threads

Specifies the number of connections to open with the Chase Paymentech Orbital Payment Gateway at one time. More threads consume more resources, including network resources, but decrease the time it takes the pmtCreditCardSubmit job to complete processing credit card payments. The maximum allowed is 10. Use the default value of 1.

Administration Guide for Oracle Billing Insight Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.