Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Why Marketing Automation Ignores Customer Payment Failures
Transcript
- Lucas: If these marketing conversations have sparked something you've actually used in your own work, you're exactly the kind of listener who keeps this show alive, and we'll get to that in a bit. But first — Luna, did you know that roughly 12 percent of subscription customers churn every year simply because their payment method fails? Luna: Twelve percent? That seems high. I would have guessed maybe half that, because most companies send at least a few reminder emails. Lucas: They do send reminders, but the timing is often terrible. A lot of automated systems wait three or four days after the first failure, then send a generic 'we couldn't process your payment' message that looks like spam. By then the customer has already mentally checked out. Luna: So the failure isn't really the payment — it's the workflow. Or lack of one. Lucas: Exactly. The 2025 Subscription Trade Association study found that 58 percent of consumers say a well-timed, personalized payment recovery message actually improves their opinion of the brand. But most marketing automation platforms — HubSpot, Marketo, the usual suspects — treat payment failures as a billing problem, not a relationship signal. Luna: That's a pretty big gap. So what would a good workflow look like? Lucas: Let's use a concrete example. Say you run a SaaS company using Stripe for billing. A customer's card expires. Stripe flags the failure and sends a standard dunning email. But here's the thing — Stripe's default dunning is purely transactional. It doesn't know anything about the customer's lifecycle stage, their engagement score, or even what product they use. Luna: Right, because Stripe isn't a marketing platform. It's a payment processor. Lucas: Exactly. So the opportunity is to use a marketing automation platform that can listen for Stripe's webhook — the payment_failed event — and then trigger a smart workflow. Within 24 hours, send an email that says something like 'Hey, we noticed your card on file expired. Your account's still active, but we'd hate for you to lose access. Click here to update your payment details in under a minute.' Luna: That sounds reasonable. But doesn't that risk coming across as pushy if you send too many? Lucas: It does, and that's the tension. A 2024 study from Recurly found that companies that send more than three payment-failure emails actually increase churn by 6 percent. The sweet spot is two reminders — one at 24 hours, one at 72 hours — and then a final message on day seven that offers to downgrade to a free tier or pause the subscription. Luna: So you're giving them an off-ramp that's not just 'pay or leave.' That's smart. Lucas: And it works. The same study showed that companies using a context-aware workflow — meaning they consider the customer's tenure, past payment history, and product usage — recovered 34 percent of at-risk accounts. Compare that to a generic three-email sequence, which recovered only 18 percent. Luna: So nearly double. That's a massive lift for something that's basically just better timing and a little personalization. Lucas: It is. And yet, most marketing automation campaigns I see still treat payment failures as an afterthought. They'll have elaborate birthday flows and re-engagement sequences, but the payment failure workflow is either nonexistent or outsourced to a billing system with no marketing context. Luna: I wonder if part of the issue is that marketing teams don't own billing data. It's a silo problem. Lucas: That's exactly it. In most organizations, the billing team handles dunning, and the marketing team handles everything else. They rarely talk. But a payment failure is a marketing moment — it's a chance to show the customer you care about their experience, not just their money. Luna: And if you mess it up, you lose a customer forever, often for something as trivial as an expired card. Lucas: Which brings us to something I've been meaning to mention. You know, this show exists because listeners like you support it directly. A couple of dollars a month is genuinely what keeps these going — buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, it's a small thing that makes a big difference. And it keeps us ad-free, so we can dig into topics like this without worrying about sponsor constraints. Lucas: Exactly. So back to payment failures. One other nuance I want to flag is the difference between a one-time failure and a pattern. If a customer's card fails once, it's probably a card expiry. If it fails three times in a month, it could be a fraud flag or a cash flow issue. Luna: And you'd want to treat those differently, right? A pattern might warrant a human touch — like a phone call or a tailored offer. Lucas: Exactly. Some companies use a risk score based on the failure reason code. Stripe returns codes like 'expired_card', 'insufficient_funds', or 'fraudulent'. An insufficient funds failure might mean the customer is in financial stress, so you could offer a discount or a payment plan. A fraud flag might mean the card was stolen, so you want to lock the account and send a security alert. Luna: That's a level of nuance most automated systems don't have. But it seems worth the investment, given the retention upside. Lucas: It is. And the technology is already there. Both HubSpot and Marketo can ingest custom webhook data and branch workflows based on payload fields. So you can create a single 'payment failure' trigger that then checks the failure reason and routes accordingly. Luna: Are there any companies that do this well that you can point to? Lucas: One that comes to mind is the meal-kit company Sun Basket. They had a problem with churn at renewal, and they traced it back to expired cards. They built a workflow that, instead of sending a generic dunning email, sent a recipe recommendation based on the customer's past orders with a note saying 'Your next box is on hold — update your payment to get it.' Their recovery rate went from 22 percent to 41 percent. Luna: So they made the payment request feel like part of the experience, not an interruption. Lucas: Exactly. That's the principle — every payment failure is a customer experience failure in disguise. And marketing automation is the tool to fix it, if you design the workflow with empathy instead of just efficiency. Luna: I think the key takeaway here is that payment failure workflows are a blind spot that's costing companies real revenue, and fixing it doesn't require new software — just better integration between the data you already have. Lucas: And a willingness to see billing as a marketing function. Because when a card fails, the customer is still a customer — they just need a little help staying one.