Implementation Guide for Oracle Billing Insight > Payment Processing > About Check Processing >

Example of Adding a Check Account at Enrollment

This topic shows an example of adding a check account. You might use this feature differently, depending on your business model. When a user adds a new bank account, Oracle Billing Insight verifies the account information before the account can be used to make a payment. This process can take a few days or the customer can choose to use auto verify, where the bank account can be used immediately without account verification, until a payment is rejected.

The following actions occur when a new user specifies a checking account during enrollment:

1. A new customer enrolls for check payment services by completing an enrollment form in the user interface. Oracle Billing Insight saves the information in the payment_accounts table with an enrollment status of pnd_active.
2. The pmtSubmitEnroll job runs to submit the enrollment information to the payment gateway. It changes the enrollment status to pnd_wait. If the check cannot be submitted, then the status is changed to Failed.

   For ACH only, pmtSubmitEnroll sends customer enrollment information, which is contained in a zero amount check called a prenote, to an ACH payment gateway for verification. To send a prenote, the pmtSubmitEnroll job creates a zero amount check with status of prenote_scheduled, and immediately inserts the check into the EDX_PMT_TRANSACTION table with a status of prenote_processed. This means that the status prenote_scheduled is transitory, and so is not visible in the EDX_PMT_TRANSACTION table. A summary report is created, which can be viewed from the Command Center.

3. After receiving the customer enrollment information, the ACH payment gateway responds with a return file only if there are errors in the customer enrollment information. If there are no errors, then ACH does not send a return file, or any other form of acknowledgement.
4. The pmtConfirmEnrollment job runs. This job updates the status of the customer enrollment status to Active if there are no problems after a specified number of days (by default, three days).

   If the payment enrollment information is not correct, then the pmtConfirmEnrollment job updates the customer enrollment status to bad_active. An exception report is created, which can be viewed from the Command Center.

5. The customer might optionally receive an email about enrollment status from the pmtNotifyEnroll job.