Binance API / SAPI / C2C
BINANCE SAPI · C2C

Get Payment Method by UserId API

Retrieve a complete list of all configured and bound payment methods, bank accounts, and digital wallets associated with the authenticated user account.

ENDPOINT
GET /sapi/v1/c2c/paymentMethod/getPayMethodByUserId
Authentication USER_DATA / SIGNED
API Group C2C / Payment Method
Method GET
Response JSON (Array)

Overview

This endpoint fetches all user-configured payment channels available for Binance C2C (P2P) trading. It returns an array of payment method configurations, including unique identifiers (id / payId), payment channel names, verified beneficiary account names, bank identifiers, and current activation statuses.

Automated trading software, merchant consoles, and dynamic ad placement bots invoke this endpoint during initialization routines to populate selectable payment methods and determine valid payId values for advertisement creation.

01

Request Parameters

Header parameters accepted by the endpoint.

HeaderTypeRequiredDescription
clientTypeSTRINGRequiredClient Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE).
x-gray-envSTRINGOptionalEnvironment flag identifier used for internal gray/stage testing.
x-trace-idSTRINGOptionalCustom client trace ID for request lifecycle tracking and debugging.
x-user-idSTRINGOptionalTarget user identifier for context validation.
i

Parameterless GET Request

This endpoint does not require URL query strings or JSON request bodies. Simply pass the mandatory clientType header in the HTTP request.

02

Request Example

Example GET request using cURL to list all user payment methods.

cURL BASH
curl -X GET \
'https://api.binance.com/sapi/v1/c2c/paymentMethod/getPayMethodByUserId' \
-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": "Chase Bank",
                "branch": "New York"
            },
            "status": 1
        },
        {
            "id": 87654321,
            "payType": "REVOLUT",
            "payMethodName": "Revolut",
            "realName": "John Doe",
            "fields": {
                "revtag": "@johndoe",
                "phone": "+123456789"
            },
            "status": 1
        }
    ],
    "success": true
}

Response Fields

FieldTypeDescription
codeSTRINGStandard Binance status code ("000000" indicates success).
dataARRAYList of user payment configuration objects.
data[].idINT64Unique payment method configuration ID (used as payId in order matching and ad management).
data[].payTypeSTRINGInternal identifier for the payment type (e.g., BANK, REVOLUT, WISE).
data[].payMethodNameSTRINGUser-facing label for the payment channel.
data[].realNameSTRINGVerified legal account holder name.
data[].fieldsOBJECTKey-value dictionary containing account details, IBAN, bank name, or digital handle.
data[].statusINTActivation status flag (1: Active, 0: Inactive/Disabled).
successBOOLEANIndicates overall request execution result.

04

How It Works

Workflow for listing all user-configured payment channels.

01 Set Headers Attach clientType and user-data credentials.
 
02 Send GET Request Call /sapi/v1/c2c/paymentMethod/getPayMethodByUserId.
 
03 Parse Method IDs Extract id list and payment channel types.
 
04 Bind to Ads & Orders Use retrieved IDs to publish ads or configure bot payouts.

Common Use Cases

Dynamic Ad Creation

Populate active payment method IDs automatically when publishing new buy/sell advertisements via bot scripts.

Merchant Account Auditing

Inspect all bound bank accounts and payment channels to verify that details remain current and active.

UI Payment Selectors

Populate payment option dropdowns in custom web portals and mobile merchant management interfaces.

💬
Telegram WhatsApp