Hi Fiuu team,
Thanks for the comprehensive documentation for the Direct Server API. While integrating across multiple channels, I found it difficult to clearly determine which fields are required, optional, or conditional for each specific channel.
The current Payment Request Parameters section provides a global list of parameters with M/O/C (Mandatory/Optional/Conditional) tags, but the conditional logic per TxnChannel is not clearly outlined.
On the parameter TxnChannelExt there is a reference to a Channel API Spec. Where can I find this documentation?
Suggestion
It would be extremely helpful if the documentation included:
A channel-specific request field matrix, showing the required, optional, and conditional fields per TxnChannel.
If possible, sample requests per channel.
| Paramater name |
Channel A |
Channel B |
| MerchantID |
M |
M |
| ReferenceNo |
M |
M |
| TxnCurrency |
M (SGD) |
M (PHP, MYR) |
| ... |
... |
... |
This addition would:
- Improve developer experience
- Minimize guesswork and errors in integration
- Clarify compliance requirements (e.g., PCI-DSS relevant fields)
- Decreases support load, as many common questions would be clarified directly in the documentation
Let me know if this can be considered for a future release of the API documentation. Happy to help test or contribute samples if useful.
Thanks!
Hi Fiuu team,
Thanks for the comprehensive documentation for the Direct Server API. While integrating across multiple channels, I found it difficult to clearly determine which fields are required, optional, or conditional for each specific channel.
The current Payment Request Parameters section provides a global list of parameters with M/O/C (Mandatory/Optional/Conditional) tags, but the conditional logic per TxnChannel is not clearly outlined.
On the parameter TxnChannelExt there is a reference to a Channel API Spec. Where can I find this documentation?
Suggestion
It would be extremely helpful if the documentation included:
A channel-specific request field matrix, showing the required, optional, and conditional fields per TxnChannel.
If possible, sample requests per channel.
This addition would:
Let me know if this can be considered for a future release of the API documentation. Happy to help test or contribute samples if useful.
Thanks!