Query Payment Order List
Query payment (collection) orders by time range with pagination. Supports filtering by order type, status, payment method, and other criteria.
Overview
This page documents the Query Payment Order List endpoint. The full schema, parameters, and examples are rendered from the linked OpenAPI definition above.Notes
- Authentication uses the standard GatePay signed headers.
- Commonly used for end-of-day reconciliation and reporting sync. Pair with payment callbacks; list queries serve as a fallback data source.
- For signing rules, see Security and Signature.
Headers
Application ClientId.
Request signature (HMAC-SHA512).
Millisecond timestamp; the difference from server time must not exceed 30 seconds.
Random nonce for replay protection.
Body
Payment order list query filters (multipart form fields).
Range start time in milliseconds.
Range end time in milliseconds.
Order status filter. Allowed values:
PENDING— Pending paymentPAID— Payment succeededERROR— Payment failedPROCESS— Payment in progressEXPIRED— ExpiredCANCELLED— CancelledBLOCK— Abnormal payment
PENDING, PAID, ERROR, PROCESS, EXPIRED, CANCELLED, BLOCK Payment method filter. Allowed values:
GatePay— Gate Pay
Note: the EU site currently supports GatePay only.
GatePay Transaction type filter. Allowed values:
checkout_pt— Checkout paymentaddress_pt— Address paymentcall_pt— App invoke paymentqrcode_pt— QR code paymentweb_pt— Web paymentmini_pt— GateLife paymentpayee_pt— Static payee QR codeagent_address_pt— AI paymentqrcode_ch— Channel QR code paymentbank_ch— Bank transfer paymentsubscription_address_pt— Subscription paymentinvoicing_pt— Invoicing payment
checkout_pt, address_pt, call_pt, qrcode_pt, web_pt, mini_pt, payee_pt, agent_address_pt, qrcode_ch, bank_ch, subscription_address_pt, invoicing_pt Page number, starting from 1.
Number of records per page. Maximum 500.

