Query Partner Transactions

Retrieves partner-level balance transactions for a date range, with optional filters and pagination.

Endpoint

POST /remittance/partner/query-transactions

Sandbox base URL: https://rem-api-sandbox.pagsmile.com Content-Type: application/json; charset=UTF-8

The request uses the standard Remittance API request envelope. The fields below describe the decrypted biz_data object.

Requirement: M = Mandatory, O = Optional, and C = Conditional. A conditional field is mandatory only when the condition stated in its description applies.

Encrypt biz_data, encrypt the AES key into random_key, and sign the request according to the Common request specification.

Request body

Decrypted biz_data fields

Field	Type	Requirement	Description
order_no	string	O	Merchant-defined order number used to submit, query, and reconcile the partner transaction.
transaction_status	integer	O	Current processing status of the transaction. See Transaction Status for supported values.
transaction_type	integer	O	Business transaction type represented by the record. See Transaction Type for supported values.
currency	string	O	Three-letter ISO 4217 code of the currency in which the partner transaction values are denominated.
start_date	string	M	Start of the query period, inclusive. Format: yyyy-MM-dd.
end_date	string	M	End of the query period, inclusive. Format: yyyy-MM-dd.
page_num	integer	O	One-based page number of the result set. Default: 1.
page_size	integer	O	Maximum number of records returned on each page. Default: 10. Maximum: 30.

Max query time range : 31 days

Plaintext biz_data example

This example includes mandatory fields and representative optional or conditional fields. Submit fields marked C only when the condition in the field description applies.

{
  "order_no": "ORDER_202607200001",
  "transaction_status": 1,
  "transaction_type": 1,
  "currency": "USD",
  "start_date": "2026-07-20",
  "end_date": "2026-07-20",
  "page_num": 1,
  "page_size": 10
}

Request example

curl --request POST \
  --url https://rem-api-sandbox.pagsmile.com/remittance/partner/query-transactions \
  --header 'Content-Type: application/json; charset=UTF-8' \
  --data '{
    "partner_id": "<your_partner_id>",
    "app_id": "<your_app_id>",
    "timestamp": "2026-07-20 10:30:00",
    "version": "2.0",
    "language": "en",
    "random_key": "<RSA-encrypted AES key>",
    "request_id": "<globally_unique_request_id>",
    "sign_type": "RSA",
    "biz_data": "<AES-encrypted biz_data>"
  }'

Use the partner_id and app_id assigned to your integration. The values above are placeholders.

Response

Success

The data field in the response envelope is AES-encrypted. Decrypt random_key with your RSA private key, then use the resulting AES key to decrypt data. See Security for implementation details.

Encrypted response example

{
  "code": "10000",
  "msg": "Success",
  "data": "<AES-encrypted response data>",
  "total": 2,
  "random_key": "<RSA-encrypted AES key>",
  "sign_type": "RSA",
  "app_id": "2017051914172236111"
}

Decrypted data example

[
  {
    "transaction_id": "100009",
    "order_no": "1721981116404",
    "transaction_type": 100,
    "transaction_status": 1,
    "account_no": "200100******0057",
    "account_name": "individual - autotest - 20240726+142031 Williams",
    "billing_currency": "USD",
    "billing_amount": "5.00",
    "billing_fee": "0.00",
    "transaction_amount": "5.00",
    "transaction_currency": "USD",
    "exchange_rate": "1",
    "reference": "6",
    "related_transaction_id": "",
    "business_date": "2026-07-20",
    "created_at": "2026-07-20 10:30:00"
  }
]

Invalid signature

{
  "code": "40002",
  "msg": "Business Failed",
  "sub_code": "invalid-signature",
  "sub_msg": "invalid signature"
}

Response data fields

Field	Type	Requirement	Description
transaction_id	string	O	Pagsmile-assigned unique identifier of the transaction.
order_no	string	O	Merchant-defined order number used to submit, query, and reconcile the partner transaction.
transaction_type	integer	O	Business transaction type represented by the record. See Transaction Type for supported values.
transaction_status	integer	O	Current processing status of the transaction. See Transaction Status for supported values.
account_no	string	O	Partner account number associated with the returned transactions.
account_name	string	O	Name registered on the account.
billing_currency	string	O	Three-letter ISO 4217 code of the account billing currency.
billing_amount	string	O	Amount posted to the account in the billing currency.
billing_fee	string	O	Fee posted to the account in the billing currency.
transaction_amount	string	O	Amount of the account transaction in the transaction currency.
transaction_currency	string	O	Three-letter ISO 4217 code of the transaction currency.
exchange_rate	string	O	Exchange rate applied to convert the transaction currency.
reference	string	O	Merchant-provided reference used to reconcile the transaction with the merchant's internal records.
related_transaction_id	string	O	Pagsmile-assigned unique identifier of the related transaction, such as the original transaction for a refund or adjustment.
business_date	string	O	Business date on which the transaction was posted. Format: yyyy-MM-dd.
created_at	string	O	Date and time when the partner transaction was created. Format: yyyy-MM-dd HH:​mm:ss.

Related APIs

• Create Topup Order

• Query Partner Balance

• Query Topup Result