Query the exact configuration details, account numbers, routing codes, and payee information for a specific bound payment method using its unique identifier.
/sapi/v1/c2c/paymentMethod/getPayMethodById
This endpoint retrieves complete configuration parameters for a single user-configured payment method on Binance P2P.
By providing the payment configuration ID (id), callers can inspect recipient bank accounts, mobile money identifiers, payment method types, and recipient verification names.
Automated trading desks, merchant ERPs, and bot engines use this endpoint to pre-validate payment details before publishing new advertisements or matching incoming fiat settlement instructions.
Parameters accepted in Query String and HTTP Headers.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
clientType |
Header | STRING | Required |
Client Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE).
|
id |
Query | INT64 | Required |
Unique payment method configuration ID (payId).
|
x-gray-env |
Header | STRING | Optional | Environment flag identifier used for internal gray/stage testing. |
x-trace-id |
Header | STRING | Optional | Custom client trace ID for request lifecycle tracking and debugging. |
x-user-id |
Header | STRING | Optional | Target user identifier for context validation. |
The payment identifier must be appended to the endpoint URL as a query parameter (e.g., ?id=12345678) along with standard signature parameters.
Example GET request using cURL to fetch payment method details by ID.
curl -X GET \
'https://api.binance.com/sapi/v1/c2c/paymentMethod/getPayMethodById?id=12345678' \
-H 'clientType: WEB'
Example response returned on successful query execution.
{
"code": "000000",
"message": "success",
"data": {
"id": 12345678,
"payType": "BANK",
"payMethodName": "Bank Transfer",
"realName": "John Doe",
"fields": {
"account": "9876543210",
"bankName": "JPMorgan Chase",
"branch": "New York Main"
},
"status": 1
},
"success": true
}
| Field | Type | Description |
|---|---|---|
code |
STRING |
Standard Binance status code ("000000" indicates success).
|
data.id |
INT64 | Unique payment method configuration ID. |
data.payType |
STRING |
Internal identifier for the payment type (e.g., BANK, REVOLUT, WISE).
|
data.payMethodName |
STRING | User-friendly display name of the payment method. |
data.realName |
STRING | Verified account holder name associated with the payment method. |
data.fields |
OBJECT | Key-value map containing payment-specific attributes (such as account number, IBAN, or bank name). |
data.status |
INT |
Configuration status flag (1: Active, 0: Inactive/Disabled).
|
success |
BOOLEAN | Indicates overall request execution result. |
Workflow for retrieving payment method configuration details.
payId) from account list or ad config.
Ensure a selected payId is active and contains valid bank credentials before binding it to a newly published advertisement.
Extract account numbers and routing codes dynamically to route outgoing fiat wires from internal treasury systems.
Verify payment method integrity and active status flags across large fleets of automated merchant accounts.
This article is part of our complete learning guide covering professional cross-exchange cryptocurrency arbitrage.
Explore the Spot Arbitrage Guide →This article is part of our complete learning guide covering Binance P2P automation, merchant tools, and automated trading.
Explore the Binance P2P Automation Guide →