diff --git a/content/payments/billpay/api-integration/objects.mdx b/content/payments/billpay/api-integration/objects.mdx index aa2584e3..babbc151 100644 --- a/content/payments/billpay/api-integration/objects.mdx +++ b/content/payments/billpay/api-integration/objects.mdx @@ -139,7 +139,7 @@ A standard structure for representing errors in API responses or callbacks. | parameter | type | description | | ---------------------- | ------------------------------------------------------- | ----------------------------------------------------------- | | mode | [Payment Mode](#payment-mode) | Payment Mode | -| paymentRefId | `string` (6 - 35 characters) | Payment Reference ID tagged by agent | +| paymentRefId | `string` (6 - 35 characters) | Unique Payment Reference ID tagged by agent | | amount | `integer` | Amount in paise | | timestamp | `date-time` | Timestamp | | selectedPaymentOptions | [Selected Payment Option](#selected-payment-option)`[]` | Array of selected payment options | diff --git a/content/payments/billpay/api-integration/remittance_flows_guide.mdx b/content/payments/billpay/api-integration/remittance_flows_guide.mdx index a54889c2..6ce6e75f 100644 --- a/content/payments/billpay/api-integration/remittance_flows_guide.mdx +++ b/content/payments/billpay/api-integration/remittance_flows_guide.mdx @@ -93,9 +93,4 @@ The following table provides detailed formatting specifications for different NP - In payment requests across Flow 1–3, `remitter.name` and `paymentDetails.accountInfo` are required - The `paymentDetails.accountInfo` field must contain NPCI-compatible values corresponding to the selected payment mode -#### 4.3.2 Optional Field Handling -- `remitter.email`, `remitter.pan`, and `remitter.aadhaar` are optional and can be omitted if not available -- Including `remitter` in bill fetch/validation requests is optional -- System automatically handles fallback scenarios for missing optional data -