COU Docs 16 Sep staging

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

@@ -1,15 +1,15 @@
 ---
-sidebar_title: Paying for alternative options
+sidebar_title: Paying for options
 page_title: Paying for alternative options
-order: 6
+order: 7
 visible_in_sidebar: true
 ---
 
 # Bill Payment Options Integration Guide
 
-## 1. You're Here Because Your Fetch Returned Payment Options
+## 1. Some Billers Allow Users to Pay Alternative Amounts for the Same Bill
 
-You successfully completed a Flow 1 bill fetch and discovered your response includes a `paymentOptions` array alongside the standard bill amount. This happens when billers—typically credit cards, loan providers, or utilities—offer customers multiple payment amounts instead of just the fixed bill amount.
+Some bill fetch responses includes a `paymentOptions` array alongside the standard bill amount. This happens when billers—typically credit cards, loan providers, or utilities—offer customers multiple payment amounts instead of just the fixed bill amount.
 
 Here's what your fetch response looks like when this happens:
 

content/payments/billpay/api-integration/customer-convenience-fee.mdx

@@ -1,7 +1,7 @@
 ---
-sidebar_title: Customer Convenience Fee (CCF)
+sidebar_title: Passing CCF
 page_title: Customer Convenience Fee (CCF) Integration Guide
-order: 7
+order: 6
 visible_in_sidebar: true
 ---
 

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

@@ -8,7 +8,7 @@ visible_in_sidebar: true
 
 # Remitter & Account Info
 
-## 1. You're Here Because You Need NPCI-Compatible Formatting
+## 1. NPCI Requirements for Remitter Details and Account Info for all Bill Payments
 
 Bill payments require remitter details and payment instrument information, and you will need to format them correctly for different payment methods. This guide provides the exact formatting specifications NPCI requires for each payment mode, plus validation rules to ensure your requests are accepted.