Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Overview

DIGIT is India's largest open-source platform for Urban Governance. It provides API-based access to governance functions enabling Urban Local Bodies (ULBs) to provide citizen facilities via integration with relevant service players.

Purpose

This document aims to provide information on how to integrate third-party(BBPS) Billing and Collection services with the DIGIT governance platform. It enables system integrators to get the system to create and update bills, record payments, and generate receipts for the amount paid. However, this document does not include information about any third-party system, DIGIT configuration outside the stated scope, installation, or deployment of either the third-party software or DIGIT.

Intended Audience

System Integrators (SI)

Prerequisites

  • Knowledge of REST API usage

  • Knowledge of JSON

Steps to Integration

  1. User - Create a new user with type as SYSTEM for 3rd Party system. The user’s login and its generated token should be bound to a specific set of whitelisted IPs.

  2. Bill - The 3rd party should call fetchBill from the server-side to fetch the bill details.

  3. Transaction - The 3rd party service will call transaction/_create to initiate a transaction before accepting the payments from the customer.

    After payment completion transaction/_update will be called to mark success or failure of the transaction. The transaction/_update should only be allowed to the user who created the transaction. Transactions once marked successful/failed should not be allowed to be updated. 

    On successful transaction, the receipt should be created automatically with a receiptdate as the transaction create date. In cases when bills are only valid for a day, these bills should be handled for transaction success delays. https://www.getpostman.com/collections/3a1626684a1585abf9ee

API List

Title

Link

Comment

/pg-service/transaction/v1/_create

https://www.getpostman.com/collections/3a1626684a1585abf9ee

/pg-service/transaction/v1/_update

https://www.getpostman.com/collections/3a1626684a1585abf9ee

/billing-service/bill/v2/_fetchbill

https://www.getpostman.com/collections/3a1626684a1585abf9ee

To search bill

/collection-services/payments/_create

https://www.getpostman.com/collections/3a1626684a1585abf9ee

To make payment

/user/users/_createnovalidate

https://www.getpostman.com/collections/d5c6e514fe7cfbce9086

A user of type SYSTEM with BBPS specific role mapped to be created. The SYSTEM user will not have access to application. Only API’s can be accessed.

/user/oauth/token (to generate authtoken)

https://www.getpostman.com/collections/7f88876f7b4c5d796428

/ACCESSCONTROL-ROLES/roles.json

{ "code": "BBPS_ADMIN",

"name": "BBPS ADMIN",

"description": "Role for BBPS ADMIN"

}

BBPS Specific role to be added in state specific MDMS repository

/ACCESSCONTROL-ROLEACTIONS/roleactions.json

{ "rolecode": "BBPS_ADMIN", "actionid": 1812, "actioncode": "", "tenantId": "uk" },

The required actions to be mapped for BBPS role.

(Note: All the API’s are in the same postman collection therefore same link is added in each row)




  • No labels