Bookshelf Home | Contents | Index | PDF     

Application Guide for Oracle Self-Service E-Billing (Business Edition) > Payment Use Cases >

About Recurring Payment Processing

In this use case, Oracle Self-Service E-Billing generates recurring payments based on user profile rules. Table 33 lists and describes the functions.

Table 33. Recurring Payment Processing
Function
Description

Name

Recurring Payment Processing

Feature Area

Payment

Users

Oracle Self-Service E-Billing

Trigger

Recurring payment job starts.

Standard Features

Email is generated when a recurring payment is scheduled.

Main Path for Recurring Payment Processing

The following path describes the Recurring Payment Processing use case:

1 Job starts.
  1. Job creates scheduled payments triggered by recurring payment rules.

Alternate Paths

Alternate paths can occur in this use case.

Threshold Exceeded

Job identifies that the recurring payment threshold has been exceeded for a recurring payment rules. Oracle Self-Service E-Billing generates email to user notifying that the payment failed. Oracle Self-Service E-Billing does not generate scheduled payment.

Expired Credit Card

Job identifies an expired Credit Card. Oracle Self-Service E-Billing generates email to user notifying that the payment failed. Oracle Self-Service E-Billing does not generate scheduled payment.

Failed Payment Request

If for some reason a scheduled payment cannot be created, Oracle Self-Service E-Billing generates email to user notifying that the payment failed.

    
Application Guide for Oracle Self-Service E-Billing (Business Edition) Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.