Administration Guide for Oracle Self-Service E-Billing > Configuring Jobs > Payment Job Types >

Configuring a pmtCreditCardSubmit Job

The pmtCreditCardSubmit job selects credit card payments that are scheduled to be paid within a configurable number of days before today, and opens a connection to a credit card payment gateway to authorize and settle those transactions. Both authorization and payment are done at the same time.

The pmtCreditCardSubmit job submits credit cards to a credit card gateway to be processed. It searches the creditcard_payments table to find all scheduled credit card payments whose status field is scheduled (6) and whose pay_date field has a date the same as or prior to one day after the day the job is running (by default), and sends them the credit card gateway for processing.

Credit card account information is saved by the Payment module as part of the payment when the payment is scheduled. Whether this copy of the account information is used for submission depends on the contents of the PID field:

• When PID is not null, the saved account information is used to extract the latest credit card account information from the enrollment database, and the extracted account information is used for submission. Using the account information from the enrolled database eliminates any potential problems related to changing or deleting a credit card account after the payment is scheduled. The Cancel Payment if Credit Card Account has Expired parameter determines which action to take with scheduled payments when the credit card account is changed.
• When the PID is null, the saved copy of the credit card account is used. Using the saved copy of the credit card account is useful when the PID cannot be found in enrollment database, such as when a customer database offers payment account information but does not have a unique PID.

If pmtCreditCardSubmit is successful submitting the credit card payment, the payment is approved, money is guaranteed to be transferred, and the status of the payment is set to settled (8). If there is a problem submitting the payment, its status is set to failed-authorize (-4).

The Payment module supports the PayPal Payflow Pro and uses HTTP to communicate with it. If there is a network problem, the status of the payment stays scheduled, but the payment txn_err_msg field gets the error message, ensuring that the payment will be picked up by the next run of the pmtCreditCardSubmit job. If the payment is successful, the Payment module stores the confirmation number from PayPal Payflow Pro in the txn_number field of the creditcard_payments table.

Table 30 describes the columns in the CHECK_PAYMENTS table updated after a credit card is submitted.

Parameters for Configuring the CreditCardSubmitTask

The configuration parameters for the CreditCardSubmitTask task are:

Table 31 describes the configuration parameters for the CreditCardSubmitTask.

Using PayPal Payflow Pro Threads

To speed up credit card processing, you can use simultaneous connections (threads) with PayPal Payflow Pro. By default, the Number of Threads field in the Payment Settings is 1, but you can enter a larger number to speed processing.

However, there is a bug with the PayPal Payflow Pro SDK, which causes a connection failure when the number of threads is too high. Connection failures can be significantly reduced by using multiple copies of the PayPal Payflow Pro certificates. By default, there is only one certificate.

Connection failures caused by the PayPal Payflow Pro bug are not fatal. The Payment module recognizes the failure and keeps the payment's status as scheduled so that the failed payments process the next time the pmtCreditCardSubmit job runs. If you increase the number of threads and find there are failures, schedule your job run twice, back to back.