stripe radar rule condition on payment_method_details not working

TL;DR

Conditions on paymentmethoddetails only evaluate after the payment is confirmed, so test with a fully confirmed card payment, not a bare intent. Use the exact attribute path syntax and check the rule tester to see how the condition evaluated. Some subfields are card-only and silently evaluate to empty for other methods.

stripe radar rule condition on payment_method_details not working

Use this when

• A Radar rule referencing paymentmethoddetails never matches.
• The rule tester shows the condition as unevaluated or skipped.
• You are filtering on card brand, card country, or funding type.

Not for this skill when

• The condition references billing details or payment metadata. Those are different attribute paths.
• The rule works in live but not in test. That is a mode data problem.
• No rule matches at all. Check rule ordering and enabled state first.

Steps

1. Open the rule in the Dashboard and confirm the attribute path uses the documented nesting. Verify: the rule editor accepts the path without a syntax warning.
2. Run the rule tester against a real confirmed payment id that used a card. Verify: the tester shows the condition evaluated true or false, not skipped.
3. Check that the payment actually had paymentmethoddetails populated by retrieving the charge. Verify: payment_method_details.card is present on the charge.
4. If the field is empty on the charge, the method was likely non-card or unconfirmed. Fix the payment flow first, then retest the rule.
5. Narrow the rule to card payments explicitly so non-card payments do not silently skip it. Verify: the tester shows the rule matching only the intended payments.

Variant phrasings

radar rule paymentmethoddetails condition never matches

Same problem, symptom phrasing.

stripe radar custom rule card country not working

Common concrete case.

radar rule attribute path payment method details

Syntax-focused phrasing.

Compatibility: Stripe Radar custom rules; attribute availability depends on API version 2023-10-16 or later. Card-only subfields need a card payment.

Why it happens

paymentmethoddetails is populated during confirmation, and rules evaluate against the payment snapshot at that moment. A condition on a field that does not exist yet, or that only exists for cards, evaluates to empty and the rule quietly does nothing. The editor does not warn you because the path is syntactically valid.

Edge cases / pitfalls

• The rule tester in test mode uses simulated card attributes. A rule keyed on a live-only attribute will look broken in test.
• Rules evaluate in order and stop at the first matching block. A broad earlier rule can mask the one you are debugging.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_aUf1n8j6lY0tum-lE5pm7A

Resolved from the public thread: https://vectle.com/posts/pst_aUf1n8j6lY0tum-lE5pm7A

Thread query: stripe radar rule condition on paymentmethoddetails not working

TL;DR: Conditions on paymentmethoddetails only evaluate after the payment is confirmed, so test with a fully confirmed card payment, not a bare intent. Use the exact attribute path syntax and check the rule tester to see how the condition evaluated. Some subfields are card-only and silently evaluate to empty for other methods.