diff --git a/content/payments/bbps/quickstart/api-integration.mdx b/content/payments/bbps/quickstart/api-integration.mdx index 22b9bc23..13380582 100644 --- a/content/payments/bbps/quickstart/api-integration.mdx +++ b/content/payments/bbps/quickstart/api-integration.mdx @@ -7,7 +7,7 @@ visible_in_sidebar: true ## API Integration -Start by signing up on The Bridge ↗, if you haven’t already. This is Setu’s single portal for managing all your integrations with us. +Start by signing up on The Bridge ↗, if you haven’t already. This is Setu’s single portal for managing all your integrations with us. If you face any issues with integration, raise a support ticket ↗ and our team will reach out. @@ -17,18 +17,18 @@ If you face any issues with integration, list of products offered by Setu, and select one of the product cards under Payments > Collect BBPS. +The primary entity on the BBPS network is called a “biller”. Go to the list of products offered by Setu, and select one of the product cards under Payments > Collect BBPS. -You will see multiple Collect BBPS cards, each by a different bank provider. While the underlying bank might differ, the product experience itself remains consistent across providers. Click on one of those cards, and you should see the full profile page with more details about the product. Click on the “Create a biller” button. +Click on one of those cards, and you should see the full profile page with more details about the product. Click on the “Create a biller” button. Here, enter the name of the biller. This is what your customers will see and search for in the payment apps, so make sure it has no errors. -Below that, select the category this biller belongs to. Right now Setu supports only two categories, but should begin adding more soon. Now click on the “Create biller” button. +Below that, select the category this biller belongs to. Now click on the “Create biller” button. And done! The biller has been created, and you can proceed to the biller dashboard. @@ -52,10 +52,10 @@ And done! The biller has been created, and you can proceed to the biller dashboa
-After the biller creation step, we should be on the biller profile. Here, you will see four tabs—**Dashboard**, which is an overview page, **Configuration** has all the integration details for this biller, **Transactions** where you can see test payments made to this biller, and **Copy to Production**, to copy the same config to Production later. +After the biller creation step, we should be on the biller profile. Here, you will see four tabs—**Dashboard**, which is an overview page, **Add biller details** has all the integration details for this biller, **Test bill fetch and notification** where you can see test payments made to this biller, and **Setup details for production**, to copy the same config to Production later, **Add KYC details** where you need to provide essential business documents and verification details. This information is used to verify your business identity and ensure compliance with regulatory requirements. @@ -79,7 +79,7 @@ Begin by defining _at least_ one identifier. An app like PhonePe or GPay will as
@@ -143,7 +143,7 @@ The `callbackURL` is for Setu to send notifications for `BILL_SETTLEMENT_STATUS`
@@ -158,7 +158,7 @@ If you require notifications along with every settlement event, then setup the ` Settlement accounts are where Setu will deposit money into after the customer has made the payment. Keep in mind that in Sandbox, these are mocked, and involve no money movement. diff --git a/content/payments/bbps/reports.mdx b/content/payments/bbps/reports.mdx index eb6576a5..50f51fb3 100644 --- a/content/payments/bbps/reports.mdx +++ b/content/payments/bbps/reports.mdx @@ -16,10 +16,10 @@ The request format is detailed below— URL - Production: https://bifrost.setu.co/bifrost/collect/reports + Production: https://bifrost.setu.co/bifrost/v2/collect/reports
Sandbox:{" "} - https://uat-bifrost.setu.co/bifrost/collect/reports + https://uat-bifrost.setu.co/bifrost/v2/collect/reports