What gets in the way
Subscribers who meant to stay, cancelled by a failed payment
01
Expired and reissued cards
Cards expire, get lost or are reissued between renewals. The stored details go stale and the charge fails on a subscriber who never chose to leave.
02
One acquirer, no second chance
A soft decline at your only acquirer goes straight to dunning, even when another acquirer could have taken the same payment.
03
Fixed retry schedules that ignore the decline
Retrying on the same days whatever the reason for the failure spends attempts on payments that needed a different moment or a different route.
How Altruon fits
Four layers between a decline and a cancellation
The renewal, step by step
Every chance a renewal gets before it ends
Your billing engine raises the invoice. Altruon works through each stage and writes the result back to that invoice.
01 · Before renewal
Updated before renewal
The account updater refreshes the stored card. The token and the subscription stay the same.
02 · Renewal day
Charged with network token
The renewal passes the network token, which keeps working after the card is reissued.
03 · On a soft decline
Retried on a second acquirer
The same card is retried elsewhere with the same network transaction id.
04 · In dunning
Retried on a smart schedule
A basic schedule in days you set, or AI-timed retries. Each retry is claimed once and never charges twice.
05 · After the last retry
Your end action
Cancel the subscription on your billing engine, flag the invoice as dunning exhausted, or stop retrying.
Align your billing engine's dunning emails and cancellation rules with Altruon's schedule. Every stage is visible on the invoice and sent to your webhooks.

