QR Payment Query Parameters
Configure the properties file as described in the Query Properties File.
- Request Parameters
- Response Parameters
Mandatory Fields
| Field Name | Type | Length | Description | Example |
|---|---|---|---|---|
PaymentID | String | 3 | Payment Method/Function. | "U02" – UPP Payment Status Query |
MerchantID | String | 15 | Merchant ID. | "000010000099939" |
ServiceID | String | 3 | Service ID. | "FNX" |
MerchRefNo | String | 40 | Unique merchant reference number. | "MYB2023030315435025LL" |
QueryRespURL | String | 512 | Query response page. | "https://XXX.XXXXX.XXX/query.jsp" |
Mandatory Fields
| Field Name | Type | Length | Description | Example |
|---|---|---|---|---|
MerchantID | String | 15 | Merchant ID. | "000010000099939" |
TxnStatus | String | 2 | Transaction status. Appendix 3 | "00" |
MerchRefNo | String | 40 | Unique merchant reference number. | "MYB2023030315435025LL" |
QueryStatus | String | 2 | Query status. Appendix 3 | "00" |
Optional Fields
Field Name Type Length Description Example CardNoString 19 Card number.
Note: Only for Credit/Debit Payment method. "545301XXXXXX5323" TxnDtTmString 14 Transaction date and time.
Format: yyyymmddhhmmss "20230303154833" TxnAmtString (Numeric) 12 Transaction amount. "100.00" CurrCodeString 3 Currency code. "458" AuthIDRespCodeString 6 Authorization ID response code.
Note: Generated by issuer and forwarded to Acquirer to indicate the approval of a transaction. Only for successful payment. "457180" ExpTxnAmtString 1 Exponent of transaction amount. "0" RetrievalRefNoString 12 Retrieval Reference Number.
Note: Available if this field returned by Acquirer in the response message. "306274008021" OrgRespCodeString 8 Original Response Code.
Note: Available if the original bank response code is not larger than 8 characters. " " OrigTxnAmtString (Numeric) 12 Original transaction amount. "10000" OrigCurrCodeString 3 Original transaction currency numeric code. "458" TxnChannelString 3 Transaction channel. "WEB" - Web Channel (default),
"API"- via API,
"DIR" - Direct,
"GDS" - GDS Channel,
"OTH" – Others FICodeString 20 Financial institution Code. Appendix 4
Note: Available for FPX payment with UppPymtMode = 01. "CIMB" PymtGwRefNoString 20 Payment Gateway Reference Number. "230303154349AC010FNX" TxnStatDetCdeString 4 Transaction status detail code. "0000" TxnStatMsgString 256 Transaction status message "Approved" ServiceIDString 3 Service Identifier provided by PayMaster. "FNX" MerchHostIDString 8 Merchant host identifier. "M2022121" MerchSessionIDString 256 Merchant session ID. "2023030315435025" OrderRefNoString 34 Order reference number. "OTMEGASTORE-20010831-ONLINE-007" FPXRefNoString 20 Unique FPX reference number generated by FI.
Note: Available for FPX payment and existed in the FI system with UppPymtMode = 01. "3143323587217932" UppPymtModeString 2 Payment mode chosen at UPP page. "00" - Credit/Debit Card Payment,
"01" - FPX Payment,
"99" - Unknown or some error occurred during the processing ExpOrigTxnAmtString 1 Exponent of original transaction amount. "2"
CardNoNote: Only for Credit/Debit Payment method.
TxnDtTmFormat: yyyymmddhhmmss
TxnAmtCurrCodeAuthIDRespCodeNote: Generated by issuer and forwarded to Acquirer to indicate the approval of a transaction. Only for successful payment.
ExpTxnAmtRetrievalRefNoNote: Available if this field returned by Acquirer in the response message.
OrgRespCodeNote: Available if the original bank response code is not larger than 8 characters.
OrigTxnAmtOrigCurrCodeTxnChannel"API"- via API,
"DIR" - Direct,
"GDS" - GDS Channel,
"OTH" – Others
FICodeNote: Available for FPX payment with
UppPymtMode = 01.PymtGwRefNoTxnStatDetCdeTxnStatMsgServiceIDMerchHostIDMerchSessionIDOrderRefNoFPXRefNoNote: Available for FPX payment and existed in the FI system with
UppPymtMode = 01.UppPymtMode"01" - FPX Payment,
"99" - Unknown or some error occurred during the processing
ExpOrigTxnAmtMerchRefNo, MerchantID, OrderRefNo, CardNo, TxnChannel, CurrCode, TxnAmt, ExpTxnAmt, OrigCurrCode, OrigTxnAmt, ExpOrigTxnAmt, MerchHostID and MerchSessionID have the same value as in prior payment request.
Example Message
- Request
- Response
QR Payment Query Request
{
"paymentID": "U02",
"merchantID": "000010000099939",
"serviceID": "",
"merchRefNo": "MYB2023030315435025LL",
"queryRespURL": ""
}
QR Payment Query Response
{
"merchantID": "000010000099939",
"cardNo": "545301XXXXXX5323",
"txnDtTm": "20230303154833",
"txnAmt": "100.00",
"txnStatus": "00",
"currCode": "458",
"authIDRespCode": "457180",
"expTxnAmt": "2",
"retrievalRefNo": "306274008021",
"origRespCode": "",
"pymtGwRefNo": "230303154349AC010FNX",
"txnStatDetCde": "0000",
"txnStatMsg": "Approved",
"serviceID": "FNX",
"merchHostID": "",
"merchSessionID": "2023030315435025",
"merchRefNo": "MYB2023030315435025LL",
"orderRefNo": "",
"uppPymtMode": "00",
"queryStatus": "00",
"origCurrCode": "458",
"origTxnAmt": "10000",
"expOrigTxnAmt": "0",
"FICode": "",
"FPXRefNo": "",
"txnChannel": "WEB"
}