2. Agenda
Sl. Action
1 Welcome Address by A.R. Ramesh – Chief Project Officer, BBPS
2 Key Note Address by Dr. Pramod Varma – Member, Technology Advisory Committee, NPCI
3 BBPS Product & Business over view – Rahul Tandon, AVP – BBPS
4 BBPS Technology Walk Through – Arulananda Selvakumar – VP – Technology, BBPS
5 BBPS – Virtual API Sandbox Launch – Dr. Pramod Varma
3. Bharat Bill Payment System
Bharat Bill Payment System (BBPS) is a Reserve Bank of India (RBI) conceptualised system
which offers integrated, accessible and interoperable bill payment services to consumers
across geographies with certainty, reliability and safety of transactions.
Consumer
Website/Internet Banking of Non-banks/Banks
Bank/Non-bank entity
facing Customer Bank/Non- bank
entity connected
with Utility Cos.
Utilities e.g.
Electricity, Water,
Gas, telecom
1.Consumer (Payer) uses a
channel for payment
2. Bank/Non-bank debits the
account, collates information
and transmits to BBPCU
3. BBPCU undertakes settlement
between BBPOUs and passes the bill
information and payment message
4. Utility connected Bank/Non-
bank entity sends information to
Utilities and credits accounts
Agents/Retail shops/ BCs of Banks/Non-banks
Mobile App of Banks/Non-banks
4. Salient Features
Interoperable
Connecting all at one place
Accessible
Digital &Physical
Cost-effective
Flat fee compared to advolerm
Complaint Management
Standardized-both ON-US & OFF-US
Standards
Standard Processes-
Integration
One point access
Brand Connect
Single and trusted brand connect
5. How BBPS is Organized
Operating Unit 1
(COU)
Agent Institution
Operating Unit 2
(BOU)
App 1/Internet 1/Bank-BranchAgent 1
Biller 1
Level 1
Level 2
Level 3
Level 4
BBPCU
Biller Circles
7. Payment Options
Internet | Internet Banking| Mobile | Mobile Banking |POS | MPOS
| KIOSK | ATM | Bank Branch | Business Correspondents | Agents
Payment Channels
Cash | Credit Card | Debit Card | IMPS | Internet Banking | Account
transfer | Prepaid Card | Wallet| UPI |AEPSPayment Mode
Full | Minimum | Excess | Part | Penalty | MultiplePayment Options
8. Bank/Non-Bank
which is Customer Facing
Default Biller aggregators
i.e. Biller Operating Units
AGENT/RETAIL SHOP
BILLERS
CONSUMER
1
2
3 4
56
78
9
10
Physical Transaction Flow
9. BILLERS
CONSUMER
Digital -Transaction Flow
Transaction flow
Bank/Non-Bank
which is Customer Facing
Default Aggregators/Biller aggregators
Biller Operating Units
1
2 3
45
6
7
8
Digital
Channels
like Mobile
, Internet,
POS
Digital Transaction Flow
11. Benefit Consumers
Control Payment of bills via one platform, instead of using different websites, apps, or going to various outlets
and biller collection points. Consumer will get all his billers on one single platform/channel
Accessibility Facility of paying all bills Digitally (Internet, Mobile, POS, Kiosk etc.) as well as Physical (Agents/Retail
shops, Bank-branches, BCs etc.) channels of his choice.
Consumer will get access to all billers even via going to his Co-operative or RRB bank Branches/Channels
Cost-effective Consumer’s saves on travel cost to various locations and charges incurred on various Utility companies
website.
Also on physical Outlet where the Consumer used to pay up to ₹10-50 per bill, BBPS has capped the
Convenience fee in the range of ₹5-25
Convenience Payments of bills Anytime Anywhere with ease of convenience. E.g. Consumer being in Mumbai can pay
his Meghalaya bills via any channel
Uniform
Experience
Uniform and seamless experience across all channels-digital and physical.
The interface consumer uses on a bank mobile app or Internet banking of some other bank would be the
same
Assurance &
Reliable Service
Assurance of transaction via secured bill payment system, reliable and easy resolution of complaints and
disputes regarding his bill payment.
Consumer can go to any bank app or any bill payment website or BBPS Website and make a complaint
regarding his bill payment issues.
Instant
Confirmation
Instant Confirmation of bill payment via SMS/Print-receipt/E-mail/Web confirmation with BBPS Logo
Benefit to Consumers
12. Key Parameters of Bill Fetch API
Bill Fetch Request
(Initiated by the
Customer-BBPOU)
This API will enable the user to input certain parameters as required by the biller
to fetch bill information.
Customer identification parameters at the biller can be more than one and the
system is capable of supporting the same.
Key Parameters include : <Initiating Channel>, <Agent Details>, <Biller
Information>, <Bill Details>, <Customer details>
Bill Fetch Response
(Initiated by Biller-
BBPOU)
This request will enable the biller to provide output parameters as a response to
bill fetch request.
Biller can respond with multiple amount field, additional fields regarding bill and
any other information as desired by the biller
Key Parameters include: <Customer Information>, <Bill Information>, <Charges &
Fees>.
* All input and output parameters will be configured at biller level at the time of Biller Onboarding
13. Key Parameters of Payment Message API
Payment Request
(Initiated by the
Customer-BBPOU)
This request will enable the user to provide parameters defining the payment
request details as per biller configuration.
Key Parameters include: <Channel>, <Payment Mode>, <Biller & Bill Information>,
<Customer Information>
Payment Response
(Initiated by Biller-
BBPOU)
This request will enable the biller to confirm the payment parameters.
Key Parameters include: <Bill Information>, <Transaction Status>
* All input and output parameters will be configured at biller level at the time of Biller Onboarding
* Bill Payment Request API includes all details of the previous Bill Fetch Response
14. Key Parameters of Online Specs
* All input and output parameters will be configured at biller level at the time of Biller Onboarding
* Bill Payment Request API includes all details of the previous Bill Fetch Response
Diagnostic Diagnostic message is a confirmation from the BBPOU to BBPCU that the respective BBPOU
is in active status and available for receiving and processing bill payment transaction
BBPOU will be triggering the diagnostic API at a desired time-frame, continuous failing of
these ping requests will mark the BBPOU inactive and transaction will not be processed at
BBPCU end.
Acknowledgment An acknowledgement message is a confirmation sent in synchronous mode from the
recipient to the sender of a message and will be a part of each leg of the payment
transaction message.
Reversal Failure to receive an acknowledgement from any participant in BBPS for a bill payment
transaction will result in a reversal where the entire transaction will be reversed and an
intimation will be sent to the origination point to return the amount to the customer
through the same payment mode.
The initiating party is the entity which has initiated a leg of the bill payment transaction but
has not received its acknowledgement.
15. ID Logic
Particulars Length Logic Example
TRANSACTION REF ID 12 Customer BBPOU code - 4;
Random alphanumeric character - 8
TJ0129197644
AI ID 4 Alpha - 2;
Numeric - 2
TJ03
AGENT ID 20 Customer BBPOU ID - 4;
Agent Institution ID - 4;
Agent Payment Channel Code - 3;
Random number - 9
TJ01TJ03BNK000000001
16. What’s New!
Bharat BillPay Website Features
Agent Outlet Locator
Documents
Phase-II Customer registration, VAS
Alerts , Reminders
Complaint Management & query
Bill Presentment & SI Module,
Standards
• List of billers at one go!
• Add billers and register for billers
• Standards for bill reciept, SMS and other
business standards
• Front-end standards and technical standarsd
BBPCU Canvas
Admin Portal for BBPOUs
Easier on-boarding Billers,Agents & AIs
MIS , Reports and Dashboard
CMS, DMS Portal
Centralized Complaint & Dispute
Raise complaints transaction service
based.
Register anywhere Website Portal, Agent
outlet or any bank portal.
2-3 days resolution time
17. Biller can have many
relationship
Prepaid Category Inclusion
Breakage of Bilateral
Opening up of More Channels
Standing Instructions
Mandate Management
Increase in Channels
19. • Prerequisites for On Boarding
• API List
• Certification Platform
• Detailed API Walkthrough
• BBPSim Unveiling
• BBPSim Demo
• BBPSim Snapshots
Agenda
20. Network Requirements
Network bandwidth: Typically a BBPOU would need a minimum of 1 Mbps MPLS link to
communicate with BBPCU for a 50 TPS throughput BBPOU system.
Network IP and Port details: BBPCU SPOC will provide the IP and Port details on request while
establishing connection with BBPCU.
Software Requirements
NPCI does not mandate implementation of any specific software stack for the BBPOUs.
BBPOU can deploy their own software stack which is capable of sending and receiving signed XML
messages with BBPCU.
Pre-Requisites For On-boarding (1/3)
21. Security Requirements
The system will have appropriate treatment for sensitive data and private data. There will be appropriate access control and
authentication mechanism.
Transport Layer Security:
All REST messages will be exchanged over TLS (v1), i.e. HTTPS
Message Security and Non-Repudiation:
All REST messages will be digitally signed
Data Security (data at rest):
All sensitive data will be encrypted and stored
Pre-Requisites For On-boarding (2/3)
22. Pre-Requisites For On-boarding (3/3)
Other Prerequisites
Availability of BBPS Technical and Message Specifications
BBPOU’s application readiness as per the BBPS specifications and data compliance
Secured data transmission using TLS 1.2 standards
Provision for data integrity using standard C-3 Digital Certificate
Connectivity to NPCINET
23. 1. Bill Fetch Request
2. Bill Fetch Response
3. Bill Payment Request
4. Bill Payment Response
5. Diagnostic Request
6. CMS Request (401,501,506)
7. CMS Response
8. Biller MDM Request
9. Biller MDM Response
API List For Online Messages
24. Sandbox Testing
Comfort Testing
Certification
Necessary testing requirements will be verified at Sandbox test platform
Initial round of testing conducted at participating BBPOU to test and verify
the possible structural / logical and compliance
On successful completion of comfort testing, BBPOU will be given the
schedule for certification
Certification Platform
25. Transaction Initiated by Customer BBPOU
Customer BBPOU sends the API transaction request to BBPCU
BBPCU routes the transaction request to Biller BBPOU simulator installed at BBPS environment
Biller BBPOU Simulator responds back to BBPCU
BBPCU forwards the response to Customer BBPOU application
Customer BBPOU
Application BBPCU
Biller OU Simulator
@ BBPS Env.
Customer OU connects with BBPS Sandbox
Transaction Flow in BBPS Certification Environment
26. Transaction Initiated by Biller BBPOU
Customer BBPOU simulator @ BBPS Environment sends the API transaction request to BBPCU
BBPCU routes the transaction request to Biller BBPOU system
Biller BBPOU system responds back to BBPCU
BBPCU forwards the response to Customer BBPOU simulator
Customer OU
Simulator
BBPCU
Biller OU Application
@ BBPS Env.
Biller OU connects with BBPS Sandbox
Certification Environment…continued
27. BBPS APIs List
API Name Purpose
Diagnostic Request Heartbeat request to be sent by OUs and participating AIs every 3 minutes
BillFetch Request To Fetch customer’s bill details
BillFetch Response Response to the Bill Fetch request containing the bill details.
BillPayment Request To initiate a Bill Payment
BillPayment Response Response for the payment request containing status of payment
Complaint and Transaction
Status Requests
To check status of a transaction,
Register new complaint,
Check status of a complaint
Complaint and Transaction
Status Response
Response to the Complaint request
Biller MDM Fetch Request to fetch Master data of billers available in BBPS
Biller MDM Response Response sent to the Biller MDM request.
Provides details of all the Billers available in BBPS.
Restricted - BBPS