Scribd
Upload
41 views15 pages

BBPS API Specification v14 Implementation Guide

The Bharat Bill Payment System (BBPS) API Specification v14.0 outlines the implementation guide and technical overview for bill fetching, payment processing, and status checks. Key updates include the introduction of Julian Date for ID generation, new payment channels, and enhancements to response structures. The document also emphasizes the importance of security protocols and error handling mechanisms to ensure efficient transaction management.

Uploaded by

deepshah112
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
41 views15 pages

BBPS API Specification v14 Implementation Guide

The Bharat Bill Payment System (BBPS) API Specification v14.0 outlines the implementation guide and technical overview for bill fetching, payment processing, and status checks. Key updates include the introduction of Julian Date for ID generation, new payment channels, and enhancements to response structures. The document also emphasizes the importance of security protocols and error handling mechanisms to ensure efficient transaction management.

Uploaded by

deepshah112
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
BHARAT BILLPAY BBPS API Specification v14.0 Implementation Guide & Technical Overview VERSION DATE DOCUMENT SCOPE 14.0 20.02.2021 Bill Fetch, Payment, Status Check, Plan MDM ‘Architectural Blueprint for Implementation eee The BBPS Ecosystem & Architecture OFF-US Transaction Customer BBPCU Biller « BBPOU (Central Unit / >| BBPOU > xmuover | (cou) | XML over Switch) xml over | (BU) | XML over foot | HTTPS HTTPS HTTPS HTTPS “Sage Customer System Ape BBPCU BBPOU Agent OFF-US Transaction The Central Unit (NPCI) Bharat Bill Payment Customer touchpoint A transaction where the . Operating Unit. (Retailer, Bank Branch, Biller OU and Customer OU Acts as the switch App) facilitating the bill are different entities. The ensuring interoperability between all participants. Authorized banking/non- banking entity. payment. primary focus of this spec. BHARAT BILLPAY Critical Updates in Version 14.0 Key changes from Document History [20.02.2021] ID Generation Logic Introduction of Julian Date in Ref ID & Msg ID generation logic. Critical update for uniqueness. New Payment Channels Introduction of OR & Paylnk flows. New drectBlichanne attribute New MDM APIs. Introduction of Pian MDM APIs (Prepaid) and Biller Status APIs (Health Checks), Response Enhancements ‘New ‘Adaitionalinfo’ biock in Payment & 402 Responses. New ‘visibility’ attribute in CustomerParams. MIGRATION NOTE: The ID generation logic change is a breaking change. Ensure all ID generators are updated to the Julian Date format immediately. The Bill Fetch Workflow commme [peur [| [onroul Tees Inte Feteh BiiFetchRequest Route Request BiiFetchResponse Route Response XML Structure: Request LetedRequest> sua — originating OU ‘hen ta 2021,.." dteeteslienanele sin isiseores> “Score types" THNRISK" vat eprisiscores> 508987198"> < Mobile Number [Link] /> = Mandatory Bill Fetch Response & Transaction Binding Data Model Bill Customer Name "Manoj Chekuri" Amount, "1200.00" Due Date "2021-09-24" Bill Number "1232332" Bill Period "MONTHL' Ref ID ‘The Ref ID binds this specific fetch result to the subsequent payment. XML Response Snippet < « < in v14.0 for Payment Parans --> < ee a Final Status — Result Node Auto-Reverse Money FAILURE Complaint Management System (CMS) (BB kaise compiaint (500 Transaction-based initiation If resolution is unsatisfactory. Complaint Status (506) Paling for updates ‘Complaint Closure (507) Final resolution by Biller/CU. teas + 502: Complaint Re-assignment = Callback APIs. (New in v14.0) Biller Master Data Management (MDM) Dynamic Ul Configuration Dynamic UI Configuration Key MDM Features (v14.0) Input Parameters Defines what the user must enter (e.g., Account No, Mobile). Either/OR Logic Allows flexibility in customer identification. ‘Param nane='Hobite' /> OR

You might also like