#How to share bills with Setu

When a customer enters their identifier on a payment app, NPCI requires Setu to respond with bill details from a biller's system. For this, the biller needs to define a way to share bills with Setu.

After configuring the expected bill format on The Bridge, the biller can use 2 different ways to do so—either via CSV upload or via API integration.

#Share bills using CSV upload

After all bill details are configured, an expected CSV file format will be generated by Setu and shared on The Bridge. Use this sample format to upload bill details.

The CSV would always include customer identifier(s) and at times, other parameters that you may have added in the “Additional information for customer” or “Bill breakup details” sections.

Additionally you would need to add the bill amount, bill due date and other details as per the CSV format.

#Share bills using API integration

Implement a baseURL path that can be called by Setu to fetch bills, using your preferred authentication protocol.

You will need to ensure that the bill response structure matches the bill configuration you have provided on The Bridge. For example, any additional info string that has been defined should exactly match the value returned in the bill response.

#Comparison between CSV upload & API integration

Both ways of sharing bills have their own advantages and pitfalls. To help you decide which solution works best for you, here's a quick comparison between the two methods—