Using reason=fraudulent when adding a card via API has what effect?

Using reason=fraudulent when adding a card via API has what effect?

• A. It flags the card as fraudulent for enforcement
• B. It automatically adds previous fraudulent cards
• C. It blocks the card from future payments
• D. It triggers a routine card update

Answer: (B)

When you add a card with reason set to fraudulent, Stripe treats that action as a fraud signal and uses it to update your fraud protection data. In practice, this means Stripe automatically adds previously identified fraudulent cards to your Radar-managed list, so those cards are recognized as fraudulent across future attempts. This helps enforce fraud controls more consistently by building on existing fraud signals. The other options don’t reflect what this parameter does: it doesn’t flag the card for enforcement on its own, it doesn’t automatically block future payments by default, and it doesn’t trigger a routine card update.

When you add a card with reason set to fraudulent, Stripe treats that action as a fraud signal and uses it to update your fraud protection data. In practice, this means Stripe automatically adds previously identified fraudulent cards to your Radar-managed list, so those cards are recognized as fraudulent across future attempts. This helps enforce fraud controls more consistently by building on existing fraud signals.

The other options don’t reflect what this parameter does: it doesn’t flag the card for enforcement on its own, it doesn’t automatically block future payments by default, and it doesn’t trigger a routine card update.