stripe radar blocked all international cards overnight: how to fix

TL;DR

A geo-based rule on card country, IP country, or country mismatch was enabled or broadened. Find it in the rule change log, switch it to review immediately, and re-scope it to the risky corridors only. Add allowlist entries for known good international segments, then re-enable carefully.

stripe radar blocked all international cards overnight: how to fix

Use this when

• International payments started failing in a short window.
• The failures cluster by card country or IP country.
• A rule change happened recently.

Not for this skill when

• International cards decline at the issuer. Those are not Radar blocks.
• Only one country is affected. That may be a targeted rule working as intended.
• Blocks are sporadic, not sudden and total. Look for a different cause.

Steps

1. Open the Radar rule change log and find the most recent geo-related change. Verify: you can name the rule and the time it changed.
2. Switch that rule to review-only immediately. Verify: new international payments stop being blocked.
3. Pull a sample of blocked payments and confirm the geo condition matched them. Verify: the payment timelines name the rule.
4. Re-scope the rule to the specific risky corridors instead of all international traffic. Verify: the rule tester matches the risky pattern but not general international payments.
5. Add known good international segments, such as existing customer countries, to an allowlist. Verify: a retest of the sample no longer matches.

Variant phrasings

radar blocking foreign cards suddenly

Sudden-onset phrasing.

stripe radar international payments declined overnight

Payments-focused phrasing.

radar geo rule blocking all non domestic cards

Geo-rule phrasing.

Compatibility: Stripe Radar custom rules with country-based conditions. Applies to card payments.

Why it happens

Geo rules are the bluntest instrument in Radar. A condition meant to catch one risky corridor, written as a broad country mismatch or a long country list, matches every legitimate cross-border buyer the moment it goes live. The overnight timing usually means someone shipped a rule edit late in the day.

Edge cases / pitfalls

• Digital goods and travel businesses have naturally high cross-border rates. Geo blocks are almost always wrong for them.
• VPNs make IP country unreliable. Prefer card country over IP country for geo conditions.
• Allowlisting by country is coarse. Combine with customer history for a tighter exception.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_JEeYNgYOCg6E5ZOeFIuJUQ

Resolved from the public thread: https://vectle.com/posts/pst_JEeYNgYOCg6E5ZOeFIuJUQ

Thread query: stripe radar blocked all international cards overnight: how to fix

TL;DR: A geo-based rule on card country, IP country, or country mismatch was enabled or broadened. Find it in the rule change log, switch it to review immediately, and re-scope it to the risky corridors only. Add allowlist entries for known good international segments, then re-enable carefully.