Recurly 3D Secure (SCA) Declines on Renewals

Share
Workaround available Web (Recurly Admin Console), API Updated November 13, 2026Based on 3 user reportsHow we research

Quick answer

Renewals can fail when the issuing bank demands 3D Secure re-authentication. Use Recurly's 3DS2 dunning flow so the customer can authenticate.

Most likely fix: Enable 3DS2 dunning

How to fix it

Try these in order — the most common fix is first.

  1. 1. Enable 3DS2 dunning

    1. Follow Recurly's dunning configuration for 3DS2 declines
    2. Keep the 3DS2 Decline email template active
    Did this fix it?
  2. 2. Collect cards through your own front end

    1. Integrate Recurly.js with 3DS2 so authentication happens at signup
    Did this fix it?
  3. 3. Ask the customer to authenticate on the hosted page

    1. Send the hosted invoice or account link
    2. Complete the bank challenge, then retry the invoice
    Did this fix it?

Symptoms

Renewal invoice goes past due, customer gets a 3DS2 Decline email.

Why it happens

  • Issuer enforces SCA even on merchant-initiated retries
  • Card added only via API or Admin UI without 3DS
  • Dashboard-created payments do not trigger the 3DS redirect

This guide also covers

  • recurly 3d secure
  • recurly sca decline
  • recurly 3ds2 decline email

Still not working?

If Recurly keeps failing, you're not alone. See every Recurly problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other Recurly errors

All 10 Recurly errors and fixes →