Using this Setu API set, you can Create a VPA Add Settlement Account as a beneficiary Set Settlement Rule Update Settlement Rule Credit Notification Settlement Notification Check Transaction Status Fetch Report

Get bill API Request { "customerId": "10935351" } Note: customerId can be as per business usecase Response Success

Biller product instance ID: 888888888888888888 Sample request { "billerProductInstanceID": "888888888888888888", "customerIdentifiers": [{"attributeName":"loanNumber","attributeValue":"BYD3421UO"}] } Partial Pay allowed true

Kinara capital https://hackmd.io/@ranjth-setu/HyfJz_tFU IDFC First Bank Biller product instance ID: 353701867596809332 Sample request { "billerProductInstanceID": "353701867596809332", "customerIdentifiers": [

We need to build a fastag web app with the following capabilities. User registers/logs in. This should be a standard email/phone OTP based flow. They can apply for a fastag Data required First name last name gender

Biller product instance ID: 777777777777777777 Sample request { "billerProductInstanceID": "777777777777777777", "customerIdentifiers": [{"attributeName":"loanApplicationNumber","attributeValue":"AC2017072800280"}] } Partial Pay Allowed True

Biller product instance ID: 359530692662527340 Sample request { "billerProductInstanceID": "359530692662527340", "customerIdentifiers": [ { "attributeName": "mobileNumber", "attributeValue": "9493506633" },

If the spec is not implemented exactly as mentioned in this document, it will result in disqualfication. Your API will be tested using an automated test suite. Product note UPI apps like PhonePe will be integrating with your bill system to allow your customers pay their bills using the UPI app. You need to expose 2 APIs for UPI App to be able to query your system and get outstanding balance for a customer update your system when a payment happens.

API details to be consumed Payer App needs to consume the line items and fees in the bill object to display the break up of the bill to the end customer. These details are already sent as part of existing API integration, but Payer App is not consuming these details as of now. When Setu sends a bill as part of the fetch Bills API, it contains the following along with other details Additional fees Line items in the bill

Auths we need to support API Key in the header X-API-KEY HTTP Basic Auth with username and password OAuth 2.0 Fetch { "customerIdentifiers": [ {

API details to be consumed Sample 1 Customer name Customer account ID Bill amount Generated date Biller Bill ID Setu (platform) Biller ID Recurrence

Biller product instance ID: 358092195539977412 Sample request { "billerProductInstanceID": "358092195539977412", "customerIdentifiers": [ { "attributeName": "loan_number", "attributeValue": "TWAUG19-0001" }

Biller ID 355825503053022742 Sample request { "billerProductInstanceID": "355825503053022742", "customerIdentifiers": [ { "attributeName": "loan_number", "attributeValue": "0001LTL1004711"

Display name of Phone Pe CreditVidya Biller ID 355960384697402576 Sample request { "billerProductInstanceID": "355960384697402576", "customerIdentifiers": [

Biller product instance ID: 350628744081179669 Sample request { "billerProductInstanceID": "350628744081179669", "customerIdentifiers": [ { "attributeName": "mobile_number", "attributeValue": "9975117344" },

User story - Developer I as a developer will be able to do the following Be able to see the product documentation Be able to see the API documentation Be able to sign up on console for bill payments. Be able to see a demo for the bill payment through WhatsApp

Collect is envisioned as a replacement to NPCI BBPS That opportunity exists in other countries We can get the regulators, big banks in other countries to run BBPS like networks using Setu We just need to keep the bank integrations to become plugins or simple download/upload.

All APIs are async Each API request generates a standardized Acknowledgement from the other end. The APIs are two way. For example LSP makes a request to lender on lender API. Lender responds to LSP on LSP's APIs. Hence, each function has 2 separate APIs. For example: Create Loan Application has 2 APIs CreateLoanApplicationRequest -> Request sent by LSP to the Lender CreateLoanApplicationResponse -> Async Response sent by Lender to LSP Update APIs for MSMEs to push more data as requested by Lender Create calls should be idempotent on the requestId field i.e. two calls to CreateLoanApplication with same requestId shouldn’t result in two applications created. Lenders are advised to return the same response as sent earlier. Update APIs for MSMEs to push more data as requested by Lender

Here is how the split settlement will be specified when Setu fetches a bill from my classboard { "status" : 200, "success" : true, "data" : { "customer" : { "name" : "Ashok Kumar" }, "billDetails" : {

Access token These services are exposed with OAuth2 authentication. Please follow the below steps to send the request. URL: https://muleuat.capitalfirst.com:1447/access-token Method: GET Headers grant_type= client_credentials // This is hardcoded value as "client_credentials" client_id = Will be shared separately