Webhook for Risk Control

Description

Risk control notification webhook configuration and usage:

• Please contact the staff to configure your Webhook Endpoint Url in the backend, which must be HTTPS
• When risk data appears, corresponding transaction messages will be pushed to your Webhook Endpoint Url
• After receiving a Webhook message, if HTTP CODE 200 is returned, it indicates that you have successfully received the Webhook message. Otherwise, we will try again

Parameter

Parameter	Type	Description
eventType	string	Webhook Event Type
eventId	string	Webhook Event ID
webhookSubscribeId	string	Webhook subscription ID
+data	object
└userId	string	User ID
└cardIds	List	Card IDs controlled by risk
└numbers	List	Card numbers controlled by risk
└type	string	FREEZE_CARD FREEZE_ACCOUNT
└riskControlReasonType	string	HIGH_REFUSE_RATE: High chargeback rate ZERO_PENDING_MANY_TIMES: Multiple instances of zero pending RISK_DECLINED: Risk declined CARD_OVERDRAW: Card overdrawn MONTHLY_FEE_PAID_FAIL: Monthly fee payment failure DANGER_TRADE_SCENE: Dangerous trading scene DANGER_ACH_USER: Dangerous user
└reason	string	Risk control reason
└gmtCreate	timestamp	Record creation time

Response Example

{
    "eventType":"RISK_CONTROL",
    "eventId":"ev_xxxxxxxxxxxxxxxxxxxxx",
    "webhookSubscribeId":"wsb_xxxxxxxxxxxxxxxxxxx",
    "data":{
          "userId": "u_123",
          "cardIds": [
            "c_12312"
          ],
          "numbers": [
            "55676612313"
          ],
          "type": "FREEZE_CARD",
          "riskControlReasonType": "HIGH_REFUSE_RATE",
          "reason": "xxxxxxx"
        }
}