The rule behind a performance fee, written out so you can check it instead of trusting it.

How we attribute recovered revenue

In one sentence. An invoice counts toward our fee only if our own series actually ran on it, and the amount we bill is the amount Stripe records as paid on that same invoice — the same id, amount and date your own dashboard shows.

Why this page exists

We charge a share of what we recover, which invites an obvious question: if the number comes from us, what stops it being flattering?

Churn Buster states the objection publicly on their own pricing page — pay-for-performance is “easy to game ‘performance’ with reporting that favors that model, and we want our interests fully aligned with our clients.” That is a fair objection, and reassurance is not an answer to it.

So here is the rule in full, and here is how you check it without taking our word for anything.

“Why doesn't Churn Buster offer pay-for-performance pricing? Because it's easy to game ‘performance’ with reporting that favors that model, and we want our interests fully aligned with our clients.”

Source: churnbuster.io/pricing — read 2 October 2026

The rule, in five parts

  1. 1

    Our series has to have actually run on the invoice

    An invoice counts only if at least one step of ours really happened on it — a retry we attempted, or a message our tool wrote for that invoice. In the engine that is a step recorded as rendered, executed or failed.

    Two things deliberately do not count. A step that could not run at all: a retry with no Stripe key to make it, or a message with no address to write to. Those are recorded as skipped, and a skipped step never creates a billable event. And a step we cancelled — because the invoice got paid or the customer opted out first.

    An invoice we merely know about is tracked, not chased, and tracked invoices are not billable. So if an invoice was paid before anything of ours touched it, we don't bill it, even though we were watching it.

  2. 2

    The amount is Stripe's amount, and nothing is recovered when Stripe records nothing

    We bill what Stripe records as paid on that invoice. If only part of the invoice came back, only that part is billable.

    And a case worth stating on its own, because it is the one line where a self-reported number would be most tempting: if Stripe reports an invoice paid while recording zero as paid, we treat it as not recovered and bill nothing. The engine files that invoice under a status called paid_unrecovered, credits 0 cents for it, and cancels whatever was still queued for it. The billing summary skips that status entirely, so it cannot reach a fee.

    There is no second set of numbers on our side, and no internal figure that differs from what your dashboard shows.

  3. 3

    If Stripe says it wasn't recovered, we don't bill it

    Our revenue figure is built only from invoices Stripe reports as paid. An invoice that fails and stays failed costs you nothing: there is no minimum, no retainer and no setup fee to make up the difference.

  4. 4

    Refunds and reversals come off the bill — and we do not detect them

    Our tooling does not look for refunds, reversals, chargebacks or disputes. Nothing in the engine does.

    So we ask you at invoicing time, your answer is the one we use, the amount comes off the next invoice or we issue a credit note, and we confirm it in writing. If you never tell us, we will not have found it ourselves. We would rather say that plainly than imply a check we don't run.

    This is a limit of ours, stated here rather than discovered by a client.

  5. 5

    A new failure starts a new series, and one click stops the customer

    Steps are scheduled per failed invoice, measured from the day that payment failed: a deliberate retry on days 0, 3 and 7, and a message on days 0, 3, 7 and 14 — day 14 being a final message rather than another attempt.

    If the same customer fails again on a different invoice, that is a new series and we would write to them again — unless they have opted out. A one-click opt-out is at customer level, not invoice level: the click cancels everything still queued for that invoice and records a suppression against the person, so nothing gets scheduled for them on any other invoice either. If someone tells us another way — replying to a message, or telling you — we suppress them by hand.

How you check us

Every fee comes with the invoice-by-invoice list, and the list is the point. For each invoice we bill you for, it names the Stripe invoice id, the amount Stripe recorded as paid, the date, and which of our steps ran on it.

  • Open those ids in your own Stripe. Compare the amount and the date. If our list and your Stripe disagree, your Stripe is right — say so, and the fee changes.
  • The list also shows the invoices Stripe marked paid that we did not chase, and therefore did not bill. The engine counts those separately and says so out loud, because the most useful thing we can send you is the money we didn't charge for.
  • The figure we quote comes from our own operations summary, built only over invoices we chased. Not from an invoice's recovered flag, which can be set on an invoice no step of ours ever touched. That is an internal detail, but it is why a list accompanies every invoice rather than a total.
  • The list is produced by hand from the engine's own commands. bun run engine summary gives the chased-and-recovered figures, bun run engine invoices the per-invoice amounts and dates, and bun run engine actions --invoice … the step-by-step trail. A person pastes them into the email. There is no automated report generator yet, and we would rather tell you that than imply one.
  • We can only name invoices we were tracking. That is why a pilot asks you to add one webhook endpoint in Stripe: without it we never learn that a payment failed, and we won't bill from memory for something we didn't see.
One check we looked for and could not confirm, so it is not claimed: we wanted to tell you that a retry of ours shows up as a rising attempt count on your own invoice. Stripe's documentation describes attempt_count as the payment attempts made “from the perspective of the payment retry schedule”, which governs Stripe's own scheduled retries; it does not say that an attempt made through the API appears the same way to you. We could not confirm it, so it is not on this page. The checkable artefact is the invoice list and the invoice itself in your Stripe.

Two numbers we will not give you, here or anywhere

No recovery rate, and no payback period. Not because they would be unflattering to us — because whether a customer still wants the product is recorded nowhere in Stripe, and a rate we produced ourselves would be exactly the flattering reporting this page exists to answer.

Nothing about the free audit is billable

The audit is read-only, it produces one page, and no customer of yours is contacted in producing it. Fees only exist inside a pilot that has started, under terms written down and agreed before anything goes live.

What this page does not claim

  • We have no customers and we have recovered $0. This rule has never run against a real Stripe account. It is built and tested against constructed payloads and fixtures; yours would be the first real one.
  • Our tooling does not detect refunds, reversals, chargebacks or disputes. That is your flag to give, under rule 4, and we take it as authoritative.
  • During a pilot a person runs this by hand. Nothing fires on a schedule and no message sends itself, so “a step ran” during a pilot means a person ran it or wrote it. A message our tool rendered is recorded as rendered, not as delivered, until a person sends it.
  • There is no dashboard. The invoice list arrives by email, in plain numbers, with the command output behind it.
  • This page is not a contract. The percentage, the period and the extra permission are agreed in writing for your account, and those terms are the ones that apply.

Where this came from

This rule is not a policy written for the website. It is what the engine already does, and the pages that promise it to a client say the same thing as this one. If you want to see how the numbers arrive, the audit page is a real run of our tool over a synthetic Stripe account — made-up invoices, no client, every figure printed by the tool rather than typed in.

See the rule applied to your own invoices

The free Failed-Payment Leak Audit is read-only, costs nothing, and produces one page: what is at risk in your Stripe account, which declines a new card would fix, and which ones nothing would. There is no fee until a pilot starts and something is actually recovered.

Request the free leak audit