Bulk Bill Payment Service

Mohamed Taman

Systems Architect & Design supervisor.

efinance

Agenda

1. Introduction.

2. What is the Bulk bill service?

3. Service participants.

4. System business flow.

5. Requirements.

6. Best architecture practice.

7. Supporting technologies.

8. Benefits.

9. Questions.

Introduction

In this presentation we will see how the best Architecture is used to develop the Bulk Bill Payment System, which enables ease of integration between different entities to the core service especially bank entity.

What is the Bulk bill payment service?

Bill Payment Service is a generic Electronic Bill Presentment and Payment (EBPP) service that enable different parties to share a common infrastructure that enables the Billers to integrate with the system for bill presentment, and the Banks for bill enquiry and payment.

Service Participants

BanksBulk Bill Payment Service

Billers

Requests Requests

ResponsesResponses

Service Participants - Continued

Bank

The channels of the Banks will interact with Bill Payment Service in real-time through the Banks’ back-end systems for all customer-facing scenarios or through the service portal.

Also Interested banks for enabling such a service (BBPS) through their internet banking will be through service Online Interface.

Biller

Billers will upload bill summary data to Bill Payment Service on a regular schedule that gets stored in the Bill Payment Service database for Offline mode.

Bill Payment Service will consolidate bill summary data from the various Billers and present it to the relevant bill payer upon a request initiated from the Banks’ channels.

Also Billers will provide bill summary data to Bill Payment Service instantly for Online mode.

Service Participants - Continued

Customer

Customers may follow a query on their bills with the payment of single or multiple bills. The Banks’ systems will capture the payment information entered by the Customers and forward it to BPS for validation.

BPS will apply business rules and determine if the payment initialized by the Customers is valid. BPS will send back the results of the validation to the Banks.

If the payment is found to be valid, the Bank will collect payment from the Customers. Payment collection will be done either by debiting the Customer’s account or by collecting the cash, depending on the channel type.

Service Participants - Continued

System business flow messages

BanksBulk Bill Payment Service

Billers

1.1- Bill Inquiry request

1.2- inquiry load request

1.3- inquiry load response1.4- Bill Inquiry

response

Bills load request

Bills load response

2.1- Bill payment Advice

2.4- payment Advice response

2.2- Payment Notification

2.3- Payment notification response

Requirements

Requirement is to build a system, run by the government to facilitate bill services providers such as Universities , Water, Electricity, phone, Gas … etc. entities customers, to pay their bills through different channels, with strong security requirement to protect the payment process and its data.

The Channels Provided by a wide coverage from banks through their branches, ATMs, internet banking and even ministry of finance ATMs or any other channel interested for providing such a service.

Best architecture practice

Banks

BPS CV2S

Billers

Admins

OSB

OSBA

da

pte

rA

da

pte

r

Ad

ap

ter

Ad

ap

ter

WS Adapter

RequestsResponsesSecurity checks

Reports & SLA

Monitoring

Requests

Responses

Utility & ASs

Requests

Responses

Utility & ASs

Message Engine

SOA

Supporting technologies

The architecture & design decision goes to choose a SOA suite that includes also Service bus for the system implementation.

As the system involves many integration with different entities, as long as message processing that could be done through already made powerful product such Oracle OSB.

We used oracle SOA suite to use business process management (BPM) for service reports and SLA monitoring.

Finally The supporting backend database is Oracle database 11g

Benefits.

1. Ease of integration.

2. Time to marked.

3. Better support.

4. Reduces boilerplate of coding.

5. Isolating the core business products from out world interfacing.

6. SOA governance.

7. Adding new services by integrating already developed services.

8. Best security achievement.

9. Integrate to new products to add new services.

10. Centralized processing and business filtration.

Thanks for listening

Questions?