Risk Control webhook

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

ParameterTypeDescription
eventTypestringWebhook Event Type
eventIdstringWebhook Event ID
webhookSubscribeIdstringWebhook subscription ID
+dataobject
└userIdstringUser ID
└cardIdsListCard IDs controlled by risk
└numbersListCard numbers controlled by risk
└typestringFREEZE_CARD
FREEZE_ACCOUNT
└riskControlReasonTypestringHIGH REFUSE RATE: High refusal rate
CONSECUTIVE DECLINED DUE TO ACCOUNT NOT ENOUGH: Continuous refusal to pay due to insufficient balance
ZERO PENDING MANY TIMES: Multiple 0Pending
CARD
OverDRAW: Card overdraft
ACCOUNT OverDRAW: Account overdraft
MANY
FREEZE CARD COUNT: Too many frozen cards
└reasonstringRisk control reason
└gmtCreatetimestampRecord 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"
        }
}