fix staging errors

Author: tanmay

api-references/payments/billpay/api-integration.json

@@ -432,7 +432,7 @@
                                 "value": {
                                   "type": "string",
                                   "description": "The value of the biller parameter to be sent as part of UPMS registration.",
-                                  "example": "500.0"
+                                  "example": "500"
                                 }
                               },
                               "description": "Optional. Only some billers require this. Details of the biller parameter to be sent as part of UPMS registration."
@@ -444,11 +444,13 @@
                             "properties": {
                               "amount": {
                                 "type": "integer",
-                                "description": "The fixed or maximum amount set for auto-debit (value must be provided in paise)."
+                                "description": "The fixed or maximum amount set for auto-debit (value must be provided in paise).",
+                                "example": 10000
                               },
                               "currency": {
                                 "type": "integer",
-                                "description": "The currency code. Use `356` for `INR`."
+                                "description": "The currency code. Use `356` for `INR`.",
+                                "example": 356
                               },
                               "debitDate": {
                                 "type": "string",
@@ -477,7 +479,7 @@
                             "type": "string",
                             "description": "The UPMS registration is invalid after this date. Date format is YYYY-MM-DD",
                             "nullable": true,
-                            "example": "2025-01-01",
+                            "example": "2027-01-01",
                             "x-omitempty": true
                           }
                         }
@@ -7127,7 +7129,7 @@
                                   "value": {
                                     "type": "string",
                                     "description": "The value of the biller parameter to be sent as part of UPMS registration.",
-                                    "example": "500.0"
+                                    "example": "500"
                                   }
                                 },
                                 "description": "Optional. Only some billers require this. Details of the biller parameter to be sent as part of UPMS registration."
@@ -7139,11 +7141,13 @@
                               "properties": {
                                 "amount": {
                                   "type": "integer",
-                                  "description": "The fixed or maximum amount set for auto-debit (value must be provided in paise)."
+                                  "description": "The fixed or maximum amount set for auto-debit (value must be provided in paise).",
+                                  "example": 10000
                                 },
                                 "currency": {
                                   "type": "integer",
-                                  "description": "The currency code. Use `356` for `INR`."
+                                  "description": "The currency code. Use `356` for `INR`.",
+                                  "example": 356
                                 },
                                 "debitDate": {
                                   "type": "string",
@@ -7172,7 +7176,7 @@
                               "type": "string",
                               "description": "The UPMS registration is invalid after this date. Date format is YYYY-MM-DD",
                               "nullable": true,
-                              "example": "2025-01-01",
+                              "example": "2027-01-01",
                               "x-omitempty": true
                             }
                           }
@@ -7734,7 +7738,7 @@
                         "type": "string",
                         "description": "The date until which the mandate is valid (YYYY-MM-DD). Must be a future date.",
                         "format": "date",
-                        "example": "2025-01-01"
+                        "example": "2027-01-01"
                       }
                     },
                     "description": "Details of the mandate to be updated. Only include fields that need changing."

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

@@ -148,7 +148,6 @@ A standard structure for representing errors in API responses or callbacks.
 | `code`    | `string` | A short code identifying the error category (e.g., `validation-error`, `biller-registration-failed`).          |
 | `message` | `string` | A human-readable description of the error.                                                                     |
 
-**Note:** In some asynchronous UPMS callbacks (e.g., for failed registration/update/cancel), the field names might appear as `Code` and `Message` (PascalCase) instead of `code` and `message`. Your callback handler should accommodate this potential difference.
 
 ## Payment Details