Overview
TXCloud uses a unified risk scoring system across all APIs. Risk scores help you make informed decisions about users, transactions, and businesses.Score Scale
All TXCloud risk scores use a 0-1000 scale:| Score Range | Risk Level | Description |
|---|---|---|
| 0-200 | 🟢 Very Low | Highly trusted, minimal risk |
| 201-400 | 🟢 Low | Normal, proceed with confidence |
| 401-600 | 🟡 Medium | Some concerns, consider review |
| 601-800 | 🟠 High | Significant risk, additional verification |
| 801-1000 | 🔴 Critical | Very high risk, likely block |
Higher scores = Higher risk. A score of 0 is the safest, 1000 is the riskiest.
Risk Score by API
Identity Verification
Transaction Scoring
Credit Assessment
Score Components
Risk scores are calculated from multiple signals:Identity Signals
| Signal | Impact | Description |
|---|---|---|
| Document fraud | +300-500 | Tampering detected |
| Face mismatch | +200-400 | Selfie doesn’t match document |
| Liveness failed | +300-500 | Not a live person |
| Data inconsistency | +100-200 | Extracted data conflicts |
Device Signals
| Signal | Impact | Description |
|---|---|---|
| Known device | -50 | Previously verified device |
| New device | +50 | First time seeing device |
| VPN detected | +100-200 | VPN connection active |
| Emulator | +300 | Running in emulator |
| Rooted/jailbroken | +200 | Modified device |
Behavioral Signals
| Signal | Impact | Description |
|---|---|---|
| Unusual amount | +100-200 | Outside normal range |
| Unusual time | +50-100 | Late night transaction |
| Velocity exceeded | +200-400 | Too many attempts |
| New recipient | +50 | First transfer to recipient |
Using Risk Scores
Decision Thresholds
Configure thresholds for automated decisions:Custom Rules
Create rules that adjust scores based on your business logic:Score Explanations
Always provide context for your decisions:Best Practices
Start Conservative, Adjust Over Time
Start Conservative, Adjust Over Time
Begin with strict thresholds and loosen as you gather data:
- Week 1-2: Manual review at score > 400
- Week 3-4: Analyze false positive rate
- Week 5+: Adjust thresholds based on data
Combine Scores with Context
Combine Scores with Context
Don’t rely on score alone — consider:
- User history
- Transaction type
- Business context
- Time sensitivity
Log Everything
Log Everything
Store risk scores and factors for:
- Compliance audits
- Model improvement
- Dispute resolution
Monitor Score Distribution
Monitor Score Distribution
Track your score distribution over time:
- Sudden spikes may indicate attacks
- Gradual shifts may indicate model drift
Analytics
Track your risk metrics in the dashboard:View Analytics Dashboard
Access detailed risk analytics in your dashboard