Skip to content

COU Staging docs 16 Sep #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tanmay-dixit merged 10 commits into from
Sep 16, 2025
Merged

COU Staging docs 16 Sep #348

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
3241eb3
updates to titles & menu items
Sep 15, 2025
ce3ee94
fix links
Sep 15, 2025
1a4658c
fix bill payment options
Sep 15, 2025
dd72559
build menuItems
Sep 16, 2025
a29910e
add integration for time based payment options
Sep 16, 2025
81ede82
style/content tweaks
Sep 16, 2025
606bca5
feedback from review
Sep 16, 2025
02ee976
remove extra space
Sep 16, 2025
f79a2bd
Merge branch 'cou-api-docs-revamp' of https://github.com/SetuHQ/docs …
Sep 16, 2025
58ceb4f
Merge branch 'staging' of https://github.com/SetuHQ/docs into cou-doc…
Sep 16, 2025
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
2 changes: 1 addition & 1 deletion content/payments/billpay/api-integration/objects.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 |
Expand Down
5 changes: 0 additions & 5 deletions content/payments/billpay/api-integration/remittance_flows_guide.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

<WasPageHelpful />