Implementation Guide for Oracle Self-Service E-Billing > Payment Processing > About Check Processing >

Check Payment Transaction Workflow


Check Payment Transaction Workflow, shown in Figure 8, processes the typical ACH check payment transaction cycle (excluding transfers between the ODFI, ACH operator and RDFI).

Figure 8. Check Payment Transaction Workflow

This workflow performs the following actions:

  1. A customer logs in and schedules a new payment. This step inserts a check into the Oracle Self-Service E-Billing database with a status of scheduled.

    If the customer later cancels the payment, then the check status is changed to cancelled, but the payment remains in the Oracle Self-Service E-Billing database for the customer to view as a cancelled payment.

  2. The pmtCheckSubmit job runs. This step selects all the checks that are due for payment, creates a batch file of selected checks, and sends the batch file to the payment gateway (ODFI). It also changes the status of each selected check to Processed in the Oracle Self-Service E-Billing database.

    If the check cannot be submitted, then the status is changed to Failed. A summary report log file is generated, which can be viewed from Command Center.

  3. The payment gateway (ODFI) processes the received check payment through the ACH operator to the RDFI. In this step, if there is an error clearing the check, then ACH creates a file containing a code that indicates why the check was returned, and sends the file to Oracle Self-Service E-Billing.
  4. The pmtCheckUpdate job runs. This step changes the status of the check from Processed to Paid if there is no return code, and five business days (default) have passed.

    If the payment gateway returns the check, then the pmtCheckUpdate job updates the check's status to Returned, and saves the reason code in the txn_err_msg field of the check_payments table. An exception report is generated to summarize the information in the returned file, which can be viewed from Command Center.

    If there is an error other than returned, then the pmtCheckUpdate job changes the check status to Failed.

  5. If configured, then the pmtPaymentReminder job sends email to the customer about the status of the check payment.

Check Payment Status Workflow

Check Payment Status Workflow updates the check payment status at different stages of check payment processing.

Figure 9 shows the states that a check can be in, and the jobs that change the state.

Figure 9. Check Payment Status Workflow

Table 67 lists the statuses that can occur during a check payment transaction cycle. The values in parentheses () are the values saved in the Oracle Self-Service E-Billing database

Table 67. Check Payment Transaction Status
Transaction Status
Description

Scheduled(6)

A customer scheduled a new check payment.

Processed(7)

Oracle Self-Service E-Billing Payment processed a check and sent it to the ACH gateway.

Paid(8)

ACH paid or cleared a check.

Cancelled(9)

The customer cancelled a check.

Failed(-1)

ACH failed to pay a check failed for a reason other than returned.

Returned(-4)

ACH returned a check.

noc_returned(-5)

This customer's payment account information must be changed.

Implementation Guide for Oracle Self-Service E-Billing Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.