Start with failed subscription payment attempts, then check the current status and balance of the original invoice. Use eligible saved cards to retry unpaid invoices, and confirm the outcome against the invoice and payment records.
Start with a date range you can explain
Decide whether you are asking which payments failed during a period or which invoices remain unpaid today. These are different views. An invoice can fail in one month and be paid in another; an old failure can remain visible even after its debt is resolved.
Use one timezone consistently. Rebound’s collection filters use New York calendar dates, and the app starts with the last 15 days including today. The list loads automatically, so changing the dates is optional.
Read failures without multiplying the debt
Review the customer, the invoice reference, the amount still due, and the saved cards. Multiple failed attempts can belong to the same invoice. Group those attempts before calculating the total you intend to collect.
The reason attached to a failed attempt tells you what happened at that moment. The invoice’s current state tells you whether there is still a balance to collect. Keep both pieces of information visible.
Check which invoice states are payable
Do not treat every failed payment record as permission to collect. Some invoices are already paid or voided. Others may have an unresolved payment outcome that needs attention before another attempt.
A written-off invoice is not the same as a voided invoice. Stripe documents a payment transition for uncollectible invoices; voided invoices are cancelled. Rebound includes written-off subscription invoices in manual recovery when otherwise eligible, while keeping voided invoices excluded. See our invoice status guide.
Run recovery and verify the result
In Rebound, review the loaded list and click Start recovery to begin real collection attempts. Each eligible saved physical card is tried at most once per invoice in that run. The tool stops trying that invoice when it is paid, when the eligible cards are exhausted, or when an uncertain outcome needs review.
After a run, inspect the invoice-level result and card-attempt history. A successful outcome should link back to the original Stripe invoice. Keep a record of the amount collected, which invoice was paid, and when the result was confirmed.
Coordinate this process with any retry policy you already run in Stripe or another tool. Looking at a failure list should never itself trigger a charge.