Skip to main content
The Stripe Audit reads your payment history and reports how many payments are failing, why, and how much of that revenue a recovery programme would be expected to recapture. It runs in read-only mode and requires no code.

​
What the audit does

When you connect your Stripe account, Airdun scans your payment history and returns four things:
  1. Every failed payment — expired cards, insufficient funds, bank blocks, 3DS friction, network errors, and every other Stripe decline code in your history.
  2. An estimate of your recoverable MRR — derived from recovery-rate benchmarks by failure type and industry, applied to your own failure history.
  3. Your failure patterns — which decline reasons are most frequent in your account.
  4. A recommended plan tier — based on your monthly failed-payment case volume.

​
Running the audit

1

Create your Airdun account

Go to app.airdun.com/register and sign up with your work email. No credit card is required to run the audit.
2

Connect your Stripe account

Click Connect Stripe in the onboarding flow. You will be redirected to Stripe’s standard OAuth consent screen, where you grant Airdun read-only access. Airdun cannot move money, modify customers, or change any Stripe settings at this stage.
If you manage multiple Stripe accounts, run a separate audit for each one — each connection is scoped to a single account.
3

Review your results

Within seconds of connecting, your audit dashboard populates with your recoverable MRR estimate, a breakdown of failure reasons, your monthly case volume, and a recommended plan tier.
4

Activate recovery

When you are ready, select your plan and follow the configuration steps to connect your outreach channels and switch on the autopilot. See the Quickstart for the full procedure.

​
What data the audit reads

Airdun accesses only the data needed to identify failed payments and build recovery cases.
Payment intent statuses, decline codes, retry history, and subscription details. This is the data used to detect failures and calculate your recoverable MRR.
Customer records including name, email address, and phone number where present. Used to personalise recovery messages and determine which outreach channels are available for each case.
Stripe’s decline codes and network response codes. This context drives the recovery strategy — a 3DS friction failure triggers a different sequence than an expired card.
Raw card numbers, CVCs, full bank account numbers, and other sensitive financial credentials. This data is not accessible through the Stripe API and is never part of any Airdun integration.
You can revoke Airdun’s access to your Stripe account at any time from the Apps section of your Stripe Dashboard. Revoking access pauses all active recovery cases immediately.