North Metric

    authentication_required: ask them to confirm.

    It isn’t a failure: one confirmation link, sent once, clears it for most customers within hours.

    authentication_requiredDECLINE CODE · AUTHENTICATE
    RECOVERYHIGHRETRYAfter 3-D SecureCUSTOMER ACTIONConfirm payment

    What does authentication_required mean in Stripe?

    It means the customer’s bank wants them to confirm the payment with 3-D Secure before it can go through.

    What happens next

    The same decline, handled two ways: a fixed retry ladder, and Stripe Smart Retries with North Metric following up once they end. North Metric never retries a card; its part in failed payment recovery starts when Stripe stops.

    THE NEXT 14 DAYS · EXAMPLE✕FAILED RETRYACTIONPAID
    Fixed retry ladder · day 1, 3, 5, 7Fails ×4
    M✕
    T
    W✕
    T
    F✕
    S
    S✕
    M
    T
    W
    T
    F
    S
    S
    Four attempts that can’t show a 3-D Secure prompt. Without the customer confirming, the bank declines every one.
    Stripe + North MetricPaid · next day
    M
    T
    W
    T
    F
    S
    S
    M
    T
    W
    T
    F
    S
    S
    North Metric drafts a note with a link to confirm the payment, at once if Stripe can’t retry it, or when its retries end. You approve it first.

    What it means

    It is common in the EU and UK under Strong Customer Authentication rules, especially on the first renewal after signup. Stripe returns it as a decline_code inside a card_error, so your integration sees the charge fail and the reason sits in this field.

    {
  "error": {
    "type": "card_error",
    "code": "card_declined",
    "decline_code": "authentication_required",
    "message": "Your card was declined."
  }
}

    Why it happens

    •The bank requires 3-D Secure for this payment, and an off-session renewal can’t show the prompt.•Strong Customer Authentication (SCA) rules apply to the card, as they do across the EU and UK.•The card was saved without authentication being set up for future off-session charges.

    What to do

    01Send the confirmation linkStripe’s hosted page runs the 3-D Secure challenge for you.
    02Remind once after 24 hoursBanks often send their own prompt too; one reminder is enough.
    03Charge on successListen for payment_intent.succeeded, then close the invoice.
    See which customers with a failed payment are at risk, in your own Stripe.Actions off until you turn them onGet your free churn report →

    What to tell the customer

    Explain that their bank asked for a quick confirmation; it’s a security step, not a problem.

    From: Maya at AcmeSubject: Your bank needs a quick confirmation
    Hi Sam, Your bank asked to confirm this month’s Acme payment; it’s a standard security check. It takes a few seconds here. Nothing else changes. Maya
    SEND AT ONCE IF STRIPE CAN’T RETRY, OR WHEN ITS RETRIES END

    What not to do

    ✕Retry without sending the confirmation link.✕Call it a “failed payment”; it isn’t.✕Send the prompt at night when banks time out.
    01RELATED CODES

    Same type,same playbook.

    Codes Stripe returns for the same underlying reason. Each one opens its own guide.

    approve_with_idThe issuer couldn’t authorize without more checksHIGHOpen code →insufficient_fundsThe card is valid but the balance was too lowHIGHOpen code →card_velocity_exceededThe card hit its spending or transaction limitHIGHOpen code →
    All decline codes →
    02FAQ

    Questions aboutthis decline.

    Short answers. The full list of codes is one click away.

    Hard. Stripe won’t retry it until the customer acts (confirm payment).

    AFTER STRIPE’S RETRIES

    Know who’s at riskafter a decline.

    Actions off until you turn them on