The signal in Stripe

The charge fails with authentication_required. The bank is not refusing the payment; it is demanding that the customer approve it, usually with a tap in their banking app. Common for European cards under Strong Customer Authentication rules, and increasingly common elsewhere as issuers tighten fraud controls.

Why it happens

Off-session subscription charges sometimes trip an issuer's authentication requirement: a new card, a larger-than-usual amount, a risk model having a cautious day. The customer did nothing wrong and often never learns the approval request existed, because it expires quietly inside their banking app.

What happens if you do nothing

The renewal stays unpaid while everyone assumes someone else acted. Retrying without authentication produces the same decline. This failure mode punishes silence: the single thing that recovers it is getting the customer to complete one approval, which requires telling them clearly.

The play, step by step

Chaser, the Stripe-native failed-payment recovery tool, sends the customer a direct link to complete the authentication, explains in one sentence that their bank requested it, and sets the retry to run immediately after approval. If the approval does not arrive within the snooze window, the case escalates with full context so a human can decide between a second nudge and a different payment method.

The email that works

Name the bank as the reason. "Your bank asked for a quick approval on your renewal" removes all suspicion from the merchant and puts the request where it belongs. One link, one tap, done.