Blocked list
How to monitor and manage transactions automatically declined by your Protect block rules.
Overview
The Blocked list shows transactions that were automatically declined because they matched one of your block rules. These transactions were never completed — no funds were captured from the customer.
This view helps you monitor what your rules are catching, identify false positives, and adjust your fraud prevention strategy over time.
How transactions get blocked
A transaction is blocked when it matches the conditions of an active block rule. Examples:
block if risk_score_gte: 800 OR card_country_id: ['NG']
block if ip_address: '123.45.67.89'
block if billing_email: '[email protected]'Rules are evaluated in order from lowest to highest order number. The first matching rule determines the outcome — if a block rule matches, the transaction is declined immediately and does not proceed to any further rules.
Monitoring for false positives
If legitimate customers are appearing in your blocked list, your rules may be too aggressive. Signs to watch for:
- A high volume of blocked transactions from a country where you have genuine customers
- Blocked transactions with low risk scores that were caught by a non-score-based rule
- Customer complaints about declined payments
When you identify a false positive pattern, consider narrowing the block rule conditions (e.g., combining with a risk score threshold using AND) or switching to a review rule while you investigate further.
Best practices
- Review the blocked list after any rule change to verify the rule is behaving as intended.
- Use AND logic to combine conditions when you want to reduce false positives.
- Start with review rules before escalating to block rules for new fraud patterns you haven't fully validated yet.
Updated 15 days ago