Fraud and risk
Risk controls that protect your MIDs and your margins
Stop bad transactions before they reach a processor. Block rules, velocity limits, a targeted 3DS strategy and chargeback ratio monitoring keep your accounts in good standing.
Block before you charge
Reject transactions by email, IP, BIN or country before they reach a MID.
Velocity limits
Cap attempts per card, email or IP to stop card testing and abuse.
Ratio monitoring
Watch chargeback ratios per MID and act before thresholds are reached.
Block rules
Maintain block lists and rules that stop transactions before authorisation. A blocked attempt never reaches your processor, so it cannot become a decline or a dispute on your account.
- Email and email domain
- IP address and IP country
- BIN and BIN range
- Billing or shipping country
Velocity limits
Card testing and repeat abuse show up as many attempts in a short time. Velocity rules limit how often the same card, email or IP can attempt a payment within a window, which protects both your approval rate and your MIDs.
3DS where it helps
Applying 3DS to every transaction can hurt conversion. LumniPay lets you trigger it selectively, for example on higher amounts, specific countries or riskier BINs, where the extra authentication is worth it.
Chargeback alerts and ratio monitoring
Track disputes and chargeback ratios per MID over time. When an account trends upward, you can reduce its share of volume with load balancing, tighten rules or act on alerts before a threshold becomes a problem.
- Chargeback ratio per MID
- Dispute reasons and trends
- Alerts when a ratio approaches the limit you set
Approval rate
87.4%
+3.1 pts
Recovered by cascade
$18,240
this month
Chargeback ratio
0.41%
all MIDs
Active subscriptions
6,912
+4.2%
Approved volume by day
MID health
Cap $212k / $250k
Cap $96k / $150k
Cap $140k / $150k
Illustrative interface and sample data.
How it works
Risk controls, step by step.
- Step 01
Screen
Each transaction is checked against block rules and velocity limits.
- Step 02
Authenticate
3DS is applied when your rules say it is worth it.
- Step 03
Route
Clean transactions continue to your routing and cascade logic.
- Step 04
Monitor
Disputes and ratios are tracked per MID, with alerts when they rise.
FAQ
Questions about risk controls.
Do blocked transactions count against my MID?
No. Blocked attempts are stopped before they reach a processor, so they do not appear as declines or disputes on your accounts.
Can I apply 3DS only to some transactions?
Yes. You can trigger 3DS based on amount, country, BIN or other conditions instead of applying it everywhere.
How does LumniPay help with chargeback ratios?
It monitors ratios per MID and lets you spread volume across accounts so disputes do not concentrate on one. Block rules and velocity limits also reduce fraudulent orders that often lead to disputes.
Can I stop card testing?
Velocity limits on card, email and IP are designed for this. They cap repeated attempts within a short window.
Does LumniPay replace my processor's fraud tools?
No. LumniPay adds a layer of rules before transactions reach your processing partners. It works alongside the controls they already apply.