Subscription payment recovery

Your processor retries the card. It doesn’t talk to your customer.

JMJ recovers failed subscription payments with a timed sequence of plain, human emails — and actually reads the replies. Works with Stripe. Works with Square.

  • Works with Stripe
  • Works with Square
  • Sends from your domain

About 9% of subscription revenue fails to collect every month.

Not because customers left. Because a card expired, a bank flagged a charge, or an ACH debit bounced. The customer still wants the service. Nobody told them anything went wrong.

Stripe’s automatic retries recover roughly a third of those dollars. Square retries on days three, six, and nine and you cannot change it. After that, both of them stop — and the subscription quietly cancels.

That is the gap. It is not a payments problem. It is a conversation nobody is having.

We have the conversation.

Five emails. Timed to the failure, not to a calendar. Different wording for a declined card than for a bounced bank draft, because those are different problems and the customer needs to do different things.

Every message goes out under your name, from your domain, with your sign-off. Your customer never sees ours.

The sequence stops the second the payment clears. Nobody gets an email asking for money they already paid.

What you get

The part your processor doesn’t do

  • Built for Square, not just Stripe

    Square gives you three fixed retries and no way to change them. We add the part Square doesn’t have.

  • Card and bank drafts speak differently

    A declined card needs a new card. A returned ACH debit needs a bank conversation. Same failure to your ledger, two different emails.

  • Replies come back to a person

    Customers answer these emails. We read every reply, sort it, and only put the ones needing a decision in front of you.

  • Your name on every message

    Your domain, your sender identity, your sign-off. White-label all the way down.

  • It stops when they pay

    Payment clears mid-sequence and the sequence ends. No awkward email the morning after.

  • Every send is on the record

    Full audit trail of what went out, when, to whom, and what came back.

It pays for itself at about a hundred active subscriptions.

Roughly 9% of subscription revenue fails each month. Your processor’s built-in retries recover about a third of those dollars. A tuned recovery sequence on top of that adds roughly fifteen points more.

Below about a hundred active subscriptions, that recovery is smaller than what we cost, and we will tell you so on the call. Above it, the math turns quickly.

Recovery ranges above are industry benchmarks for the category, not a forecast of your results.

FAQ

Questions subscription operators ask

Straight answers on processors, replies, white-labeling, and what happens the moment a payment clears.

Does this work with Square?

Yes. Square’s built-in recovery is three fixed retries on days three, six, and nine, and it cannot be adjusted. JMJ Dunning adds the customer-facing sequence Square does not have. Most dunning tools support Stripe only.

Does this work with Stripe?

Yes. JMJ Dunning runs alongside Stripe’s Smart Retries rather than replacing them — the retries handle the card, we handle the customer.

Will my customers know JMJ is involved?

No. Every message sends from your domain under your business name with your sign-off. There is no JMJ branding anywhere a customer sees.

What happens when a customer replies?

The reply comes back to us, gets classified, and lands in your action list only if it needs a decision. Routine replies are handled automatically. Anything that looks like a dispute always goes to a human.

Do I need your accounts receivable product to use this?

No. Dunning is sold on its own. If you also send invoices, the two work together, but neither requires the other.

What if the payment goes through mid-sequence?

The sequence stops immediately. Your customer will not get an email about a payment they already made.