Skip to content

Transaction Inquiry

This API is used to query payment order details within a specified time range in a paginated manner. It supports filtering by time, order status, country, payment method, channel, and other dimensions, helping merchants or system operators quickly locate and retrieve historical transaction records.

Recommended Use Cases:

  • Log analysis and exception troubleshooting;

  • Daily reconciliation reference;

  • Backend data export and data governance.

1. API Path

POST https://pay-gate-uat.payermax.com/aggregate-pay/api/gateway/paymentOrderQry

2. Environment Information

  • Test Environment: https:// pay-gate-uat.payermax.com/aggregate-pay/api/gateway/ <API PATH>

  • Integration Environment: https:// pay-gate.payermax.com/aggregate-pay/api/gateway/ <API PATH>

3. Request Parameter Description

3.1 Headers

Parameter NameTypeMandatory (Y/N)Example ValueDescription
signStringMFPFVT3o227JrFRbqu...Request signature, please refer to the signature generation rules

3.2 Body

Parameter NameTypeMandatory (Y/N)Example ValueDescription
versionStringM1.4API version; the current version is 1.4
keyVersionStringM1Key version; the current version is 1
requestTimeStringM2025-04-23T10:00:00.500+08:00Request time, compliant with RFC 3339 standard, format: yyyy-MM-dd’T’HH:mm:ss.SSSXXX
appIdStringM6666c83333a24666674497c444a33333Merchant App ID; the unique identifier assigned by PayerMax to the merchant's application
merchantNoStringM10213834123456Merchant Number; the unique identifier generated when the merchant signs a business contract with PayerMax
dataObjectMRequest data body
└─ queryBeginTimeStringM2025-04-23 01:00:00Transaction query start time, time zone UTC+0, format: yyyy-MM-dd HH:mm:ss; the time interval between start time and end time cannot exceed 1 day
└─ queryEndTimeStringM"2025-04-23 02:00:00"Transaction query end time, time zone UTC+0, format: yyyy-MM-dd HH:mm:ss; the time interval between start time and end time cannot exceed 1 day
└─ pageSizeLongO20Maximum number of transactions returned per query; cannot exceed 100. If this field is not provided, the query will return the first 20 transactions sorted by order creation time in ascending order
└─ currentPageIndexLongO3The page number of data to be queried in this request. If this field is not provided, the query will return the first page of the result set
└─ statusStringOPENDINGStatus of the orders to be queried in this request: SUCCESS (Successful), FAILED (Failed), PENDING (Processing), BOUNCEBACK (Payment Reversed)
└─ countryStringOPHCountry of the orders to be queried in this request
└─ paymentMethodTypeStringOWALLETPayment method type of the orders to be queried in this request
└─ targetOrgStringOGCASHTarget institution of the orders to be queried in this request
└─ clearingRailStringOLOCALClearing network of the orders to be queried in this request, mainly for bank transfer types

3.3 Request Example

json
{
  "version": "1.4",
  "keyVersion": "1",
  "requestTime": "2025-04-23T10:00:00.500+08:00",
  "appId": "6666c83333a24666674497c444a33333",
  "merchantNo": "010213834123456",
  "data": {
    "queryBeginTime": "2025-04-23 01:00:00",
    "queryEndTime": "2025-04-23 02:00:00",
    "pageSize": 20,
    "currentPageIndex": 2,
    "status": "PENDING",
    "country": "PH",
    "paymentMethodType": "WALLET",
    "targetOrg": "GCASH",
    "clearingRail": ""
  }
}

This query example means:

  • Query all transactions with a PENDING status in the Philippines GCASH wallet between 01:00 and 02:00 on April 23, 2025;

  • Returns 20 records per page, currently requesting page 2.

4. Response Parameter Description

4.1 Top-Level Fields (code/msg/data)

Field NameTypeMandatory (Y/N)Example ValueDescription
codeStringMAPPLY_SUCCESSReturn code; APPLY_SUCCESS indicates success. It only means the API request is successful, not the order status.
msgStringMSuccess.Return description.
dataObjectM-Return data body

4.2 data Field Structure

Field NameTypeMandatory (Y/N)Example ValueDescription
totalTransactionNumLongM98Total number of orders within the query time interval. When the total number is 0, the pageIndex and transactionList fields will not be present
maxPageIndexLongO10Maximum page number after paginating the query results according to the pageSize in the input parameters. If pageSize is not provided in the input parameters, the default is 20 items per page
currentPageIndexLongO2Current result set page number, which does not exceed maxPageIndex
transactionListArrayO-List of order information. This field is not empty when totalTransactionNum is greater than 0

4.3 transactionList Field Structure

