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
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 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
â””reason
string
Risk control reason
â””gmtCreate
timestamp
Record creation time
Response Example
Last updated