style/content tweaks

content/payments/billpay/api-integration/bill-payment-options.mdx

@@ -1,6 +1,6 @@
 ---
-sidebar_title: Bill Payment Options
-page_title: Bill Payment Options Integration Guide
+sidebar_title: Paying for alternative options
+page_title: Paying for alternative options
 order: 7
 visible_in_sidebar: true
 ---
@@ -165,7 +165,7 @@ All date comparisons are in IST.
 
 📖 **Related Guides:**
 - <a href="/payments/billpay/api-integration/paying_bills" target="_blank">Paying Bills Integration Guide</a> — Master guide with Flow 1 implementation
-- <a href="/payments/billpay/api-integration/multi-bill-processing" target="_blank">Multi-Bill Processing Guide</a> — Multiple bills handling (optional)
+- <a href="/payments/billpay/api-integration/multi-bill-processing" target="_blank">Paying for multiple bills</a> — Multiple bills handling 
 - <a href="/payments/billpay/api-integration/api-reference" target="_blank">API Reference</a> — Complete endpoint specifications
 - <a href="/payments/billpay/api-integration/webhooks" target="_blank">Webhooks Integration</a> — Real-time payment status updates
 

content/payments/billpay/api-integration/multi-bill-processing.mdx

@@ -54,17 +54,17 @@ if (fetchResponse.data.billerResponseType === "LIST") {
 ## Common Multi-Bill Scenarios
 
 **When billers return multiple outstanding bills:**
-- **Corporate credit cards**: Multiple billing periods (May + June statements)
+- **Corporate credit cards**: Multiple outstanding bills
 - **B2B invoices**: Multiple outstanding invoices requiring payment
 - **Government eChallans**: Bulk payment processing
 
 ## Selection Rules
 
 **The `billerSelectionType` field determines how many bills users can select:**
 
-- **`"SINGLE"`** → Choose exactly 1 bill (e.g., May OR June credit card statement)
+- **`"SINGLE"`** → Choose exactly 1 bill (e.g., one credit card bill)
 - **`"MULTIPLE"`** → Choose 1+ bills (e.g., select which invoices to pay)
-- **`"ALL"`** → Must pay all bills together (no selection)
+- **`"ALL"`** → Must pay all bills together (pay all bills at once)
 
 ## Implementation Guide
 
@@ -120,13 +120,6 @@ function renderBillSelection(fetchResponse) {
 2. **Amount consistency**: `paymentDetails.amount` must equal sum of selected bill amounts  
 3. **Bill matching**: All selected `billNumber` values must exist in fetch response
 
-**Multi-Bill + Payment Options:**
-Individual bills in LIST responses can also have `paymentOptions`. Handle bill selection first, then payment options for selected bills.
-
-📖 **Payment options implementation → <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Bill Payment Options Guide</a>**
-
-**Transaction responses include individual bill breakdown for detailed reconciliation and audit trails.**
-
 ## Implementation Checklist
 
 1. **Add detection logic** to your existing Flow 1 fetch handler
@@ -138,7 +131,7 @@ Individual bills in LIST responses can also have `paymentOptions`. Handle bill s
 
 📖 **Related Guides:**
 - <a href="/payments/billpay/api-integration/paying_bills" target="_blank">Paying Bills Integration Guide</a> — Master guide with Flow 1 implementation
-- <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Bill Payment Options Guide</a> — Handle payment options within bills
+- <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Paying for alternative options</a> — Handle payment options within bills
 - <a href="/payments/billpay/api-integration/api-reference" target="_blank">API Reference</a> — Complete endpoint specifications
 - <a href="/payments/billpay/api-integration/webhooks" target="_blank">Webhooks Integration</a> — Real-time payment status updates
 

content/payments/billpay/api-integration/paying_bills.mdx

@@ -273,7 +273,7 @@ Call `/api/v{1|2}/bbps/bills/payment/request` with:
 }
 `}</CodeBlockWithCopy>
 
-📖 **Complete payment options implementation → <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Bill Payment Options Guide</a>**
+📖 **Complete payment options implementation → <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Paying for alternative options</a>**
 
 ### Paying for multiple bills (Optional)
 
@@ -495,9 +495,9 @@ After initiating a payment across any flow, you'll receive responses that requir
 
 📖 **Essential References:**
 - <a href="/payments/billpay/api-integration/api-reference" target="_blank">Complete API Documentation</a> — Full endpoint specifications
-- <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Bill Payment Options Guide</a> — Handle multiple payment amounts (essential)
+- <a href="/payments/billpay/api-integration/bill-payment-options" target="_blank">Paying for alternative options</a> — Handle multiple payment amounts 
 - <a href="/payments/billpay/api-integration/plan-mdm-integration" target="_blank">Plan MDM Integration</a> — Plan-based biller patterns
-- <a href="/payments/billpay/api-integration/multi-bill-processing" target="_blank">Multi-Bill Processing Guide</a> — Multiple bills handling (optional)
+- <a href="/payments/billpay/api-integration/multi-bill-processing" target="_blank">Multi-Bill Processing Guide</a> — Multiple bills handling 
 - <a href="/payments/billpay/api-integration/remittance_flows_guide" target="_blank">Remitter Details Guide</a> — Payment format specifications  
 - <a href="/payments/billpay/api-integration/webhooks" target="_blank">Webhooks Integration</a> — Real-time status updates
 

content/payments/billpay/api-integration/remittance_flows_guide.mdx

@@ -1,6 +1,6 @@
 ---
-sidebar_title: Remitter Details
-page_title: Remitter Details
+sidebar_title: Passing Remitter Details
+page_title: Passing Remitter Details
 order: 6
 visible_in_sidebar: true
 ---
@@ -14,8 +14,6 @@ This guide is a concise format reference for remitter details and NPCI-compatibl
 
 📖 **For complete payment integration context and examples → <a href="/payments/billpay/api-integration/paying_bills" target="_blank">Paying Bills Integration Guide</a>**
 
-NPCI supports rich remittance information for all bill payments. 
-
 
 ## Fields Reference
 
@@ -39,11 +37,10 @@ NPCI supports rich remittance information for all bill payments.
 
 ## Usage Across Flows
 
-- Fetch/Validation requests: <Code>remitter</Code> is optional.
-- Payment requests (Flow 1–3): <Code>remitter.name</Code> and <Code>paymentDetails.accountInfo</Code> are required.
-- For CCF handling and funds movement, see <a href="/payments/billpay/api-integration/paying_bills#common-patterns" target="_blank">Paying Bills → Cross‑Flow Rules & Patterns</a>.
+- Fetch/Validation requests: <code>remitter</code> is optional.
+- Payment requests (Flow 1–3): <code>remitter.name</code> and <code>paymentDetails.accountInfo</code> are required.
 
-### Sample Payment Request (minimal)
+### Sample Payment Request
 
 <CodeBlockWithCopy language="json">{`
 {