Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Journey Maps Miss the Payment Failure Touchpoint
Transcript
- Lucas: Luna, quick question. When was the last time you had a payment decline — a card get rejected for something you actually wanted to buy? Luna: Oof. Probably a few months ago. I was trying to renew a software subscription, and my card had expired. I didn't notice for like three days. Lucas: And what did you feel? Not just inconvenience — what was the emotional reaction? Luna: I think... a little embarrassed? Like, is my account overdrawn? And then annoyed because I had to go find my new card and update the payment. Honestly, I almost just let the subscription lapse. Luna: Wait, really? Even in subscription businesses where failed billing is basically inevitable? Lucas: Especially there. Most maps show the happy path — browse, add to cart, checkout, receive confirmation, use product. The unhappy paths are rarely mapped. And payment failure is probably the most common unhappy path that's completely invisible. Luna: Okay, so let's put some numbers on this. How common are payment failures in practice? Lucas: Stripe published data in 2025 — they process payments for millions of businesses globally. Their network-wide decline rate is about 9 percent for card not present transactions. That's nearly one in ten attempts. For recurring billing specifically, the failure rate on the first retry is around 15 percent. And after three attempts, about 5 percent of subscriptions are still failing. That's involuntary churn — customers who want to keep paying but can't. Luna: And those customers often don't come back. I've seen stats that say less than 30 percent of customers who involuntarily churn ever resubscribe. Lucas: Exactly. So when a journey map ignores payment failure, it's ignoring a touchpoint that can cost a business 10 to 30 percent of its recurring revenue. That's not a minor edge case — that's a major leak. Luna: But why do journey mappers skip it? Is it because they think it's a technical issue, not a customer experience issue? Lucas: I think it's partly that. Payment failures get handed off to the finance or engineering team. The marketing team builds the journey map, and they focus on the touchpoints they control — emails, ads, landing pages. They don't think about the billing system. But the customer doesn't distinguish between 'marketing experience' and 'billing experience.' To them, it's all just the company. Luna: So what does a good payment failure touchpoint look like? Let's get concrete. Lucas: Let's use HelloFresh as an example. The meal-kit company has millions of subscribers, and they were seeing involuntary churn around 12 percent from payment failures. They mapped the journey and realized that when a card declined, they were sending a standard email — 'Your payment failed, please update your billing info.' That email had an open rate around 40 percent, but only about half of those who opened actually updated their card. Luna: So the email alone wasn't enough. What did they change? Lucas: They added a push notification to their mobile app — sent within five minutes of the decline — with a direct deep link to the billing page. That notification had a click-through rate of 22 percent. Combined with the email, they recovered about 70 percent of customers who would have otherwise churned. They cut involuntary churn by 22 percent overall. Luna: So the key was speed and directness. The notification arrived while the customer was still in the context of the transaction. Lucas: Right. And the deep link removed friction — you didn't have to log in and navigate to settings. One tap, and you're on the payment update page. That's journey mapping at the micro level. Luna: But not every business has an app. What about a purely e-commerce business with one-time purchases? The payment failure there is more transactional, but still a touchpoint. Lucas: Absolutely. For a one-time purchase, the decline happens at checkout. The customer sees a generic error: 'Your card was declined. Please try a different payment method.' That's the moment. And most businesses treat it as a dead end — you either try again or you leave. But a journey mapping mindset would ask: what if we offered a one-click alternative? Like, 'Your Visa was declined. Would you like to pay with PayPal?' Or even offering to split the payment across two cards. Some fintechs are experimenting with that now. Luna: There's also the emotional side. When a card is declined in public — at a store or on a website — it's humiliating. Even if it's just a technical glitch, the customer feels judged. Lucas: That's the part that journey maps are supposed to capture: the emotional state. But they rarely do for payment failure. The standard map shows a happy customer at checkout. The reality is that 9 percent of them hit a wall of shame. And the company's response — or lack of response — determines whether that customer ever comes back. Luna: So if someone listening wants to fix this, what's the first step? How do you even discover that you have a payment failure problem? Lucas: Start with your billing data. Pull the decline rate for the last three months. Segment by transaction type — one-time versus recurring. Then look at the recovery rate: how many customers who hit a decline eventually complete the purchase or update their payment method. If that rate is below 50 percent, you have a journey map gap. Luna: And then map the actual experience. Go through it yourself — intentionally use a card that's about to expire. See what happens. Lucas: Exactly. Walk the path. And when you do, you'll almost certainly find that the messaging is generic, the retry logic is opaque, and the customer is left to figure it out alone. That's the gap. Luna: You know, Lucas, I realize we talk a lot about optimizing the happy path — the perfect journey. But these hidden touchpoints, like payment failure, are where the real loyalty is built or lost. Lucas: Speaking of building loyalty through content — if today's episode sparked something you've actually used in your own journey mapping, honestly, that's the moment when listener support matters most. We keep this show ad-free by choice, and the only way that works is if people who find value here toss in what they think it's worth. There's a link at buy me a coffee dot com slash fexingo — lower case, no spaces. If today was worth even a coffee to you, that's the place. No pressure, no upsell. Just a real way to keep these conversations going. Luna: Yeah, it's a small gesture that makes a big difference for us. And we appreciate every single one. Lucas: Alright, back to payment failures. One more thing I want to highlight: the retry logic itself is a journey design decision. Most companies retry the card automatically after three, five, and seven days. But that cadence was chosen by a developer, not a customer experience designer. Luna: What would a better cadence look like from the customer's perspective? Lucas: First, retry within minutes of the initial failure, not days. If the decline was a temporary issue — bank security flag, network timeout — a quick retry often works. Stripe data shows that retrying within five minutes recovers about 30 percent of declines. Then if that fails, send a notification immediately, not after three days. The customer still remembers why they were buying. After three days, they may have moved on emotionally. Luna: So speed plus clear communication. And maybe offering an alternative payment method before the second retry. Lucas: Yes. Some subscription companies now show a 'retry with a different card' button right inside the notification. That's a designed touchpoint — it didn't happen by accident. It came from mapping the failure journey and realizing that the customer's willingness to act peaks right after the decline, then decays rapidly. Luna: I've also seen companies use SMS for payment failure alerts, especially for subscription services like streaming or SaaS. The open rate on SMS is over 90 percent. Lucas: SMS is powerful, but you have to be careful with compliance. In the US, you need opt-in for marketing texts. But a transactional message about a payment failure is generally allowed. Still, best practice is to have an explicit opt-in for payment-related texts at sign-up. Luna: So journey mappers should add that as a step in the sign-up flow: 'Can we text you about billing issues?' That's a proactive touchpoint. Lucas: Exactly. And it's a tiny addition that can dramatically improve recovery rates. But again, it only happens if someone maps the failure path. Luna: Let's talk about fraud declines for a second. A lot of legitimate transactions get declined because of overly aggressive fraud filters. That's a different kind of failure — the customer is being penalized for the bank's risk model. Lucas: That's a huge one. Visa's 2024 data showed that about 15 percent of all declines are false positives — legitimate transactions the bank flagged as suspicious. For the customer, it's the same emotional experience: rejection. But the merchant often has no idea it's a false positive. They just see 'declined.' Mapping this touchpoint would prompt the merchant to ask: 'Do we have a way to help the customer retry with a different verification method? Or call their bank?' Some companies now include a phone number for the bank's fraud department right in the decline message. Luna: That's smart. It turns a dead end into a guided path. Lucas: Right. And it's exactly the kind of insight that comes from journey mapping — not from a dashboard. Dashboards show you the decline rate. Journey mapping shows you the human cost. Luna: Okay, so let's say I'm a marketer and I want to add payment failure to my journey map. Where do I start? Walk me through it. Lucas: First, pull a sample of actual customer experiences — support tickets, chat logs, social media mentions about payment issues. You'll see a pattern of language: 'My card was declined but I have money,' 'I tried three times and it still didn't work,' 'I'm not sure why it failed.' That's your raw material. Luna: Then map the current flow: what happens from the moment the customer hits 'pay' to the moment they either succeed or give up. Lucas: Exactly. Include the system actions — retries, notifications — and the customer's emotional state at each step. You'll likely find a gap: the system retries silently, the customer doesn't know, then three days later they get an email and think 'Oh, I forgot about that.' By then, the impulse is gone. Luna: So the fix is to close that gap — notify immediately, offer a clear path, and reduce friction. Lucas: Yes. And once you've redesigned the failure touchpoint, measure the impact. Compare your involuntary churn rate before and after. If you cut it by even 10 percent, that's often a huge revenue win, especially for subscription businesses where customer acquisition cost is high. Luna: I think the big takeaway here is that payment failure isn't just a billing problem — it's a customer experience problem that belongs on every journey map. Lucas: And it's one of the highest-leverage touchpoints to fix, because it's so often ignored. The companies that do map it, like HelloFresh, see real results. The rest are leaving money — and relationships — on the table. Luna: Alright, Lucas, I think we've given everyone a lot to think about. Next time you're reviewing your journey map, just ask: where does payment failure live? And if it's not there, that's your first edit. Lucas: Exactly. And if you want to hear more deep dives into the hidden touchpoints that actually drive customer loyalty, we'll be back with another episode soon. Until then, keep mapping the paths that matter.