Retrieve dynamic anti-fraud risk warning tips, security notices, and regional compliance banners tailored to a specific peer-to-peer (C2C) order and chat context.
/sapi/v1/c2c/chat/getRiskWarningTips
This endpoint delivers contextual security warnings and anti-scam advisories based on the active trade context.
By submitting the order identifier (orderNo), fiat currency (fiat), and application context (scene), applications receive tailored risk mitigation messages (e.g., warnings regarding third-party payments, chargeback risks, or off-platform communication scams).
Merchant terminals, chat applications, and custom trading desks invoke this endpoint when rendering order chat windows to display real-time safety advisories to operators and traders.
Parameters accepted in Body and HTTP Headers.
| Parameter | In | Type | Required | Description |
|---|---|---|---|---|
clientType |
Header | STRING | Required |
Client Device Type initiating the request (e.g., WEB, APP, WEB_MOBILE).
|
orderNo |
Body | STRING | Required | Unique C2C order number identifier. |
fiat |
Body | STRING | Optional |
Fiat currency symbol associated with the order (e.g., USD, EUR, KES).
|
scene |
Body | STRING | Optional |
Display context or view state (e.g., CHAT, ORDER_DETAIL, RELEASE).
|
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. |
Setting the scene parameter (such as CHAT or RELEASE) allows the risk engine to return targeted warnings—such as reminding sellers to never release crypto based on fake SMS receipts.
Example POST request using cURL to fetch chat risk warning tips.
curl -X POST \
'https://api.binance.com/sapi/v1/c2c/chat/getRiskWarningTips' \
-H 'clientType: WEB' \
-H 'Content-Type: application/json' \
-d '{
"orderNo": "202608161234567890",
"fiat": "USD",
"scene": "CHAT"
}'
Example response returned on successful query execution.
{
"code": "000000",
"message": "success",
"data": {
"showWarning": true,
"warningType": "THIRD_PARTY_PAYMENT",
"title": "Avoid Third-Party Payments",
"content": "Always verify that the bank account name matches the counterparty verified name. Never accept third-party transfers.",
"tipsList": [
"Do not communicate outside Binance P2P chat.",
"Verify real account balance in your banking application before releasing crypto."
]
},
"success": true
}
| Field | Type | Description |
|---|---|---|
code |
STRING |
Standard Binance status code ("000000" indicates success).
|
message |
STRING | Response execution feedback or status message. |
data.showWarning |
BOOLEAN | Indicates whether an active risk banner should be displayed in the UI. |
data.warningType |
STRING |
Categorical risk code identifier (e.g., THIRD_PARTY_PAYMENT, CHARGEBACK_RISK).
|
data.title |
STRING | Headline title for the security warning banner. |
data.content |
STRING | Detailed explanatory body text of the security notice. |
data.tipsList |
ARRAY[STRING] | List of specific operational precautions recommended for this trade. |
success |
BOOLEAN | Indicates overall request execution result. |
Workflow for displaying contextual risk warnings.
Present visual warning banners to operators when counterparties initiate conversations in high-risk fiat pairs.
Display critical verification reminders before enabling coin release confirmation buttons.
Provide fiat-specific regulatory notices dynamically depending on local banking conditions and payment rails.
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 →