Improving Chargeback Protection Acceptance Rates
📊 Maximizing Chargeback Protection Accuracy
To get the most out of Approvely's chargeback protection, it’s critical to pass data that clearly ties each transaction to an individual user. Our system relies on identity signals like:
- Name
- Device behavior
- Prior activity
These reduce chargeback risk and boost approval rates.
Use this data template to ensure you're passing the right fields.
❌ 999 Error Code Explained
A 999 error means Approvely's chargeback provider reviewed the session data but declined the transaction. This is typically caused by:
- Missing/low-quality data
- Early-stage integration with insufficient behavioral signals
Use the Events API to send registration, login, or KYC events to build user profiles before the first transaction.
💡 Why Data Matters
Our fraud models analyze:
- Typical transaction sizes
- User behavior patterns
- Card & identity history
To optimize acceptance rates, provide:
- Historical transaction data
- Past successful customer profiles
Without this, the model defaults to caution, lowering approval rates.
🧠 Best Practices by Customer Type
✅ If You Have Card Transaction History
| Field | Description |
|---|---|
paymentAmount | Total amount |
paymentMethod | "card" |
last4 | Last 4 digits of card |
bin | Bank Identification Number |
pan (optional) | Full card number (if secure) |
firstName | Cardholder’s first name |
lastName | Cardholder’s last name |
email | Email used at time of purchase |
Helps match users to previous payment behavior
✅ If You Have User & Payment Data (No Card Info)
| Field | Description |
|---|---|
firstName | User’s first name |
lastName | User’s last name |
email | User’s email address |
paymentAmount | Transaction amount |
paymentMethod | e.g., "wallet" |
Builds identity-based behavioral models
✅ If You Have No Transaction History
| Field | Description |
|---|---|
firstName | Likely transactor’s first name |
lastName | Last name |
email | Email address |
Start building profiles early. Share:
- Returning buyer lists
- Whitelisted users
- Marketing/newsletter recipient lists
📋 Summary of What Data to Send
| Your Situation | Required Data Fields |
|---|---|
| Have card transaction history | paymentAmount, paymentMethod, last4, bin, pan (optional), firstName, lastName, email |
| No card, but payment history | paymentAmount, paymentMethod, firstName, lastName, email |
| No transaction history | firstName, lastName, email |
Reference the onboarding data template to configure risk models.
Updated 4 months ago