+# Hiding pages from the sidebar + +You can hide pages, products, or entire categories from the sidebar navigation while keeping them accessible via direct URL. This is useful for: + +- Deprecated pages that shouldn't be discoverable but need to remain accessible for existing links +- Internal or partner-specific documentation +- Draft content not yet ready for public visibility +- Sample/template content + +Use the `visible_in_sidebar` property and set it to `false`. + +--- + +### Hide a specific page + +In the MDX file's frontmatter, set `visible_in_sidebar: false`: + +``` +--- +sidebar_title: Hidden Page +page_title: Hidden Page — Setu Docs +order: 0 +visible_in_sidebar: false +--- +``` + +The page will not appear in the sidebar but can still be accessed via its direct URL. + +--- + +### Hide an entire product + +In `endpoints.json`, set `visible_in_sidebar: false` on the product: + +``` +{ + "name": "Hidden Product", + "path": "hidden-product", + "order": 0, + "visible_in_sidebar": false +} +``` + +--- + +### Hide an entire category + +In `endpoints.json`, set `visible_in_sidebar: false` on the category: + +``` +{ + "name": "Hidden Category", + "path": "hidden-category", + "order": 4, + "visible_in_sidebar": false, + "children": [...] +} +``` + +
+
+ # Using React components in MDX files List of all components and their usage can be found by visiting https://docs.setu.co/sample-category/sample-product/sample-page diff --git a/content/data/account-aggregator/api-integration.mdx b/content/data/account-aggregator/api-integration.mdx index 15bc2aea..6841ffde 100644 --- a/content/data/account-aggregator/api-integration.mdx +++ b/content/data/account-aggregator/api-integration.mdx @@ -14,7 +14,7 @@ Setu’s AA APIs can be broken down into 3 broad flows— - **Notifications flow**—To receive notifications from Setu for key events like approval/rejection of consent or be notified when FI data is ready to be fetched.
diff --git a/content/data/account-aggregator/api-integration/consent-flow.mdx b/content/data/account-aggregator/api-integration/consent-flow.mdx
index 34b2e8a7..ffb92697 100644
--- a/content/data/account-aggregator/api-integration/consent-flow.mdx
+++ b/content/data/account-aggregator/api-integration/consent-flow.mdx
@@ -407,7 +407,7 @@ In the Account Aggregator (AA) ecosystem in India, the multi consent feature all
-
+
##### Features
diff --git a/content/data/account-aggregator/api-integration/data-apis.mdx b/content/data/account-aggregator/api-integration/data-apis.mdx
index 9ef86f5c..d68da34d 100644
--- a/content/data/account-aggregator/api-integration/data-apis.mdx
+++ b/content/data/account-aggregator/api-integration/data-apis.mdx
@@ -12,7 +12,7 @@ Below is a summary of the APIs you need to use to fetch FI data. These APIs are
- **Create Data Session**—Call this API against an `APPROVED` consent. This initiates data preparation at user's linked FIP accounts. You will be notified by Setu once the data is ready to be fetched.
- **Fetch FI data**—Fetch decrypted FI data with data session id.
-
+
@@ -455,7 +455,7 @@ Auto-Fetch data feature aims to absorb this complexity from the FIUs. With Auto- - For one time consents, Auto-Fetch executes only once, right after the consent is approved. - For recurring consents, Auto-Fetch can fetch data periodically. Set up the frequency of Auto-Fetch data in your configuration on the Bridge. -
+
+ 
+ 
+ 
diff --git a/content/data/account-aggregator/multi-aa-gateway.mdx b/content/data/account-aggregator/multi-aa-gateway.mdx index 04adbfde..9fb3013b 100644 --- a/content/data/account-aggregator/multi-aa-gateway.mdx +++ b/content/data/account-aggregator/multi-aa-gateway.mdx @@ -12,7 +12,7 @@ Setu’s multi-AA gateway is a powerful enhancement for Account Aggregator (AA) This improves consent conversion, offers redundancy with multiple AA partners, and ensures higher performance across AA integrations.
- Create Account Aggreagator Data product -
+ 
@@ -53,7 +53,7 @@ You can also enable developer specific features to reduce your integration effor - Partial fetch - Auto-Fetch data -
+
@@ -80,7 +80,7 @@ You will be notified for two types of events— You can read about notifications in detail here. - +
@@ -88,7 +88,7 @@ You can read about notifications in detail diff --git a/content/data/account-aggregator/v1/api-integration.mdx b/content/data/account-aggregator/v1/api-integration.mdx index 15bc2aea..6841ffde 100644 --- a/content/data/account-aggregator/v1/api-integration.mdx +++ b/content/data/account-aggregator/v1/api-integration.mdx @@ -14,7 +14,7 @@ Setu’s AA APIs can be broken down into 3 broad flows— - **Notifications flow**—To receive notifications from Setu for key events like approval/rejection of consent or be notified when FI data is ready to be fetched.
+
<hr class=){kind=link}
diff --git a/content/data/account-aggregator/v1/api-integration/data-apis.mdx b/content/data/account-aggregator/v1/api-integration/data-apis.mdx
index 76c05121..78dd5e47 100644
--- a/content/data/account-aggregator/v1/api-integration/data-apis.mdx
+++ b/content/data/account-aggregator/v1/api-integration/data-apis.mdx
@@ -12,7 +12,7 @@ Below is a summary of the APIs you need to use to fetch FI data. These APIs are
- **Create Data Session**—Call this API against an `APPROVED` consent. This initiates data preparation at user's linked FIP accounts. You will be notified by Setu once the data is ready to be fetched.
- **Fetch FI data**—Fetch decrypted FI data with data session id.
-
+
diff --git a/content/data/account-aggregator/v1/embed-setu-aa.mdx b/content/data/account-aggregator/v1/embed-setu-aa.mdx index d363a943..e5133036 100644 --- a/content/data/account-aggregator/v1/embed-setu-aa.mdx +++ b/content/data/account-aggregator/v1/embed-setu-aa.mdx @@ -30,7 +30,7 @@ Please find the below integration steps to embed Setu’s consent manager screen Redirect your customer to consent manager `url` received after Create Consent request. Once your customer has approved or rejected consent, this final screen in the consent manager will show a button that will redirect your customer to the `redirectUrl` provided by you in the Create consent API. - + ### React Native diff --git a/content/data/account-aggregator/v1/overview.mdx b/content/data/account-aggregator/v1/overview.mdx index 6962492a..d70f8903 100644 --- a/content/data/account-aggregator/v1/overview.mdx +++ b/content/data/account-aggregator/v1/overview.mdx @@ -19,7 +19,7 @@ Account aggregators(AAs) are diff --git a/content/data/account-aggregator/v1/postman.mdx b/content/data/account-aggregator/v1/postman.mdx index 30240cb6..a2c1ecec 100644 --- a/content/data/account-aggregator/v1/postman.mdx +++ b/content/data/account-aggregator/v1/postman.mdx @@ -26,7 +26,7 @@ Postman collection comes wth default test credentials. Set the following variabl - Set `client_secret` to the FIU app client secret received on Bridge. - Set `mobile_number` to the user's mobile number that will be used for testing. - +
+ 
@@ -40,7 +40,7 @@ You can read a bit about the FIU product on the profile page before clicking on
Enter a name for the FIU app. This is what the FIU will be registered as eventually, but you can always edit before going live.
@@ -52,7 +52,7 @@ Setu provides a set of prebuilt screens that your customer sees upon receiving t
You can theme these screens to match your brand—add your logo, primary and secondary colours, font colour and background colour—to provide a seamless UI transition for your customers.
-
+
@@ -79,7 +79,7 @@ You will be notified for two types of events— You can read about notifications in detail here. - +
@@ -87,7 +87,7 @@ You can read about notifications in detail diff --git a/content/data/account-aggregator/v1/request-signing.mdx b/content/data/account-aggregator/v1/request-signing.mdx index 6ca3a651..5cbd9856 100644 --- a/content/data/account-aggregator/v1/request-signing.mdx +++ b/content/data/account-aggregator/v1/request-signing.mdx @@ -44,7 +44,7 @@ A public-key-private-key pair is required for the request signing. In the Setu Bridge, you can generate these keys with just a simple click of a button and download the keys in CSV format. - + Setu will share its public key during the creation of app (available in the "grab credentials" step). Your app code will use this key to verify requests from Setu. diff --git a/content/data/bav/bundled-bav.mdx b/content/data/bav/bundled-bav.mdx new file mode 100644 index 00000000..d1fa4870 --- /dev/null +++ b/content/data/bav/bundled-bav.mdx @@ -0,0 +1,6 @@ +--- +sidebar_title: Bundled BAV +page_title: Bundled Bank Account Verification +order: 2 +visible_in_sidebar: true +--- diff --git a/content/data/bav/bundled-bav/api-integration.mdx b/content/data/bav/bundled-bav/api-integration.mdx new file mode 100644 index 00000000..d0934f57 --- /dev/null +++ b/content/data/bav/bundled-bav/api-integration.mdx @@ -0,0 +1,205 @@ +--- +sidebar_title: API integration +page_title: Bundled BAV API integration +order: 2 +visible_in_sidebar: true +--- + +## API integration + +Integrating Bundled BAV into your application involves creating a verification request and handling the response flow. + +
+
<hr class=){kind=link}
+ +### Create a Bundled BAV request + +Call the API to generate a verification URL for your customer. + +
+
+
Request
++
Response
+requestId from this
+ response. You will receive the same{" "}
+ requestId in the webhook
+ notification when verification is complete,
+ allowing you to match the webhook to the
+ original request.
+
+
+
Request
++
Response
+
+
+
Request
++
Response
++ +### Open URL in webview + +Open the returned `url` in a webview within your application. The customer will see the Bundled BAV interface where they can choose their preferred verification method. + +
+ +### Handle redirect + +Once the customer completes the verification process, they will be redirected to the `redirectUrl` configured in your product settings. + +Set up an event listener in your app to detect this redirect and close the webview accordingly. + +**Example event listener pattern** + +
+ +### Webhook notification + +Once the verification is complete, Setu will send the bank account details to your configured webhook endpoint. + +
requestId that you
+ received in the create request response. Use this to match the webhook
+ notification with the original verification request.
++ +**Webhook payload** + +
+ +### Best practices + +1. **Handle webhook retries** — Make your webhook endpoint idempotent as Setu may retry failed webhook deliveries +2. **Store traceId** — Always store the `traceId` for debugging and support purposes +3. **Handle timeouts** — Implement appropriate timeout handling for the webview + +
+ +### Which BAV methods are supported? + +1. Penny Drop +2. Reverse Penny Drop +3. Mobile to Bank Account +4. UPI ID to Bank Account + +
+ +### How does it work? + +1. **Create a verification request** — Call the API with your customer's phone number to generate a verification URL +2. **Open URL in webview** — Display the URL in a webview within your app +3. **Customer completes verification** — The customer verifies their bank account using any of your enabled methods +4. **Receive webhook notification** — Once verification is complete, bank account details are sent to your configured webhook endpoint +5. **Close webview** — Set up an event listener to detect the redirect and close the webview + +
+ +### Step 1 — Get API credentials + +Contact Setu at onboarding@setu.co to get your API credentials and configure your product instance. + +
+ +### Step 2 — Configure product settings + +Work with Setu to configure the following for your product instance: + +- List of supported BAV methods +- Webhook notification URL for receiving verification results +- Redirect URL for post-verification navigation +- Primary theme color (e.g., primary button background color) +- Primary foreground color (e.g., primary button text color) +- Logo URL (optional) + +
+ +### Step 3 — Test on sandbox + +Use the sandbox environment to test the Bundled BAV flow: + +**Sandbox base URL** — `https://dg-sandbox.setu.co` + +##### API integration + +Refer to the API integration guide for detailed implementation steps. + +
+ +### Next steps + +
+ Learn how to integrate the Bundled BAV API into your + application. +
+Complete API reference with request and response schemas.
+@@ -382,7 +382,7 @@ Setu provides webhook authentication. For more details, refer to -##### 1. RPD_VERIFICATION_UPDATE Webhook +##### RPD_VERIFICATION_UPDATE Webhook This webhook is sent when the end user makes a payments. @@ -403,7 +403,7 @@ _`accountType` can be `BANK_ACCOUNT`, `PPI` or `UNKNOWN`_
_`bankAccountType` is an optional data field, you may not receive the value always. (Please contact with Setu team to know more about this feature.)_ -_The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ +_The value can be `SAVINGS`, `CURRENT`, `VIRTUAL_ACCOUNT`, `OVERDRAFT`, `UOD`, `SOD`, `PPIWALLET` ###### Examples @@ -425,7 +425,7 @@ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ "rpd" : { "success" : true, "id" : "7097e53a-ba29-48a2-983d-878433b4f33e", // the RPD request id - "upiBillId" : "907442106379798024", + "upiBillId" : "a6577bb0ae4d9301cf47c1", "data" : { "bankAccountName" : "Eve", "bankAccountIfsc" : "SBIN0000001", @@ -451,13 +451,17 @@ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ "swift": "", "upi": "true" } - } + }, "additionalData": { // if you have specified while creating RPD request "key1" : "value1", "key2" : "value2" - } + }, + "receiptId": "AXI75fc85a15ce6449491b79f8509c55a96", + "transactionId": "602185974626" } - } + }, + "status": "BAV_REVERSE_PENNY_DROP_PAYMENT_SUCCESSFUL", + "productInstanceId": "abcdefgh-c1b5-4219-a64b-abcabc123456", "traceId" : "7097e53a-baq9-4122-9d3d-8s8433b4f33e", } `} @@ -470,6 +474,73 @@ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ Example 2
+
+{`
+{
+ "event" : "RPD_VERIFICATION_UPDATE",
+ "timeStamp" : "2021-11-12T00:12:29+05:30",
+ "data" : {
+ "rpd" : {
+ "success" : true,
+ "id" : "7097e53a-ba29-48a2-983d-878433b4f33e", // the RPD request id
+ "upiBillId" : "a6577bb0ae4d9301cf47c1",
+ "data" : {
+ "bankAccountName" : "Eve",
+ "bankAccountIfsc" : "SBIN0000001",
+ "bankAccountNumber" : "48097036412",
+ "payerVpa" : "test@upi",
+ "accountType" : "BANK_ACCOUNT", // or UNKNOWN or PPI
+ "bankAccountType" : "SAVINGS", // Optional, can be null
+ "ifscCrossCheck" : true,
+ "ifscDetails" : {
+ "address": "EXPRESS TOWERS,GROUND FLOOR,NARIMAN POINT,MUMBAI 400021",
+ "branch": "Development Bank of Singapore IMPS",
+ "center": "MUMBAI",
+ "city": "MUMBAI",
+ "contact": "+912266388888",
+ "district": "MUMBAI",
+ "imps": "true",
+ "iso3166": "IN-MH",
+ "micr": "400641002",
+ "name": "Development Bank of Singapore",
+ "neft": "true",
+ "rtgs": "true",
+ "state": "MAHARASHTRA",
+ "swift": "",
+ "upi": "true"
+ }
+ },
+ "additionalData": { // if you have specified while creating RPD request
+ "key1" : "value1",
+ "key2" : "value2"
+ },
+ "receiptId": "AXI75fc85a15ce6449491b79f8509c55a96",
+ "transactionId": "602185974626",
+ "addOnFields": {
+ "psp_app": "PayApp"
+ }
+ }
+ },
+ "status": "BAV_REVERSE_PENNY_DROP_PAYMENT_SUCCESSFUL",
+ "traceId" : "7097e53a-baq9-4122-9d3d-8s8433b4f33e",
+ "productInstanceId": "abcdefgh-c1b5-4219-a64b-abcabc123456",
+}
+ `}
+
+
+
++ In case of successful bank verification, with add-on schema configured +
++
@@ -485,7 +556,7 @@ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_ "rpd" : { "success" : false, "id" : "7097e53a-ba29-48a2-983d-878433b4f33e", - "upiBillId" : "907442106379798024", + "upiBillId" : "a6577bb0ae4d9301cf47c1", "data" : null, "error" : { "code" : "BAV_REVERSE_PENNY_DROP_EXPIRED", // or BAV_REVERSE_PENNY_DROP_FAILED @@ -500,121 +571,43 @@ _The value can be `SAVINGS`, `CURRENT`, `NRO`, `NRE`_
-
-
-
-statusCode of this event can be one of the following:
-| statusCode | -statusDescription | -
|---|---|
| R01 | -The customer's debit attempt failed. | -
| R02 | -Payment authorization took too long. | -
| R03 | -The customer's bank is taking too long to respond. | -
| R04 | -The debit process took too long. | -
| R05 | -Connection timed out during the credit request process. | -
| R06 | -The transaction exceeds the risk threshold. | -
| R07 | -The customer's bank is unavailable. | -
| R08 | -This transaction isn't permitted for the beneficiary. | -
| R09 | -Connection timed out during the debit request process. | -
| R12 | -Beneficiary bank response time is too high. | -
| R13 | -The total debit amount exceeded the set limit. | -
| R14 | -Transaction details mismatch. | -
| R16 | -- The requested function is not supported for the beneficiary. - | -
| R20 | -- Receiver/beneficiary is not available, causing a timeout. - | -
| R22 | -The debit acknowledgement was not received. | -
| R25 | -Duplicate transaction request. | -
| R100 | -Any other upstream server error. | -
-
-
- {`
+
+
+
In case of customer's debit attempt failed
--
+
+{`
{
"data": {
"rpd": {
- "id": "178ce32b-bf43-4797-9423-027d3722df08",
- "additionalData": null, // customer's own data if they provided
- "statusCode": "R01",
- "statusDescription": "The customer's debit attempt failed."
+ "success": true,
+ "id": "1af36b4e-681e-48a2-a15c-3b92da00e4c4",
+ "upiBillId": "a6577bb0ae4d9301cf47c1",
+ "data": null,
+ "additionalData": {
+ "key1": value1,
+ "key2": value2
+ },
+ "receiptId": "RPD_REC_12345",
+ "transactionId": "RPD_TXN_67890",
+ "status": "BAV_REVERSE_PENNY_DROP_PII_PURGED"
}
},
- "event": "RPD_DEBIT_ATTEMPT_FAILED",
- "timeStamp": "2023-08-24T12:59:11.427233"
+ "event": "RPD_VERIFICATION_UPDATE",
+ "status": "BAV_REVERSE_PENNY_DROP_PII_PURGED",
+ "traceId": "1-6348f366-55c47bbe132d78441bbe4623",
+ "productInstanceId": "prod_inst_123",
+ "timeStamp": "2023-10-27T10:00:00+05:30"
}
`}
-
-
++ In case of PII purged +
++
@@ -660,8 +653,8 @@ This is an optional API. This API lets you know the bank verification status.
Response
+
+
Request
++
Response
+
+ 
diff --git a/content/data/insights/quickstart/postman.mdx b/content/data/insights/quickstart/postman.mdx
index 23f4a3db..2f78537a 100644
--- a/content/data/insights/quickstart/postman.mdx
+++ b/content/data/insights/quickstart/postman.mdx
@@ -26,7 +26,7 @@ Postman environment comes wth default test credentials, which are passed as head
- Set `clientSecret` to the FIU app client secret received from our support team. This variable is passed as the `x-client-secret` header.
- Set `productInstanceId` to the FIU product instance ID received from our support team. This variable is passed as the `x-product-instance-id` header.
-
+
diff --git a/content/data/insights/v1/quickstart/postman.mdx b/content/data/insights/v1/quickstart/postman.mdx
index 58d1eec0..2b93dc42 100644
--- a/content/data/insights/v1/quickstart/postman.mdx
+++ b/content/data/insights/v1/quickstart/postman.mdx
@@ -26,7 +26,7 @@ Postman environment comes wth default test credentials, which are passed as head
- Set `clientSecret` to the FIU app client secret received from our support team. This variable is passed as the `x-client-secret` header.
- Set `productInstanceId` to the FIU product instance ID received from our support team. This variable is passed as the `x-product-instance-id` header.
-
+
diff --git a/content/data/uli/quickstart.mdx b/content/data/uli/quickstart.mdx
index 3b95cbff..f2f8d31f 100644
--- a/content/data/uli/quickstart.mdx
+++ b/content/data/uli/quickstart.mdx
@@ -25,7 +25,7 @@ The URLs you would need for this API—
+
-
+
diff --git a/content/dev-tools/bridge/explore-and-configure-products.mdx b/content/dev-tools/bridge/explore-and-configure-products.mdx index 94b0e41d..e878eda9 100644 --- a/content/dev-tools/bridge/explore-and-configure-products.mdx +++ b/content/dev-tools/bridge/explore-and-configure-products.mdx @@ -9,7 +9,7 @@ visible_in_sidebar: true Use **Home or Product store** to see all the products that you can configure with Setu. Select any one, and start setting up your product integration. -
+
##### 1. Create a child sub-org account
The first step is to set up a child sub-org account, which contains context about a product category and the organisation that can legally use this product. There are different types of legal entities allowed to use different product categories. For example, you will set up an FIU to use Account Aggregator, or set up a merchant to use UPI products.
@@ -23,7 +23,7 @@ While this is rarely needed, you can also create multiple child sub-org accounts
+
##### 2. Set up product instance
Depending on the product you choose, you need to fill in different details to start using the product. At times, our products also allow you to directly use the APIs for our products, by generating test credentials and using the “Product ID” in the `product-instance-id` header field.
@@ -36,12 +36,12 @@ Usually, the details you need to fill out for a product instance include the fol
- **KYC details** — Mandatory details as per government regulations, needed and reviewed by Setu only if you intend to go live with a product. These might include PAN, GST, certificates, and other relevant information.
-
+
##### 3. Submit all the details
Finally, check and verify all the details you have provided, and submit them. A Setu admin will verify all details and if everything looks good, approve your config. This typically takes 2-5 days and you can start transacting on production after approval.
-
+
+
1. Your organisation, either reused from sign-up or a relevant subsidiary, for which KYC will be done.
2. The product category you want to use.
Here are a few examples:
• **Account Aggregator FIUs (Financial Information Users):** In the AA ecosystem, entities using financial information, such as personal finance apps or loan providers.
• **UPI merchants:** In the UPI ecosystem, entities collecting payments through UPI.
• **BBPS BOU billers:** Entities collecting repeat payments for their services via BBPS-enabled apps.
• **BBPS COU agents:**Entities offering BBPS-enabled platforms to collect bill payments for BBPS billers. | -| **Aggregator account (coming soon)** | This is a type of parent Bridge account, that is allowed to resell Setu products to its business customers. The Bridge allows additional features for an aggregator—like viewing combined reports and analytics for all their business customers, or managing their corresponding Parent Bridge accounts with a single login.
If you want to become an aggregator, please contact onboarding@setu.co for more details.| +| **Aggregator account (coming soon)** | This is a type of parent Bridge account, that is allowed to resell Setu products to its business customers. The Bridge allows additional features for an aggregator—like viewing combined reports and analytics for all their business customers, or managing their corresponding Parent Bridge accounts with a single login.
If you want to become an aggregator, please contact [onboarding@setu.co](mailto:onboarding@setu.co) for more details.| -
+
diff --git a/content/dev-tools/bridge/overview.mdx b/content/dev-tools/bridge/overview.mdx index fec22167..4dce2648 100644 --- a/content/dev-tools/bridge/overview.mdx +++ b/content/dev-tools/bridge/overview.mdx @@ -9,7 +9,7 @@ visible_in_sidebar: true Bridge is a free self-serve platform provided by Setu, where you can explore and use multiple products provided by Setu—fill in details to go live with products, manage user access to those products, and also check reports and analytics related to your configured products, on a single platform. -
+
**Explore the platform and get started with Setu Bridge **
@@ -24,7 +24,7 @@ You can sign up on the Bridge in a few simple steps:
5. Provide your business name. This should belong to the business you’re setting up the Bridge account for. **Quick note:** You can use a different business name later when you configure the product (say, if you have a subsidiary or a different legal name).
6. Optionally, set up 2FA (two-factor authentication) for account login. Enable or disable 2FA, which asks for a password and an OTP sent to your registered e-mail ID whenever you login.
-
+
### Log in to Bridge
@@ -33,16 +33,16 @@ You can log in to the Bridge in a few simple steps:
2. Enter your password.
3. Enter OTP. **Note**, you need to provide an OTP only if you have enabled 2FA.
-
+
### Navigating Bridge
-
+
##### Side navigation items
Explore the different sections on the Bridge sidebar.
-
+
- The **Home page** is a central view for all products. This is where you can see details of your child accounts, pending integrations, and data on live integrations.
@@ -60,7 +60,7 @@ Explore the different sections on the Bridge sidebar.
##### Your Profile
-
+
+
@@ -42,7 +42,7 @@ Check for users who can access the account, the roles assigned to each user, the
+
@@ -71,7 +71,7 @@ Check for users who can access the account, the roles assigned to each user, the
+
@@ -89,7 +89,7 @@ Check for users who can access the account, the roles assigned to each user, the
+
@@ -113,21 +113,21 @@ Live credentials work only for product instance IDs with “Live config Also, don’t worry about “accidentally” using live credentials for an instance ID that is not yet live—you simply cannot use live credentials for the instance ID, before it acquires the “Live config” status. -
+
##### Settings > Account preferences Set two-factor-authentication for better security, so that every user who logs into your parent account has to additionally provide an OTP sent to their email, along with their password for Bridge. -
+
##### Settings > Your profile Your user profile contains account details—like e-mail, phone number—and access details to one or more Bridge accounts. -
+
@@ -139,7 +139,7 @@ You can check all the details attached to your personal profile. 3. **Security preferences:** Enable or disable two-factor authentication (2FA) and change your password. -
+
@@ -154,7 +154,7 @@ To switch between organisations you are part of, follow these steps: 3. **Select or search for another organisation:** Click on the organisation you want to switch to. In case you have access to more than 3 accounts, a search bar will be visible and you can search by typing in the name (at least 3 characters) or ID of the Bridge account. You can click the organisation and that account’s details will appear in Bridge. -
+
@@ -21,7 +21,7 @@ You can check all the details attached to your personal profile. 2. **Organisation listing:** View the list of organisations where you are invited. 3. **Security preferences:** Enable or disable two-factor authentication (2FA) and change your password. -
+
@@ -35,6 +35,6 @@ To switch between organisations you are part of, follow these steps: 2. **Check the list of organisations:** The currently active organisation is marked with a green tick. You can view the list of all other organisations. 3. **Select or search for another organisation:** Click on the organisation you want to switch to. In case you have access to more than 3 accounts, a search bar will be visible and you can search by typing in the name (at least 3 characters) or ID of the Bridge account. You can click the organisation and that account’s details will appear in Bridge. -
+
fetch bill ↗ for the customer, and then, shares it with BBPS.
fetchBillReceipt ↗
diff --git a/content/payments/billpay/api-integration/paying_bills.mdx b/content/payments/billpay/api-integration/paying-bills/quickstart.mdx similarity index 92% rename from content/payments/billpay/api-integration/paying_bills.mdx rename to content/payments/billpay/api-integration/paying-bills/quickstart.mdx index 51881343..9276db9a 100644 --- a/content/payments/billpay/api-integration/paying_bills.mdx +++ b/content/payments/billpay/api-integration/paying-bills/quickstart.mdx @@ -1,13 +1,13 @@ --- -sidebar_title: Paying Bills +sidebar_title: Quickstart page_title: BBPS Bill Payment Integration Guide -order: 4 +order: 1 visible_in_sidebar: true --- # Paying Bills -**Scope**: This guide covers using Setu APIs to pay bills through the BBPS (Bharat Bill Payment System) network. For prepaid mobile recharge, refer to the separate prepaid recharge API documentation. +**Scope**: This guide covers using Setu APIs to pay bills through the BBPS (Bharat Bill Payment System) network. For prepaid mobile recharge, refer to the separate prepaid recharge API documentation.
+
+
+
+ {`{
+ "event": "BILL_PAY",
+ "data": {
+ "refId": "D4FBHNBFTPVUIF7U2L30zNfa44153241214",
+ "status": "Credit_Adjustment",
+ "billerRefId": "AB123456",
+ "transactionId": "AS015324121535B9bN8t",
+ "paymentDetails": {
+ "mode": "Internet Banking/Debit Card/Credit Card/Cash/UPI/Wallet/Prepaid Card/AEPS/Account Transfer/Bharat QR/USSD",
+ "paymentRefId": "VBPO2511779235981744230279",
+ "amount": 87150,
+ "timestamp": "2025-11-20T12:15:36.000+05:30"
+ },
+ "billerId": "INDI00000NATT5"
+ }
+}`}
+
+
+
+
+ Bill payment sample request (Credit Adjustment)
+
+
+ ### Dispute webhook @@ -211,7 +239,7 @@ URL : To be provided by partner`} "data": { "refId": "JPMRPBOGGDTP1EFRZVXVESQVQIS10461642", "disputeId": "OP0121046567755", - "status": "ASSIGNED/RESOLVED/REJECTED/DEFAULT_RESOLVED/REFUNDED/PENDING_REFUND", + "status": "ASSIGNED/RESOLVED/REJECTED/DEFAULT_RESOLVED/REFUNDED/PENDING_REFUND/FAILED", "assignedTo": "AX39", "remarks": "Resolved in favour of customer" } @@ -755,4 +783,4 @@ URL : To be provided by partner (Skip Payment Callback URL)`} -
-
+
- Browse over to Settings under the Profile section. +
- Under Apps and Connectors, scroll down to Advance Settings and expand. +
- On expanding it, you will see an option to enable Developer Mode. +
- Once enabled, you will observe an orange highlight on your chat inputs. +
-
+
- Once the Developer mode is enabled, go to Apps and Connectors. +
- Click on Create at the top right. +
- Add a name for the Setu MCP — say, Setu Bill Payments MCP. +
- In the URL field, add https://billpay-mcp.setu.co/mcp. +
- Under Authentication, select OAuth; check the consent box, and confirm. +
-
+
- On confirming, you will be taken to a page to enter your phone number and OTP. All bill payments require a phone number to fetch bills. +
-
+
- You can also instruct GPT to only use the Setu Bill Payments MCP on the chat window, by clicking on the plus icon and adding the MCP to your chat. +
- It is not mandatory to do so, but could help in some scenarios. +
-
+
- Follow the steps on Download Claude to download the relevant desktop version for your system. +
- Install the application by clicking continue and complete the installation successfully. +
-
+
- Open Claude Desktop, and under Profile, go to Settings, and click on Connectors. +
- Click on “Custom Connector”. +
- Enter the MCP name - Setu Bill Payments MCP, and the MCP URL https://billpay-mcp.setu.co/mcp. +
-
+
- You can also instruct Claude to only use the Setu Bill Payments MCP on the chat window, by clicking on the plus icon and adding the MCP to your chat. +
- It is not mandatory to do so, but could help in some scenarios. +
+ +
+ +### Pre-requisites +You need to do the following to configure a Setu provided webhook— + +- Share the webhook URL. A URL that can accept `JSON` data over `POST`. +- Take steps to handle the notification + +### Configuration + +To configure webhooks, share your webhook URL with Setu via email to support@setu.co. + +
+ + +## Webhook Endpoints + +The system appends specific routes to your base `webhook_url` based on the event type: + +### 1. Payment Status Webhook + +**Endpoint**: `{webhook_url}/payment/status` + +**Description**: Sent when a recharge transaction status is updated (successful, failed, or processing). + +**Request Body**: + +
+
+
+
+ {`{
+ "transactionRefId": "TXN123456789",
+ "trace_id": "SYS-ABC-123",
+ "operatorRefId": "OP-987654321",
+ "status": "Successful",
+ "amount": "99.00",
+ "mobile_number": "9876543210",
+ "provider": "Airtel",
+ "timestamp": "2025-11-13T10:30:00Z"
+}`}
+
+
+
+
+ Payment status webhook example (Success)
+
+
+
+
+
+
+ {`{
+ "transactionRefId": "TXN123456790",
+ "trace_id": "SYS-ABC-124",
+ "status": "Failure",
+ "amount": "99.00",
+ "mobile_number": "9876543210",
+ "provider": "Airtel",
+ "failureReason": "Insufficient balance",
+ "timestamp": "2025-11-13T10:31:00Z"
+}`}
+
+
+
+
+ Payment status webhook example (Failure)
+
+
+ + +### 2. Payment Reversal Webhook + +**Endpoint**: `{webhook_url}/payment/reversal` + +**Description**: Sent when a recharge transaction is reversed by the operator. + +**Request Body**: + +
+
+
+
+ {`{
+ "transactionRefId": "TXN123456789",
+ "trace_id": "SYS-ABC-123",
+ "operatorRefId": "OP-987654321",
+ "status": "REVERSED",
+ "amount": "99.00",
+ "mobile_number": "9876543210",
+ "provider": "Airtel",
+ "failureReason": "Transaction reversed by operator",
+ "timestamp": "2025-11-13T10:35:00Z"
+}`}
+
+
+
+
+ Payment reversal webhook example
+
+
+ + +### 3. Wallet Low Balance Webhook + +**Endpoint**: `{webhook_url}/wallet/low_balance` + +**Description**: Sent when the wallet balance falls below the configured threshold or when a low balance alert is received from the vendor. + +**Request Body**: + +
+
+
+
+ {`{
+ "event": "wallet.low_balance",
+ "balance": "2450.00",
+ "message": "Low balance Alert",
+ "timestamp": "2025-11-13T09:15:00Z",
+ "traceId": "low-balance-webhook-demo-instance-a1b2c3d4"
+}`}
+
+
+
+
+ Wallet low balance webhook example
+
+
+ + +### 4. Wallet Topup Webhook + +**Endpoint**: `{webhook_url}/wallet/top_up` + +**Description**: Sent when a wallet top-up is detected or when a top-up notification is received from the vendor. + +**Request Body**: + +
+
+
+
+ {`{
+ "event": "wallet.credit",
+ "amount": "5000.00",
+ "referenceNumber": "TXN-9090",
+ "creditedFrom": "Bank Transfer",
+ "transactionDate": "2025-11-13T09:45:00Z",
+ "message": "Wallet topped up successfully",
+ "traceId": "topup-webhook-demo-instance-e5f6g7h8",
+ "currentBalance": "12450.00"
+}`}
+
+
+
+
+ Wallet topup webhook example
+
+
+ + +## Webhook Response + +Your webhook endpoint should respond with: + +- **HTTP Status Code**: `200-299` for successful receipt +- **Response Body**: Any valid JSON (will be logged but not processed) + +**Example Response**: + +
+ +### Retry Mechanism + +The system implements automatic retry mechanisms for webhook delivery with different policies based on webhook type: + +#### Payment Webhooks (Transaction Status & Reversal) + +- **Maximum Retries**: 5 attempts +- **Initial Retry Interval**: 2 seconds +- **Maximum Retry Interval**: 2 minutes +- **Backoff Strategy**: Exponential backoff with coefficient of 2.0 +- **Retry Triggers**: + - Non-2xx HTTP status codes + - Network timeouts + - Connection errors + +#### Wallet Webhooks (Low Balance & Topup) + +- **Maximum Retries**: 3 attempts +- **Initial Retry Interval**: 5 seconds +- **Maximum Retry Interval**: 1 minute +- **Backoff Strategy**: Exponential backoff with coefficient of 2.0 +- **Retry Triggers**: + - Non-2xx HTTP status codes + - Network timeouts + - Connection errors + +**Retry Timeline Example (Payment Webhooks)**: + +- Attempt 1: Immediate +- Attempt 2: After 2 seconds +- Attempt 3: After 4 seconds (2 Ă— 2) +- Attempt 4: After 8 seconds (4 Ă— 2) +- Attempt 5: After 16 seconds (8 Ă— 2) +- Attempt 6: After 32 seconds (16 Ă— 2, capped at 2 minutes max) + +After all retries are exhausted, the webhook status is marked as "FAILED" in the system. + +
/COU_WL_custom_payment_web_(1).gif)
diff --git a/content/payments/billpay/pre-built-screens/webhooks.mdx b/content/payments/billpay/pre-built-screens/webhooks.mdx
index 3418eb9c..ae7ca0c9 100644
--- a/content/payments/billpay/pre-built-screens/webhooks.mdx
+++ b/content/payments/billpay/pre-built-screens/webhooks.mdx
@@ -285,12 +285,11 @@ Below are the parameter tables and sample payloads for the listed events. Note t
{`{
"mobileNumber": "9481773053",
"status": "FETCH_FAILURE",
- "billId": "",
"billerId": "MAHI00000NATIC",
"billerName": "Mahindra Rural Housing Finance Ltd",
"billerCategory": "Loan-Repayment",
"sessionId": "1272707270496486911",
- "customerId": "cust@1234" // if available
+ "customerId": "cust@1234", // if available
"event": "bill_fetch_failure",
"refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831",
"fetchErrorCode": "ERR001",
@@ -323,18 +322,6 @@ Below are the parameter tables and sample payloads for the listed events. Note t
FETCH_FAILURE
- 69a1fbc0-b5d1-4cbf-ac6d-c4244e3e7e0c
- | billAmount | -String (Number) | -Amount of the bill in rupees (INR) | -
- 101.55
- |
-
| dueDate | -String (Date) | -Due date of the bill. Format is YYYY-MM-DD. | -
- 2023-05-02
- |
-
| amountPaid | String (Number) | @@ -817,6 +791,12 @@ Below are the parameter tables and sample payloads for the listed events. Note t||
| error | +Object | +Error details for failure of bill payment | +[{"code": "insufficient-balance", "message": "66578Insufficient balance in the bank account. Please ensure sufficient funds are available before retrying.01290", "type": "FUND_TRANSFER"] |
+
null
- COLLECTION_FAILURE
dfeeaf14-e43a-4196-90d0-41089e979ad5
- Loan-Repayment
101.55
- 2023-05-02
- cust@1234
601.75
null
- PAYMENT_REFUNDED
dfeeaf14-e43a-4196-90d0-41089e979ad5
- cust@1234
601.75
- 2023-05-02
- 
+ 
diff --git a/content/payments/billpay/v1/pre-built-screens/webhooks.mdx b/content/payments/billpay/v1/pre-built-screens/webhooks.mdx
index 3fe83353..a0ce5cc8 100644
--- a/content/payments/billpay/v1/pre-built-screens/webhooks.mdx
+++ b/content/payments/billpay/v1/pre-built-screens/webhooks.mdx
@@ -255,12 +255,11 @@ Below are the parameter tables and sample payloads for the listed events. Note t
{`{
"mobileNumber": "9481773053",
"status": "FETCH_FAILURE",
- "billId": "",
"billerId": "MAHI00000NATIC",
"billerName": "Mahindra Rural Housing Finance Ltd",
"billerCategory": "Loan-Repayment",
"sessionId": "1272707270496486911",
- "customerId": "cust@1234" // if available
+ "customerId": "cust@1234", // if available
"event": "bill_fetch_failure",
"refId": "CMA0I65RCU2I32C3L0H0KNYQYAG40021831",
"fetchErrorCode": "ERR001",
@@ -293,17 +292,6 @@ Below are the parameter tables and sample payloads for the listed events. Note t
FETCH_FAILURE
69a1fbc0-b5d1-4cbf-ac6d-c4244e3e7e0c
- Q00ABCDEFGHZOQ
101.55
- 2023-05-02
- null
- COLLECTION_FAILURE
dfeeaf14-e43a-4196-90d0-41089e979ad5
- Loan-Repayment
101.55
- 2023-05-02
- cust@1234
601.75
null
- PAYMENT_REFUNDED
dfeeaf14-e43a-4196-90d0-41089e979ad5
- cust@1234
601.75
- 2023-05-02
- 
diff --git a/content/payments/umap/mandates/generic/pause.mdx b/content/payments/umap/mandates/generic/pause.mdx
index d8bc15f3..fe4984fc 100644
--- a/content/payments/umap/mandates/generic/pause.mdx
+++ b/content/payments/umap/mandates/generic/pause.mdx
@@ -45,7 +45,7 @@ Read more about
The notifications are depicted in the below diagram—
diff --git a/content/payments/umap/mandates/generic/revoke.mdx b/content/payments/umap/mandates/generic/revoke.mdx
index ba5cbe40..8f9dec14 100644
--- a/content/payments/umap/mandates/generic/revoke.mdx
+++ b/content/payments/umap/mandates/generic/revoke.mdx
@@ -31,7 +31,7 @@ The process for revoking a mandate initiated from the
customer's UPI app is described in the below diagram
@@ -88,7 +88,7 @@ The process for revoking a mandate by the merchant is
described in the below diagram
The merchant or aggregator will have to call the
diff --git a/content/payments/umap/mandates/generic/unpause.mdx b/content/payments/umap/mandates/generic/unpause.mdx
index 335e0ef2..bd5bb4b7 100644
--- a/content/payments/umap/mandates/generic/unpause.mdx
+++ b/content/payments/umap/mandates/generic/unpause.mdx
@@ -47,7 +47,7 @@ Only the end customer has the option of unpausing a paused UPI mandate from thei
The notifications are depicted in the below diagram
diff --git a/content/payments/umap/mandates/generic/update.mdx b/content/payments/umap/mandates/generic/update.mdx
index d619d2de..cb0703c4 100644
--- a/content/payments/umap/mandates/generic/update.mdx
+++ b/content/payments/umap/mandates/generic/update.mdx
@@ -36,7 +36,7 @@ There are only two updates possible on a UPI mandate
The process for updating an intent based mandate is described in the
below diagram
The merchant will have to call the{" "}
@@ -174,7 +174,7 @@ There are only two updates possible on a UPI mandate
The process for updating a collect based mandate is described in the
below diagram
The merchant will have to call the{" "}
diff --git a/content/payments/umap/mandates/one-shot/create.mdx b/content/payments/umap/mandates/one-shot/create.mdx
index 4405eee4..ffcc57aa 100644
--- a/content/payments/umap/mandates/one-shot/create.mdx
+++ b/content/payments/umap/mandates/one-shot/create.mdx
@@ -20,7 +20,7 @@ There are two ways to create a one time mandate—**Intent based** and **Collect
The process for mandate creation is described in the below diagram:
@@ -254,7 +254,7 @@ There are two ways to create a one time mandate—**Intent based** and **Collect The process for mandate creation is described in the below diagram:
diff --git a/content/payments/umap/mandates/one-shot/pre-debit-notify.mdx b/content/payments/umap/mandates/one-shot/pre-debit-notify.mdx
index dac33682..b7bb503b 100644
--- a/content/payments/umap/mandates/one-shot/pre-debit-notify.mdx
+++ b/content/payments/umap/mandates/one-shot/pre-debit-notify.mdx
@@ -28,7 +28,7 @@ Once the mandate is **LIVE** the merchant needs to send a pre debit notification
The process for mandate pre debit notification is described in the below diagram:
diff --git a/content/payments/umap/mandates/recur/create.mdx b/content/payments/umap/mandates/recur/create.mdx
index 34633c95..0c920723 100644
--- a/content/payments/umap/mandates/recur/create.mdx
+++ b/content/payments/umap/mandates/recur/create.mdx
@@ -20,7 +20,7 @@ There are 2 ways to create a recurring mandate: **Intent based**, **Collect base
The process for mandate creation is described in the below diagram:
@@ -228,7 +228,7 @@ There are 2 ways to create a recurring mandate: **Intent based**, **Collect base
@@ -578,7 +578,7 @@ There are 2 ways to create a recurring mandate: **Intent based**, **Collect base
diff --git a/content/payments/umap/mandates/reserve-plus/create.mdx b/content/payments/umap/mandates/reserve-plus/create.mdx
index c446a1f8..f0c06464 100644
--- a/content/payments/umap/mandates/reserve-plus/create.mdx
+++ b/content/payments/umap/mandates/reserve-plus/create.mdx
@@ -243,7 +243,7 @@ visible_in_sidebar: true
The process for mandate creation is described in the below diagram
diff --git a/content/payments/umap/mandates/reserve.mdx b/content/payments/umap/mandates/reserve.mdx
index b61de5c1..1365c9a8 100644
--- a/content/payments/umap/mandates/reserve.mdx
+++ b/content/payments/umap/mandates/reserve.mdx
@@ -29,7 +29,7 @@ MCC 6211 - Capital Markets & Securities Brokers merchants can block upto â‚ą5 la
diff --git a/content/payments/umap/mandates/reserve/create.mdx b/content/payments/umap/mandates/reserve/create.mdx
index f47a7cbd..c3b42e98 100644
--- a/content/payments/umap/mandates/reserve/create.mdx
+++ b/content/payments/umap/mandates/reserve/create.mdx
@@ -20,7 +20,7 @@ There are two ways to create a Reserve mandate—**Intent based** and **Collect
The process for mandate creation is described in the below diagram:
@@ -254,7 +254,7 @@ There are two ways to create a Reserve mandate—**Intent based** and **Collect The process for mandate creation is described in the below diagram:
diff --git a/content/payments/umap/notifications/mandates.mdx b/content/payments/umap/notifications/mandates.mdx
index ac904370..805f6e6c 100644
--- a/content/payments/umap/notifications/mandates.mdx
+++ b/content/payments/umap/notifications/mandates.mdx
@@ -23,7 +23,7 @@ Below is a list mandate statuses that are uniform across all types of mandates.
Here is the expected life-cycle of a mandate—
diff --git a/content/payments/umap/notifications/mandates/create.mdx b/content/payments/umap/notifications/mandates/create.mdx
index 5e58c35d..b3194df4 100644
--- a/content/payments/umap/notifications/mandates/create.mdx
+++ b/content/payments/umap/notifications/mandates/create.mdx
@@ -10,7 +10,7 @@ visible_in_sidebar: true
The first step to start utilising mandates is to create a mandate. Here is a quick view of how the status moves from `mandate.initiated` to `mandate.live` or `mandate.rejected`—
diff --git a/content/payments/umap/notifications/mandates/pause.mdx b/content/payments/umap/notifications/mandates/pause.mdx
index c6592eb4..f90830ae 100644
--- a/content/payments/umap/notifications/mandates/pause.mdx
+++ b/content/payments/umap/notifications/mandates/pause.mdx
@@ -19,7 +19,7 @@ visible_in_sidebar: true
These are the available webhooks for merchants, when their customers attempt to pause their mandate (which can be a temporary action). Here is a quick view of how the status moves from `mandate.live` to `mandate.paused`—
diff --git a/content/payments/umap/notifications/mandates/revoke.mdx b/content/payments/umap/notifications/mandates/revoke.mdx
index b5993620..14084c75 100644
--- a/content/payments/umap/notifications/mandates/revoke.mdx
+++ b/content/payments/umap/notifications/mandates/revoke.mdx
@@ -19,7 +19,7 @@ visible_in_sidebar: true
These are the available webhooks for merchants, when revoking of mandate is done by either the customer or in rarer cases, the merchant. Here is a quick view of how the status moves from `mandate.live` to `mandate.revoked`—
diff --git a/content/payments/umap/notifications/mandates/unpause.mdx b/content/payments/umap/notifications/mandates/unpause.mdx
index 5080211f..9a3160fc 100644
--- a/content/payments/umap/notifications/mandates/unpause.mdx
+++ b/content/payments/umap/notifications/mandates/unpause.mdx
@@ -19,7 +19,7 @@ visible_in_sidebar: true
These are the available webhooks for merchants, when their customer unpauses their mandate. Here is a quick view of how the status moves from `mandate.paused` to `mandate.unpaused`—
diff --git a/content/payments/umap/notifications/mandates/update.mdx b/content/payments/umap/notifications/mandates/update.mdx
index ee7209b1..06615293 100644
--- a/content/payments/umap/notifications/mandates/update.mdx
+++ b/content/payments/umap/notifications/mandates/update.mdx
@@ -19,7 +19,7 @@ visible_in_sidebar: true
Here is a quick view of how the status moves from `mandate.live` to `mandate.updated`—
diff --git a/content/payments/umap/notifications/payments.mdx b/content/payments/umap/notifications/payments.mdx
index 31eaf6f6..812a36f6 100644
--- a/content/payments/umap/notifications/payments.mdx
+++ b/content/payments/umap/notifications/payments.mdx
@@ -12,7 +12,7 @@ Most of the products on our platform end up creating a payment event when a cust
Any UPI Setu product relies on creating and presenting payment request to a customer. Setu's UPI Setu stack provides consistent and transparent payment statuses for a merchant, to be able to track the life-cycle of a payment request. These statuses are shown in the diagram below.
diff --git a/content/payments/umap/notifications/refunds.mdx b/content/payments/umap/notifications/refunds.mdx
index d8674489..a32ca95b 100644
--- a/content/payments/umap/notifications/refunds.mdx
+++ b/content/payments/umap/notifications/refunds.mdx
@@ -36,7 +36,7 @@ The statuses are consistent across all UPI Setu products—
Here is the life-cycle for refund statuses—
diff --git a/content/payments/umap/overview.mdx b/content/payments/umap/overview.mdx
index c1f378fe..2ef733ec 100644
--- a/content/payments/umap/overview.mdx
+++ b/content/payments/umap/overview.mdx
@@ -16,7 +16,7 @@ UPI Setu connects directly with NPCI, absorbing both acquirer and beneficiary ba
_
diff --git a/content/payments/umap/payments.mdx b/content/payments/umap/payments.mdx
index d90d6ea9..1f0931f5 100644
--- a/content/payments/umap/payments.mdx
+++ b/content/payments/umap/payments.mdx
@@ -34,7 +34,7 @@ UPI Setu relies on a few features that persist across various products offered u
UPI Setu has consistent and transparent payment statuses across all transaction flows.
diff --git a/content/payments/umap/payments/collect.mdx b/content/payments/umap/payments/collect.mdx
index b3327892..09f790bb 100644
--- a/content/payments/umap/payments/collect.mdx
+++ b/content/payments/umap/payments/collect.mdx
@@ -62,7 +62,7 @@ After the customer responds to the collect request, transaction details can be f
## Collect flow interactions
diff --git a/content/payments/umap/payments/flash.mdx b/content/payments/umap/payments/flash.mdx
index 6d615b51..5f0daefb 100644
--- a/content/payments/umap/payments/flash.mdx
+++ b/content/payments/umap/payments/flash.mdx
@@ -62,7 +62,7 @@ Following the initiation of the transaction, the system retrieves the payment de
## Payment flow interactions
diff --git a/content/payments/umap/payments/tpv.mdx b/content/payments/umap/payments/tpv.mdx
index c2803889..3363bcff 100644
--- a/content/payments/umap/payments/tpv.mdx
+++ b/content/payments/umap/payments/tpv.mdx
@@ -47,7 +47,7 @@ Based on the outcome of the validation check, the UPI Setu system decides whethe
### TPV Process Flow
diff --git a/content/payments/umap/refunds-disputes.mdx b/content/payments/umap/refunds-disputes.mdx
index 7c65d296..3cc300d4 100644
--- a/content/payments/umap/refunds-disputes.mdx
+++ b/content/payments/umap/refunds-disputes.mdx
@@ -23,7 +23,7 @@ UPI Setu empowers merchants with direct API access to issue refunds and contest
### Refund process overview
@@ -55,7 +55,7 @@ In addition to notifications, merchants can also use the
diff --git a/content/redirects.json b/content/redirects.json
index 09d180de..6d1f2318 100644
--- a/content/redirects.json
+++ b/content/redirects.json
@@ -21,6 +21,8 @@
"/payments/billpay-apis": "/payments/billpay-apis/overview",
"/payments/billpay/api-integration": "/payments/billpay/api-integration/quickstart",
"/payments/billpay/v1/api-integration": "/payments/billpay/v1/api-integration/quickstart",
+ "/payments/billpay/api-integration/paying-bills": "/payments/billpay/api-integration/paying-bills/quickstart",
+ "/payments/billpay/v1/api-integration/paying-bills": "/payments/billpay/v1/api-integration/paying-bills/quickstart",
"/payments/billpay/quickstart": "/payments/billpay/overview",
"/payments/billpay/pre-built-screens": "/payments/billpay/pre-built-screens/quickstart",
"/payments/billpay/mobile-prepaid-recharge": "/payments/billpay/mobile-prepaid-recharge/quickstart",
@@ -72,6 +74,7 @@
"/data/bav/api-integration": "/data/bav/penny-drop/api-integration",
"/data/bav/api-integration/sync": "/data/bav/penny-drop/api-integration/sync",
"/data/bav/api-integration/async": "/data/bav/penny-drop/api-integration/async",
+ "/data/bav/bundled-bav": "/data/bav/bundled-bav/quickstart",
"/data/pan": "/data/pan/quickstart",
"/data/esign": "/data/esign/overview",
"/data/digilocker": "/data/digilocker/overview",
@@ -124,5 +127,6 @@
"/biller-quickstart": "/payments/bbps/quickstart",
"/sample-category/sample-product": "/sample-category/sample-product/sample-page",
"/docs-components": "/sample-category/sample-product/sample-page",
- "/setu-bot": "/"
+ "/setu-bot": "/",
+ "/payments/billpay/mcp": "/payments/billpay/mcp/integration-guide"
}
diff --git a/content/sample-category/sample-product/sample-page.mdx b/content/sample-category/sample-product/sample-page.mdx
index f1676bf1..5b2d4cf8 100644
--- a/content/sample-category/sample-product/sample-page.mdx
+++ b/content/sample-category/sample-product/sample-page.mdx
@@ -10,14 +10,14 @@ visible_in_sidebar: false
#### Full width image
