FAQ

Frequently asked questions

Everything founders, engineering, and finance teams ask before connecting Chaser to a production Stripe account.

How does Chaser fit into our existing finance stack?
Chaser plays nicely with the tools you already use. We push real-time webhooks for every recovery event so you can sync data into your data warehouse or anything you can hit via Zapier or API. Native HubSpot, Salesforce, QuickBooks and NetSuite connectors are rolling out, with Pro customers getting priority access. Stripe stays your source of truth — Chaser just adds recovery context on top.
How do we reconcile recovered payments with our accounting system?
Every outcome is written back to Stripe where it applies — paid out-of-band, invoice resend, cancellation — and logged with operator and timestamp. Today, outcomes flow to your accounting system via webhooks and Zapier; native HubSpot, Salesforce, QuickBooks and NetSuite connectors are rolling out, with Pro customers getting priority access. You can also export the full history as CSV or JSON.
Is Chaser secure enough for our production Stripe account?
Yes. We connect through Stripe's official OAuth with restricted, read-only scopes you approve on Stripe's own consent screen. We can't move money, change prices, or see card numbers. Your data is isolated per workspace, hosted on SOC 2 Type II infrastructure, and encrypted in transit and at rest.
How does Chaser connect to Stripe?
Through Stripe's official OAuth flow (one click), or with a restricted key you create if you prefer. We never ask for your secret key. The connection is scoped to exactly what we need to recover failed payments — nothing more.
Does Chaser work with WooCommerce, Chargebee, or my custom checkout?
Yes, as long as your billing runs through Stripe. Chaser connects to Stripe itself, so anything that uses Stripe as the payment processor is already compatible: Stripe Billing, WooCommerce with the Stripe gateway, Chargebee with Stripe as the processor, and custom carts built on Stripe. There is no plugin to install and no per-platform setup. One Stripe connection covers all of it.
Does Chaser ever see customer card details?
No. Update pages are hosted by Chaser and fully branded as yours, but the card fields themselves are served and tokenized by Stripe — details go straight to Stripe's vault and never touch Chaser's servers. We're PCI-compliant because we never handle that data.
How do you make sure recovery data stays in sync with Stripe?
Every Stripe event is processed exactly once, so nothing gets double-counted. When your team marks a payment as recovered outside Stripe (say a customer paid by bank transfer), Chaser updates Stripe at the same time so your records always match.
Can we import our historical Stripe data?
Yes. When you connect Stripe, we automatically pull in the last 30 days so you have context from day one. You can also upload a CSV of older failed payments from the Customers screen if you're migrating from another tool or want a deeper history.
What happens the moment we connect Stripe?
Nothing goes out to your customers. Safe Mode runs a 90-day historical diagnostic of your ledger and shows exactly what would have been recovered. No emails are sent, no retries run, nothing in Stripe changes until you switch recovery on.
What permissions does Chaser actually need in Stripe?
Restricted, read-only OAuth scopes to start — visible on Stripe's consent screen before you grant anything. Write access (for retries and invoice actions) is a separate, explicit upgrade you approve later. You can revoke access instantly from your Stripe dashboard at any time.