Skip to main content
Gruv.ai logo
Payment recovery

Know the next step after a failed payment

Connect the unpaid invoice to its recovery schedule. Follow collection attempts, customer actions and the outcome your billing team needs to act on.

Discuss payment recoveryFollow a recovery schedule

Studio · SUB-318

INV-318-09 · Still unpaid

USD 100

1 Sep–1 Oct 2026

Initial payment attempt
1 Sep · Failed
Configured campaign starts
1 Oct · Mark past due and attempt collection

Follow the schedule and the payment result for this invoice.

Give the unpaid invoice a schedule

September’s USD 100 payment failed on 1 September. This campaign starts from the period-end due date, 1 October, and follows the steps your team configured.

Saved-method collection is set up for this subscription. Later steps run while the invoice remains unpaid; a successful collection ends recovery for this cycle.

What if the payment needs customer action?

A payment that needs customer action can require a payment-method update. Use the configured customer message and follow the next collection result. Follow the payment result before treating the invoice as paid.

INV-318-09 · One configured campaign

  1. 1 Oct

    Mark past due and attempt collection

    The campaign records the subscription as past due and tries the saved method.

  2. 4 Oct

    Retry collection

    If the invoice is still unpaid, make the next configured attempt.

  3. 8 Oct

    Final-notice step

    Prepare the configured final notice if payment remains unresolved.

  4. 15 Oct

    Stop this cycle’s collection

    End this campaign’s collection steps if the invoice is still unpaid.

All dates are in October 2026. Your campaign’s timing and final action are configuration choices.

Know how this recovery attempt ends

The same campaign can finish with a paid cycle or an unresolved invoice. Keep the outcome visible to the team following up.

If payment succeeds · 4 Oct

USD 100 collected

The cycle is marked paid and its recovery ends. No later campaign steps are needed for this invoice.

SUB-318 moves from past due to active after the successful collection.

If still unpaid · 15 Oct

USD 100 remains unresolved

This configured stop action ends collection for the cycle. Keep INV-318-09 with its unpaid amount for the team’s next decision.

Stopping collection does not cancel the subscription or mark the invoice paid.

Does stopping collection also stop future billing?

No. This action ends the current cycle’s collection campaign. Subscription cancellation, expiry and future billing are separate lifecycle decisions. Review those settings and any connected product-access rules separately.

More in Subscriptions

Explore more in Subscriptions

Recurring billing

Keep the subscription period, invoice and collection result connected.

Subscription pricing

Review the target price and effective timing before a plan change.

Subscription Lifecycle

Review subscription state changes separately from a cycle’s collection outcome.

Frequently Asked Questions

Does every campaign use these dates and actions?+
No. This is one configured schedule anchored to the cycle’s due date. Agree the attempt offsets, notification steps and terminal action for your campaign before rollout.
What does past due mean for product access?+
Past due is a subscription billing state. Product access follows your connected entitlement rules; confirm those separately from payment recovery. Successful collection restores an active state when the subscription was past due.
What needs to be configured before retries run?+
Set the campaign steps and confirm autopay, customer and saved payment-method details. Connect the customer notification path and agree how your team handles invoices that remain unpaid.

Make payment recovery clear

Tell us how you handle failed renewals today. We’ll work through the campaign timing, customer actions and unresolved-payment handoff together.

Discuss payment recovery