...
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.
Bill - The 3rd party should call fetchBill from the server-side to fetch the bill details.
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 | ||
/pg-service/transaction/v1/_update | ||
/pgbilling-service/transactionbill/v1v2/_searchfetchbill | To search bill | |
/pgcollection-serviceservices/gatewaypayments/v1/_searchcreate | To make payment | |
/user/users/_createnovalidate (to create SYSTEM user ) | 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) | ||
/ACCESSCONTROL-ROLES/roles.json (Specific role to be added in state specific MDMS repository) |
| BBPS Specific role to be added in state specific MDMS repository |
/ACCESSCONTROL-ROLEACTIONS/roleactions.json |
| 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)
...