Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 13 additions & 9 deletions api-references/payments/billpay/api-integration.json
Original file line number Diff line number Diff line change
Expand Up @@ -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."
Expand All @@ -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",
Expand Down Expand Up @@ -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
}
}
Expand Down Expand Up @@ -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."
Expand All @@ -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",
Expand Down Expand Up @@ -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
}
}
Expand Down Expand Up @@ -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."
Expand Down
1 change: 0 additions & 1 deletion content/payments/billpay/api-integration/objects.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Loading