Subscription auth is an infrastructure problem.

Why subscription auth looks different

Recurring uses stored credentials. Cards expire, get reissued, hit velocity limits, or return soft (temporary) vs hard (do not keep retrying) declines. Involuntary churn is often an infrastructure and billing-ops problem: updater coverage, retry policy, dunning, descriptors, and network reattempt guidance.

Soft vs hard declines and retries

Soft declines may succeed later with intelligent spacing. Hard declines should stop retrying the same credentials and move to updater paths or customer outreach. Blind retry storms waste money, can trigger excessive-reattempt fees, and can worsen issuer trust. Build taxonomy first; then schedule. Follow network guidance.

Account Updater

Network updater programs (via acquirer or gateway) refresh stored numbers and expiry when issuers reissue cards. Subscription merchants should confirm enrollment and how fast updates apply before the next cycle. Updater fixes a class of declines raw retries cannot. Milestone does not run updater programs.

Levers we work

Decline taxonomy, updater / token hygiene, retry and dunning within network rules, descriptors and customer communication, corridor and rail fit for recurring traffic, and commercial terms that assume subscription risk. We do not promise a fixed approval-rate lift.

What we do / What we don't

Do: Diagnose recurring failure modes; improve and prove recovery on live volume.

Don't: Publish guaranteed AR or run network updater programs ourselves.