Centre for Digital Public Infrastructure
english
english
  • THE DPI WIKI
    • 🎉About the DPI Wiki
    • 🔆What is DPI?
    • ✨DPI Overview
    • 📝DPI Tech Architecture Principles
      • 🔗Interoperability
      • 🧱Minimalist & Reusable Building Blocks
      • 💡Diverse, Inclusive Innovation
      • 💠Federated & Decentralised by Design
      • 🔐Security & Privacy By Design
    • 🎯DPI Implementation & Execution Guidance
    • 🆚DPG and DPI
    • ❓What DPI can I build?
    • 🥇First use case for DPI
    • 📘Inputs for designing a DPI informed digital transformation strategy
    • 💰How much does it cost to build DPI?
    • 📢Is my system a DPI?
      • TL; DR - Is my system a DPI?
  • Mythbusters and FAQs
    • 🔯DPI and Mandating Adoption
    • 🔯DPI and Private Competition
    • 🔯DPI and Privacy / Security
    • 🔯DPI and the Digital Divide
  • Technical Notes
    • 🆔Identifiers & Registries
      • Digital ID
        • Capabilities on ID system
        • ID-Auth
        • Face Authentication
        • eKYC/ Identity profile sharing
        • Single Sign On (SSO)
        • QR Code for Offline ID
    • 📂Data Sharing, Credentials and Models
      • A primer to personal data sharing
      • Data standards
      • Verifiable Credentials
      • Building Data Analytics Pipelines
      • eLockers
      • Non-personal Anonymised Datasets
    • 🔏Trust Infra
      • Digital Signatures and PKI
      • eConsent
      • eSign
    • 🛒Discovery & Fulfilment
      • Platforms to Protocols
    • 💸Payments
      • Financial Address
      • Interoperable QR Code
      • Interoperable Authentication
      • Interoperable Bill Payments
      • Cash in Cash Out (CICO)
      • Financial Address Mapper (G2P Connect)
      • G2P Payments
  • Initiatives
    • 🌐DPI advisory
    • 🚀DPI as a Packaged Solution (DaaS)
      • 💡Why do we need DaaS?
      • 🎯DaaS in a nutshell
      • 📦Pre-packaged DaaS kits
      • ♻️Reusable DaaS Artefacts
      • 3️⃣A 3-step process from idea to implementation!
      • 📈Funded DaaS Program overview
      • 👩‍💻Cohort 1: DaaS Offerings
        • Digital authentication
        • Digital credentials
        • ID Account Mapper
      • 🖥️Co-create with us!
      • 💬Upcoming DaaS cohorts
        • Functional Registries
        • AI Assistant
      • ❓FAQs on DaaS
        • Country x DPG MOU /LoI FAQs
        • Ecosystem Participation Terms FAQs
    • 📑DPI Residents Program
    • ⚖️DPI-CPA
    • 💸G2P Connect
    • 📨User Centric Credentialing & Personal Data Sharing
    • ⚕️DPI for Health
    • 🌍Agri Connect (forthcoming)
  • References
    • Glossary
    • Curated Specifications
  • Additional Info
    • 🤝Licensing
    • ✍️Contact Us
Powered by GitBook
On this page
  • Why:
  • What:
  • How:
  • Benefits:
Export as PDF
  1. Technical Notes
  2. Payments

Interoperable Bill Payments

Streamlining the process of bill payments across authorities and departments

Why:

Individuals have to pay multiple bills on a monthly basis - electricity, water, loan EMIs, mobile recharge etc. Keeping track of all individual due dates, navigating complex standalone portals and making payments for each is a difficult, time-consuming process. Often, this leads to an increase in missed payments, defaults, and subsequently, higher interest rates for individuals and a weaker economy for the country.

Centralisation of payments through a single portal is not an option - it will create a bulky, slow system that is the target of cyber attacks. It will also cause various departments to lose agency and autonomy over their own collections and create friction in society.

Leaving payments integration to private sector players is not an option either - multiple bill issuers will have to integrate with multiple different applications each, once again causing high friction, loss of opportunities and a monopolistic situation for the first mover.

The only solution lies in establishing interoperable bill payment rails through the Digital Public Infrastructure approach.

What:

Interoperable bill payments means that people should be able to view and pay all their bills through a single platform of their choice.

The bills are federated at the back end, but centralised for user experience.

Through this, the objectives of all parties are met -

  1. Bill issuers: They retain control over their own assets, and can decrease the costs of their own issuing infrastructure.

  2. Market innovation: It allows a variety of market players to innovate services, platforms and applications on top of the bill payment rails to cater to diverse segments of society.

  3. Bill Payers: Individuals now have the freedom of choice, bolstered by the variety of payment applications available to pay their bills through a single platform.

How:

To make an existing billing infrastructure interoperable, all that is needed is to simply open up the APIs (Application Programming Interfaces) of different bill issuing authorities. This enables a variety of user-facing applications to ‘fetch’ the data from the issuers and present it to the individuals through their platform.

The individuals can choose to make the payment directly from that same platform or through any other means such as cash, card or cheques.

The bill data is simply fetched from the issuing server and not stored with the individual applications.

Once the APIs are open, any market player (once it clears the necessary safety measures set out by the central bank) can use it to fetch data based on individual’s consent. There is no need to separately on-board different issuers or platforms over and over again.

Financial Model:

A variety of financial models can be established on top of this infrastructure. One common one being, that every time an intermediary fetches a bill for an individual they charge the bill issuing authority a miniscule amount (0.0x%) of the transaction. The percentage is laid out by the central bank and same for all intermediaries to ensure a level playing field.

This money is the cost of convenience for letting the bill be discovered (and hence paid) by the individual on the application of the individual’s choice. This cost is absorbed by the bill issuer and not passed on to the consumer, thus ensuring that the cost of the bill for the individual across all applications remains standardised.

Benefits:

  1. Federated control: Data continues to be stored on individual servers of issuers and is only fetched and displayed upon receiving an API call.

  2. Inclusive innovation and Interoperability: The design of the infrastructure allows for multiple market players to innovate services and platforms on top, while ensuring no additional work for bill issuers to integrate with diverse systems.

  3. Privacy and security by design: The intermediary applications cannot see, modify or force transactions. It can simply display the bills based on an individual’s consent, who are free to pay through the same application or any other means of their choice.

PreviousInteroperable AuthenticationNextCash in Cash Out (CICO)

Last updated 1 year ago

💸