Frequently asked questions

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.

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.

Yes. We connect through Stripe's official OAuth with least-privilege scopes you approve on Stripe's own consent screen, and access is revocable from your Stripe dashboard any time. We never see or store card numbers. Your data is isolated per workspace, hosted on SOC 2 Type II certified infrastructure, and encrypted in transit and at rest.

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.

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. PayPal subscription payments are supported in beta: connect PayPal in the Integration Hub and failed payments flow into the same dashboard and dunning sequences as Stripe. Billing that runs entirely outside Stripe and PayPal, on Paddle for example, is not visible to Chaser today.

Yes, in beta. Chaser ingests failed PayPal subscription payments into the same recovery pipeline as your Stripe failures, so they show up in the same dashboard, get the same root-cause classification, and run through the same dunning sequences and reconciliation. You connect with your own PayPal REST API credentials (read-only), and the connection is workspace-scoped and revocable any time. PayPal support is in active beta and Stripe remains our primary, fully-supported processor, so if PayPal is a large share of your revenue, tell us and we'll walk you through where the beta stands.

Yes, included on every paid plan (Micro, Starter, Growth, and Pro). Connect Claude or any MCP client to https://chaser.cash/mcp and your AI tools can query at-risk renewals, the recovery queue, and closed outcomes. Access is read-only, protected by OAuth, scoped to your own workspace, and revocable at any time: a connection cannot send emails, change playbooks, or take any action. The reverse direction, where Chaser draws on your own MCP server to enrich playbooks, is coming next.

Yes, on Growth and Pro. The Closed Outcomes page shows an AI-written 3 to 5 sentence narrative over the period you pick, with stat chips for recovered, lost, and dismissed totals. The numbers come straight from your ledger; the model only sees aggregate counts and amounts, never customer emails, names, or Stripe IDs. Starter sees the same stat chips without the narrative.

A single card at the top of your dashboard that combines two things: today's triage chips (stale Attention Queue items, renewals that newly turned at-risk, and cold accounts), and a one-line recap of last week (recovered amount, recovery rate, week-over-week delta). Each triage chip deep-links into the relevant worklist. It is read-only: it never sends emails, retries charges, or changes playbook state. Refreshes at 06:00 UTC each morning, with the recap line updating on Mondays. Included on every plan, trials included.

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.

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.

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.

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.

Least-privilege OAuth scopes, visible on Stripe's consent screen before you grant anything. The 90-day Safe Mode audit reads your ledger and sends nothing; live recovery uses the same scoped connection to run retries and invoice actions on your behalf. You can revoke access instantly from your Stripe dashboard at any time.

Yes. Chaser sends a signed recovery.resolved webhook to your configured endpoint for every closed outcome: recovered, churned, written off, or dismissed. Payloads are HMAC-SHA256 signed. Failed deliveries retry with exponential backoff for up to 24 hours. Configure your endpoint and send a test event from Integrations > Reconciliation.

If an invoice is way bigger than what the customer normally pays (say 3x their usual bill), Chaser still runs the retries, but sends only one clear, itemized email and flags the account for your team to review. We don't aggressively dun customers on bill-shock invoices — your team makes the call.

No. Chaser has read-only access to your invoices and can't change pricing, line items, or amounts. Every email is checked to confirm the original invoice breakdown and Stripe receipt link are intact before it goes out.

Chaser picks up the failure from Stripe in real time and starts the right recovery sequence for that customer automatically. We also watch for cards that are about to expire in the next 30 days and prompt customers to update them before the payment fails in the first place.

Yes. Chaser sends a trial-ending reminder 7 days before the trial converts and an upcoming-renewal reminder before each subscription cycle, both from your brand with a one-click link to the customer's Stripe billing portal. Because Chaser owns these proactive lifecycle emails natively, you can (and should) mute Stripe's built-in 'reminder 7 days before a trial ends' and 'upcoming renewal' emails in your Stripe dashboard so customers never receive duplicate notices from two different senders.

It's the sequence of retries and emails Chaser runs when a payment fails — smart retry timing, branded emails, and a secure link customers click to update their card. You can assign playbooks per customer or in bulk, and once the automated sequence is done, any unresolved accounts land in your team's inbox for follow-up.

Full control, on every plan. You own the templates, subject lines, branding, send timing, and how often customers can be contacted. Growth and Pro plans add a one-click tone rewriter (founder, corporate, urgent, concierge) so you can adjust voice without rewriting copy.

Smart Retries just retry the card. Chaser also emails the customer with your brand as the sender name (with proper email authentication so messages actually land in the inbox), times retries around when banks are most likely to approve them, and stops everything the second the invoice is paid. The result: more recovered revenue, fewer angry customers.

Not yet — WhatsApp is on the roadmap. Today, Chaser recovers payments through branded email with managed deliverability.

Nothing goes out to your customers. Until you finish onboarding, the workspace runs in a sandbox with sample data so you can explore the product safely. You activate live recovery when you're ready.

No. Chaser handles email authentication for you. All recovery and lifecycle emails go out on Chaser's authenticated sending infrastructure (SPF, DKIM and DMARC are maintained on our side), and in the inbox they appear as 'Your Company Billing <billing@billing.chaser.cash>' with reply-to set to your team's inbox. You do connect a branded subdomain (like billing.yourcompany.com) from settings, but its job is to host the customer payment portal and recovery short-links under your brand and to prove subdomain ownership before live dispatch is unlocked. There are no DKIM or SPF records for you to publish.

Yes. We automatically detect WooCommerce subscription renewals in Stripe and recover those. One-time store purchases are ignored by default so you're not chasing customers for non-recurring orders.

