BINANCE SAPI · C2C

List All Of Valid Payment Methods API

Query the complete directory of globally supported peer-to-peer (C2C) payment methods, banking rails, and regional e-wallets available on the Binance platform.

ENDPOINT
POST /sapi/v1/c2c/paymentMethod/listAll
Authentication USER_DATA / SIGNED
API Group C2C / Payment Method
Method POST
Response JSON (Paginated)

Overview

This endpoint provides access to the master registry of all valid payment methods supported across Binance C2C (P2P) fiat markets. It returns detailed payment method definitions, including channel identifiers (identifier / payType), localized display names, required metadata input fields, and supported fiat currencies.

Trading desk applications, multi-currency arbitrage platforms, and merchant software query this catalog to populate dynamic payment channel selectors and ensure custom integrations conform to required banking field schemas.

01

Request Parameters

Header parameters accepted by the endpoint.

Header Type Required Description
clientType STRING Required Client Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE).
x-gray-env STRING Optional Environment flag identifier used for internal gray/stage testing.
x-trace-id STRING Optional Custom client trace ID for request lifecycle tracking and debugging.
x-user-id STRING Optional Target user identifier for context validation.
i
POST with Empty Body

This catalog inquiry runs via an HTTP POST call with an empty body. Ensure the required clientType header is present in your request headers.

02

Request Example

Example POST request using cURL to fetch the global payment method catalog.

cURL BASH
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/paymentMethod/listAll' \
-H 'clientType: WEB'
03

Response

Example response returned on successful catalog query.

RESPONSE 200 OK
{
    "code": "000000",
    "message": "success",
    "data": {
        "total": 350,
        "data": [
            {
                "identifier": "BANK",
                "name": "Bank Transfer",
                "tradeType": "BOTH",
                "fields": [
                    {
                        "fieldName": "account",
                        "fieldTitle": "Bank Account Number",
                        "required": true
                    },
                    {
                        "fieldName": "bankName",
                        "fieldTitle": "Bank Name",
                        "required": true
                    },
                    {
                        "fieldName": "branch",
                        "fieldTitle": "Branch Info",
                        "required": false
                    }
                ]
            },
            {
                "identifier": "REVOLUT",
                "name": "Revolut",
                "tradeType": "BOTH",
                "fields": [
                    {
                        "fieldName": "revtag",
                        "fieldTitle": "Revtag / Phone Number",
                        "required": true
                    }
                ]
            }
        ]
    },
    "success": true
}

Response Fields

Field Type Description
code STRING Standard Binance status code ("000000" indicates success).
data.total INT Total count of supported payment channels in the catalog.
data.data ARRAY Collection of supported payment channel specification objects.
data.data[].identifier STRING Unique payment type code (e.g., BANK, REVOLUT, ZELLE).
data.data[].name STRING Standardized public display title of the payment system.
data.data[].fields ARRAY Array defining input requirements and labels for configuring this payment channel.
success BOOLEAN Indicates overall request execution result.
04

How It Works

Workflow for querying supported global payment methods.

01 Set Headers Pass clientType header in HTTP request.
02 Send POST Request Call /sapi/v1/c2c/paymentMethod/listAll endpoint.
03 Parse Schema Fields Extract supported channels and their required input fields.
04 Sync UI Selectors Dynamically render available payment rails in merchant dashboards.

Common Use Cases

Dynamic Form Generation

Build automated user interfaces that dynamically render input fields according to Binance payment specifications.

Catalog Synchronization

Cache the global catalog locally to cross-reference payment identifiers with internal banking gateways.

Regional Expansion

Discover newly listed local banks and mobile money methods supported for international fiat pairs.



💬
Telegram WhatsApp