Bill Subscriptions Use Case
The Bill Subscriptions use case allows customers to subscribe to bill payments. New bills coming from the subscribed external company are presented to the customer for payment.
Actors: Customer, System
Pre-Conditions: The customer must be authenticated. Anonymous requests are forbidden.
Actions
1. The customer selects the Bill Subscription option in the Global Bank Web portal.
2. The system displays a list of the customer's subscribed bills.
3. The customer selects a bill payee from the list and the enters his or her account number for the selected payee.
4. The customer confirms the request and the new subscription is added to the list.
5. The system displays a unique identifier of the operation and the Bill Subscription — Receipt page.
Alternative Flows
Delete subscription: Each row on the subscribed bills section will have a delete button. If the customer clicks this button, the bill subscription is set to inactive. This will be allowed only if there are no pending bills to be paid.
Alternative Flows (out of scope)
Bill identifier validation: The customer enters a Bill Identifier that identifies the relationship between him or her and the external company. If the external company provides this service to the bank, validations will occur.
Billing Company Notification: The billing company may be notified of the subscription. Notifications will happen asynchronously, meaning that they will not affect the subscription transaction. The GBRI does not show processing that would normally occur in an offline batch mode.
Post-Conditions: Cached Account Summary Information
The cached Account Summary in the Web application is automatically updated. The Bill Subscription service returns the state of the accounts after subscribing the bills. This information is used by the Web application to update the cache.

Back To: UseCases