Skip to content

Subscription Billing | Dunning & Recovery

Recover failed payments before they churn.

Smart retries on a schedule you control, dunning emails, and a hosted page for customers to update their card. Past-due subscriptions move through grace, retry and pause states automatically. You see recovered revenue and what is still at risk.

Dunning Management

What the system does

Capability, input, output.

  • Smart retries

    Input
    Failed charge, configurable retry schedule
    Output
    Retry attempts spaced to maximise recovery
  • Dunning emails

    Input
    Past-due subscription, email template per step
    Output
    Timed notifications sent without manual work
  • Hosted card update

    Input
    Customer link from a dunning email
    Output
    Updated payment method stored for the next retry
  • Subscription states

    Input
    Charge failure event
    Output
    Subscription moves through past-due, grace, retry and paused automatically
  • Recovery visibility

    Input
    Dunning config, payment attempts
    Output
    Recovered revenue and at-risk revenue in one view
  • Dunning config

    Input
    Retry intervals, grace period, final action
    Output
    A sequence applied consistently across all past-due subscriptions

Standards + connections

Recovery wired to billing, payments and the books.

Dunning is not a standalone drip sequence. Each retry draws on a stored payment method, each successful recovery posts a receipt to receivables, and the subscription status the billing engine sees is always current.

Regulations we work within

  • PCI DSS

    Payment methods stored and retried through a compliant vault; card data never touches application code.

  • Audit trail

    Every retry attempt, email sent and state change is logged with time and outcome, end to end.

  • IFRS 15 / Ind-AS 115

    Revenue suspended on past-due subscriptions is recognised only when payment clears, keeping the ledger accurate.

Connects to

  • Payments Stored methods, retry attempts and receipts
  • Accounts Receivable Receipts posted on recovery, balances updated
  • Subscription Management Subscription state kept in sync across the sequence
  • Accounting Deferred revenue resolved when payment clears

Dunning Management FAQ

What buyers ask.

What happens the moment a charge fails?

The subscription moves to past-due and the dunning sequence starts. The engine schedules the first retry according to your config, queues the first dunning email, and the customer receives a link to update their card. Your team sees the subscription flagged in the at-risk view without any manual step.

Can we set our own retry schedule and grace period?

Yes. The dunning config lets you define the number of retry attempts, the interval between them, and a grace period before the subscription pauses or cancels. Different configs can apply to different plans or customer segments if your recovery strategy varies.

How does the hosted card update page work?

Each dunning email contains a tokenised link to a hosted page where the customer enters new card details. The stored payment method updates, and the next scheduled retry picks it up automatically. No code changes are needed on your side to support the flow.

What does the recovered revenue view show?

The recovery dashboard shows subscriptions by dunning state, the amount recovered in the current period versus the same period prior, and the value still at risk by retry step. Each row links to the subscription and its payment attempt history so your team can act on outliers.

See a failed payment move through recovery automatically.

Trigger a test charge failure, watch the subscription enter past-due, and follow the retry sequence, the dunning email and the recovery receipt through to the books.