Tag your subscription payments in Stripe with metadata.payment_type = 'recurring' (or include a subscription_id), and Chaser will pick them up. One-off payments are excluded by default.

They work together. Stripe's Account Updater quietly refreshes about 30% of reissued cards through Visa and Mastercard. The other ~70% — cancelled cards, smaller issuers, customers who switched banks — is exactly what Chaser is built to recover, through pre-expiry reminders and post-failure outreach. Run both.

Chaser coordinates the two playbooks for you. The Revenue Protection playbook handles the card-expiry nudge for shorter-cycle customers (like monthly subscribers). The Renewal Reminder playbook handles your quarterly and annual customers, and emails the customer in the weeks before it expires with an inline 'update your card' callout when the card on file won't make it to the renewal date. When the renewal reminder is going to handle the warning, Chaser holds back the card-expiry reminder for that same customer, so they only hear from you once. If you turn renewal reminders off, the card-expiry playbook still covers every customer, including your quarterly and annual ones. If you turn card-expiry off, renewal reminders will still warn your quarterly and annual customers, but your shorter-cycle customers (like monthly) won't get an expiring-card heads-up until you turn it back on. The only case where neither side emails is when you've turned both off. Both playbooks ship off by default; turn them on individually when you're ready.

Yes. The In-App Recovery widget embeds directly in your app and shows a targeted banner or paywall to customers with open failed payments, before they churn. When a customer clicks through, they're taken to a Stripe-hosted card update page. The update is confirmed by Stripe and Chaser marks the payment recovered only after the invoice is settled. To install: rotate your signing secret, add your domain to the allow-list, create a Recovery API key to mint per-user tokens, and embed the script tag. Full setup guide in the docs.

Create a Recovery API key in Integrations > In-App Recovery, then call POST /api/v1/recovery/mint-token from your backend with the customer's ID. Tokens are short-lived (default 1 hour) and HMAC-signed against your workspace signing secret. Alternatively, self-sign tokens server-side using the HMAC recipe in the setup docs. Both produce tokens the widget verifies identically.

Most tools just retry the card on a fixed schedule. Chaser watches what's actually happening — whether the customer opened emails, clicked the update link, or went silent — and surfaces stuck accounts to your team. When you escalate, the AI rewrites the message in a firmer tone, but a human always reviews it before it goes out.

AI drafts the message, but it never sends on its own. Your team reviews, edits, or approves every escalation. We also hard-code the important bits — payment link, unsubscribe footer, your branding — so the AI can't accidentally remove or change them.

No. Chaser is a flat monthly subscription based on your Stripe volume — you keep 100% of every dollar we recover.

If Chaser doesn't recover more than it costs in your first active billing cycle, message us and we refund the subscription fee in full. Verified in Closed Outcomes — a read-only, exportable audit of every recovered and lost dollar.

Full access to the plan you choose. The 30-day trial clock doesn't even start until Chaser has recovered $100 of revenue for you. Cancel anytime in one click from the Billing page.

Your Stripe connection stays yours — it's bound to your Stripe account, not ours. Your workspace data is kept for 30 days in case you come back, then deleted. Nothing is sent to your customers during that period.

Starter shows a preview. Growth unlocks the full weekly cash-flow timeline and headline numbers. Pro unlocks the full 30-day forward forecast, churn risk view, and monthly cash-flow grid.

Yes — Customer Augmentation lets you push attributes from your warehouse or app (plan tier, MRR, CSM owner, signup date, anything else) and use them in playbook conditions, attention-queue filters, and email personalization. Available on the Pro plan, via CSV import or the ingest API. You can also explore it for free in any sandbox workspace before upgrading.

Starter includes 1 seat, Growth includes 3, and Pro includes 10. Invite teammates from Settings → Team. Each person gets access to the recovery inbox, customer data, and playbook settings based on their role.

Your dashboard shows recovered revenue, recovery rate, how many active recovery sequences are running, expiring cards we've flagged, emails sent, and cards updated. Every action, automated or manual, is logged with who did it and when, so you have a clean audit trail.

When a customer clicks your cancel button, instead of going straight to Stripe, they land on a branded cancel page hosted by Chaser. The page shows your logo, colors, and domain, asks why they are leaving, and can automatically show a save offer -- a discount or a pause -- before the cancellation is processed. If they accept the offer, the subscription continues. If they decline, the cancellation proceeds normally and the reason is logged.

Save rules are conditions you define that trigger an offer when a customer tries to cancel. For example: if the reason is Too Expensive and their MRR is above $50, show a 20% discount for 3 months. Rules are evaluated automatically at the moment of cancel intent, so the right offer appears without any manual intervention.

Yes. The cancel page supports your logo, accent color, background color, card color, dark or light theme, and a custom domain so it appears on your own subdomain rather than chaser.cash. You can also customize the headline, subheadline, cancellation reasons, offer copy, and continue button label.

Every cancellation attempt is logged to your Cancellation Insights dashboard with the reason, whether an offer was shown, whether the offer was accepted, and the MRR kept or lost. This gives you a save rate, a breakdown of cancel reasons, and a running total of revenue saved versus lost over time.

Yes. Failed payment recovery handles involuntary churn -- customers whose cards fail. Cancellation recovery handles voluntary churn -- customers who actively choose to leave. Both are in chaser.cash. You get one dashboard, one integration, and one place to see your full churn picture.

You need to wire your cancel button to call the chaser.cash mint-token endpoint first, then redirect your customer to the cancel page URL with the returned token. The integration takes about 30 minutes. Full documentation and a copy-paste code snippet are in the Integrations section of your workspace.