Query Payment Fields

Returns the beneficiary fields and validation rules required for a selected country, currency, payment type, and account type.

Endpoint

POST /remittance/payment/query-fields

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
merchant_id	long	O	Pagsmile-assigned unique identifier of the merchant.
bank_country	string	M	Two-letter ISO 3166-1 alpha-2 code of the country where the bank account is held.
receive_currency	string	M	Three-letter ISO 4217 code of the currency credited to the recipient.
payment_type	integer	M	Payment route used to deliver funds to the recipient. See Payment Type for supported values.
account_type	integer	M	Type of destination bank account. See Account Type for supported values.
payee_type	integer	M	Classification of the payee or beneficiary. See Payee Type for supported values.

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.

{
  "merchant_id": 100398,
  "bank_country": "BR",
  "receive_currency": "USD",
  "payment_type": 1,
  "account_type": 1,
  "payee_type": 1
}

Request example

curl --request POST \
  --url https://rem-api-sandbox.pagsmile.com/remittance/payment/query-fields \
  --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>",
  "random_key": "<RSA-encrypted AES key>",
  "sign_type": "RSA",
  "app_id": "2017051914172236111"
}

Decrypted data example

{
  "payee_fields": {
    "SPI_PIX": [],
    "SPI_ISPB": []
  }
}

Invalid signature

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

Response data fields

Field	Type	Requirement	Description
payee_fields	object	M	Beneficiary field definitions grouped by payment rail. Each object key is a supported payment rail, such as SPI_PIX.
payee_fields.<payment_rail>	list	M	Fields accepted in payee_values for the corresponding payment rail. An empty list means no additional fields are required.
payee_fields.<payment_rail>[0].field	string	O	API field name accepted in the beneficiary payee_values object.
payee_fields.<payment_rail>[0].name	string	O	Human-readable label of the beneficiary field.
payee_fields.<payment_rail>[0].required	boolean	O	Indicates whether the beneficiary field must be supplied for the payment rail.
payee_fields.<payment_rail>[0].rule	string	O	Validation rule applied to the beneficiary field, when provided.

Related APIs

• Create Beneficiary

• Create Payment Order

• Delete Beneficiary

• Payment Result Notification

• Query Beneficiary Detail

• Query Payment Orders

• Update Beneficiary