How To: Send Payer Events for Chargeback Protection

Why Sharing Payer Events Matters

Merchants can improve the chargeback protection model’s decisions by sending major events that payers take throughout the lifespan of the customer on your app. Anytime the customer makes a significant action on your app that allows you to collect information that identifies them, you may call our /events endpoints to share data with the chargeback model.

Implementing this endpoint is a critical step for any customer—especially those with:

• High transaction volumes (>=$500K)
• Those aiming to improve the accuracy of chargeback protection decisions

How It Helps with Chargeback Approval Rates

Our chargeback protection engine learns from both successful and failed user actions. When you provide lifecycle data like logins, verification steps, or sign-in failures, our models can:

• Increase approval rates by identifying legitimate users more accurately (reducing false positives)
• Prevent fraud by recognizing suspicious or automated behavior earlier (reducing false negatives)
• Reduce your risk profile with card networks, minimizing the chance of being flagged for excessive chargebacks

Understanding Which Events to Pass

We’ve included some examples below to help your team determine when and how to trigger events. As a rule of thumb: if your system has enough confidence to identify the user or verify intent, it’s a good time to share an event. Engineering teams should ensure this data is sent automatically as part of your user workflows. This requires minimal engineering effort but can yield substantial returns in both revenue and risk mitigation.

Example Requests for Events

1
curl --request POST \
2
     --url https://api-sandbox.coinflow.cash/api/events \
3
     --header 'Authorization: YOUR_API_KEY' \
4
     --header 'content-type: application/json' \
5
     --data '
6
{
7
  "eventType": "SignUp",
8
  "customerId": "user-123-abc",
9
  "country": "US",
10
  "username": "therock72",
11
  "email": "dwaynejohnson@gmail.com",
12
  "firstName": "Dwayne",
13
  "lastName": "Johnson"
14
}
15
'

1
curl --request POST \
2
     --url https://api-sandbox.coinflow.cash/api/events \
3
     --header 'Authorization: YOU_API_KEY' \
4
     --header 'content-type: application/json' \
5
     --data '
6
{
7
  "eventType": "SignIn",
8
  "customerId": "user-123-abc",
9
  "country": "US",
10
  "email": "dwaynejohnson@gmail.com"
11
}
12
'

1
curl --request POST \
2
     --url https://api-sandbox.coinflow.cash/api/events \
3
     --header 'Authorization: YOUR_API_KEY' \
4
     --header 'content-type: application/json' \
5
     --data '
6
{
7
  "eventType": "SignInFailure",
8
  "customerId": "user-123-abc",
9
  "country": "US",
10
  "email": "dwaynejohnson@gmail.com",
11
  "failureReason": "Password Failed"
12
}
13
'

1
curl --request POST \
2
     --url https://api-sandbox.coinflow.cash/api/events \
3
     --header 'Authorization: YOUR_API_KEY' \
4
     --header 'content-type: application/json' \
5
     --data '
6
{
7
  "eventType": "BuyerChallenge",
8
  "type": "thirdPartyKyc",
9
  "status": "successfullyFulfilled",
10
  "customerId": "user-123-abc",
11
  "country": "US",
12
  "email": "dwaynejohnson@gmail.com"
13
}
14
'