DEV Community

Swipe Again for Swipe Again

Posted on

Your Customer Got the Failure Email Too. Here Is What They Do Next.

Most writing about failed payments is written from the merchant's side of the glass: queues, retries, recovery rates. It is worth spending a few minutes on the other side, because the customer's experience of a failed subscription payment is stranger than most billing teams imagine — and designing for it honestly is the difference between a rescue and a quiet cancellation.

Begin with the fact that the customer usually did nothing. The card was replaced after a fraud alert in another state. The bank tightened a rule. The account was forty dollars short on the wrong Tuesday. From the customer's chair, the subscription simply hiccups, and the first they hear of it is a message whose tone will decide everything. If that message sounds like an accusation, they feel accused — of being broke, of being careless — and accused people do not hurry to help you. They postpone. Postponement, in subscription billing, is indistinguishable from churn two weeks later.

Then comes the fix itself, and here the friction compounds. The customer clicks through and meets a login they have not used in months, a password they do not remember, a card form that wants the billing address exactly as the bank holds it. Each obstacle is small. Together they form a wall, and on the other side of the wall the customer starts doing different maths: how much do I actually use this? A payment failure forces a re-evaluation that the customer was never going to volunteer for, which is why so many involuntary failures end as voluntary cancellations wearing a disguise.

The practical guidance in what a subscriber should do next when a subscription payment fails is written for that customer, and merchants should read it as a design brief. Update the card promptly, yes — but notice what the guidance assumes: that updating is easy, that the deadline is clear, that access continues while the fix is made, that a human answers if something looks wrong. Every assumption your own process fails is a leak with a name.

There is a subtler point about timing. Customers fix payment problems in the margins of a day: on a phone, in a queue, between meetings. The window is minutes wide and it closes. A secure update link that works without a login respects that window. A link that expires in an hour insults it. A reminder sent while the customer is at work, readable at lunch, outperforms a technically superior campaign sent at an hour chosen by a server's timezone rather than a person's life.

Merchants who doubt this should run the cheapest experiment in billing: take the next failure notice your own system sends and follow it, on a phone, as a customer would. Time it. Count the screens, the fields, the moments where you would need information you do not carry in your head. Note the exact sentence where the message stops sounding like a person and starts sounding like a policy. Most teams find the exercise quietly horrifying, and most fix at least two things within the week — which is the point. The customer's path through a failure is a product surface, and it deserves the same walkthrough discipline as the checkout it protects.

None of this requires sentimentality. It requires remembering that a failed payment is a joint problem briefly shared by two parties, only one of whom chose to be in the conversation. The businesses that recover well write their messages, their deadlines, and their update pages as if the customer is busy, blameless, and one annoyance away from reconsidering the whole subscription — because all three are true, every time, and the billing teams that internalise it stop losing people they had already won.

Swipe Again (swipeagain.com) is flat-fee failed payment recovery for subscription businesses — $179/mo, no percentage of recovered revenue, no sales call required.

Top comments (0)