Field PathTypeMandatory (Y/N)Example ValueDescription
transactionUtcTimeStringM2024-07-29T12:32:53+0000Transaction creation time, compliant with RFC 3339 standard, format: yyyy-MM-dd’T’HH:mm:ss Z
outTradeNoStringMORDER123456789Merchant Order Number
tradeNoStringM20250423012658PO71330000270184PayerMax Transaction Serial Number
accountInfo.accountNoStringM123456****1234Payee Account Number, returned in desensitized format (showing first 6 and last 4 digits)
name.fullNameStringOAntonio Maldonado EvangelistaPayee Name
statusStringMFAILEDTransaction Status
responseCodeStringOINVALID_ACCOUNTOrder Failure Error Code, see Transaction Status/Error Codes for details
responseMsgStringOInvalid accountOrder Failure Error Description
referenceStringOthis is referenceAdditional Data, value submitted during order placement
redeemCodeStringO-1. FAWRY Withdrawal Code; 2. Telecom Operator Top-up PIN Code
expiryTimeStringO2022-12-02T11:35:23+0000Order Expiration Time, compliant with RFC 3339 standard, format: yyyy-MM-dd’T’HH:mm:ss Z
bounceBackTimeStringO2022-12-02T11:35:23+0000Payment Reversal Time, compliant with RFC 3339 standard, format: yyyy-MM-dd’T’HH:mm:ss Z
payFinishTimeStringO2022-12-02T11:35:23+0000Transaction Completion Time, compliant with RFC 3339 standard, format: yyyy-MM-dd’T’HH:mm:ss Z
countryStringMPHCountry
paymentMethodTypeStringMWALLETPayment Method Type
targetOrgStringOGCASHTarget Institution
clearingRailStringOLOCALClearing Network
trade.amountStringM3223.59Payment Amount Submitted in the Request
trade.currencyStringMPHPPayment Currency, currency code corresponding to the payment amount submitted in the request
source.amountStringM3223.59Payer - Debited Amount
source.currencyStringMPHPPayer - Debited Currency
source.exchangeRateStringO1.00000000Exchange Rate for Converting Transaction Currency to Debited Currency
source.feeStringO0Payer - Service Fee
source.feeCurrencyStringOPHPPayer - Service Fee Currency
source.taxStringO0Payer - Tax
source.taxCurrencyStringOPHPPayer - Tax Currency
destination.amountStringM3223Payee - Received Amount
destination.currencyStringMPHPPayee - Received Amount Currency
destination.exchangeRateStringO1.00000000Exchange Rate for Converting Transaction Currency to Received Currency
destination.feeStringO0.59Payee - Service Fee
destination.feeCurrencyStringOPHPPayee - Service Fee Currency
destination.taxStringO0Payee - Tax
destination.taxCurrencyStringOPHPPayee - Tax Currency
notifyPhoneStringO1234454556Payee Notification Phone Number
notifyEmailStringOxxxx@gmail.comPayee Notification Email

5. Interface Response Code Description

CodeMsgDescription
APPLY_SUCCESSSuccess.The request is successful, and the content in data can be parsed normally
PARAMS_INVALIDqueryBeginTime cannot be emptyThe transaction query start time cannot be empty
PARAMS_INVALIDInvalid queryBeginTime formatThe transaction query start time format is incorrect
PARAMS_INVALIDqueryEndTime cannot be emptyThe transaction query end time cannot be empty
PARAMS_INVALIDInvalid queryEndTime formatThe transaction query end time format is incorrect
PARAMS_INVALIDqueryBeginTime must be earlier than current timeThe start time must be earlier than the current time
PARAMS_INVALIDqueryEndTime must be earlier than current timeThe end time must be earlier than the current time
PARAMS_INVALIDqueryBeginTime cannot exceed six months from current timeThe start time cannot be more than 6 months from the current time
PARAMS_INVALIDTime interval between queryBeginTime and queryEndTime exceeds maximum allowed durationThe time interval between the start time and end time exceeds the maximum limit
PARAMS_INVALIDqueryEndTime must be later than queryBeginTimeThe end time must be later than the start time
PARAMS_INVALIDpageSize cannot exceed maxPageSizepageSize exceeds the maximum limit
PARAMS_INVALIDcurrentPageIndex must not exceed maxPageIndexcurrentPageIndex exceeds the maximum page number
PARAMS_INVALIDThe status is incorrect.The status parameter is incorrect; only SUCCESS, FAILED, PENDING, and BOUNCEBACK are supported
PARAMS_INVALIDThe country is incorrect.The country parameter is invalid
PARAMS_INVALIDThe paymentMethodType is incorrect.The paymentMethodType parameter is invalid
SYSTEM_ERRORSystem is busy, please try again later.System exception, please try again later

Was this page helpful?

Thank you for your help in improving PayerMax Product Docs!

Last updated:

Released under the MIT License.