Your Stripe connection
Create a Rebound account, open Stripe & settings in the account menu, and configure your Stripe API key. Treat that key as a sensitive credential. Use a dedicated key with only the permissions needed for your recovery workflow, and revoke it in Stripe when it is no longer needed.
Rebound needs to read customer, invoice, subscription, payment, and saved-card information and attempt payment on the relevant invoices. Review the Stripe restricted API key documentation before creating a key.
Reading and charging are separate actions
Opening Collections, scanning a date range, and opening invoice details read data. They do not start charges. Clicking Start recovery—or explicitly resuming an interrupted collection run—starts collection attempts.
Defined limits for each run
A run contains a specific list of invoices. Rebound tries each eligible distinct saved card once per invoice in that run. It stops on successful payment or when the eligible cards are exhausted. Starting another run is a separate action.
Uncertain results need review
A connection interruption is not proof that a charge failed. Rebound holds uncertain payment outcomes for review rather than blindly moving on to another charge. Check the run status and Stripe invoice before deciding what to do next.
Keep the evidence
Run results include invoice-level states and card-attempt outcomes. Use the original Stripe invoice reference to verify a collection. Rebound’s Insights view also provides a monthly drill-down of recorded recoveries.