BINANCE SAPI · C2C

Get Payment Method by ID API

Query the exact configuration details, account numbers, routing codes, and payee information for a specific bound payment method using its unique identifier.

ENDPOINT
GET /sapi/v1/c2c/paymentMethod/getPayMethodById
Authentication USER_DATA / SIGNED
API Group C2C / Payment Method
Method GET
Response JSON

Overview

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.

01

Request Parameters

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.
i
Query Parameter Construction

The payment identifier must be appended to the endpoint URL as a query parameter (e.g., ?id=12345678) along with standard signature parameters.

02

Request Example

Example GET request using cURL to fetch payment method details by ID.

cURL BASH
curl -X GET \
'https://api.binance.com/sapi/v1/c2c/paymentMethod/getPayMethodById?id=12345678' \
-H 'clientType: WEB'
03

Response

Example response returned on successful query execution.

RESPONSE 200 OK
{
    "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
}

Response Fields

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.
04

How It Works

Workflow for retrieving payment method configuration details.

01 Obtain ID Get payment method ID (payId) from account list or ad config.
02 Send GET Request Call /sapi/v1/c2c/paymentMethod/getPayMethodById?id={id}.
03 Parse Configuration Extract account number, bank details, and active status.
04 Validate Settlement Confirm details match target fiat bank accounts for trade execution.

Common Use Cases

Ad Creation Pre-Validation

Ensure a selected payId is active and contains valid bank credentials before binding it to a newly published advertisement.

Automated Payout Routing

Extract account numbers and routing codes dynamically to route outgoing fiat wires from internal treasury systems.

Merchant Configuration Audits

Verify payment method integrity and active status flags across large fleets of automated merchant accounts.



💬
Telegram WhatsApp