Latest / Marketing Automation with Fexingo: HubSpot, Marketo, and Automated Customer Journeys / Marketing Automation Ignores Customer Credit Card Churn
Transcript
- Lucas: You get a new credit card in the mail — maybe a better rewards card, maybe your old one had an annual fee kick in — and you update it with your bank, your streaming services, your meal-kit subscription. Life goes on. Luna: But the marketing automation system never noticed. No email, no workflow, no segment update. Just silence. Lucas: Exactly. That card switch is one of the highest-signal customer behaviors that almost no one tracks. And it costs real money. I was looking at churn data from a DTC meal-kit company — they lost 11% of subscribers within 60 days of a card change, and they never sent a single message about it. Luna: Eleven percent. That's huge. And the marketing team probably blamed price sensitivity or 'seasonal churn' when the real trigger was sitting in their payment processor. Lucas: Right. So, look — this show stays ad-free because listeners chip in a couple of dollars a month. If these marketing conversations have sparked something you've actually used at work, buy me a coffee dot com slash fexingo. Genuinely helps. Luna: Yeah, it's a small thing that makes a real difference. Keeps us independent. Lucas: Back to the card switch blind spot. The meal-kit company I mentioned — they run on a standard automation stack. HubSpot for CRM, Stripe for payments, a few connected apps. When a customer updates their card number in Stripe, that event is technically available. But nobody built a trigger for it. Luna: Why not? It seems obvious. 'Hey, we see you switched cards — thanks for keeping your account active. Anything we can help with?' Lucas: You'd think. But in practice, payment data and marketing data live in different departments. The payments team cares about successful transactions and failed auths. The marketing team cares about opens and clicks. The card change event falls into a gray zone — the payments team doesn't think it's interesting, and marketing doesn't know it exists. Luna: It's a classic data silo problem. The same thing happens with address changes, right? People move and suddenly their mail-order subscriptions break. Lucas: Exactly. But cards are worse because they're tied to the payment method itself. If a customer switches from a Visa to an AmEx, they might also be signaling a shift in financial behavior — maybe they're consolidating spending, maybe they got a premium card that changes how they think about subscriptions. Luna: So what would a good triggered workflow look like? Not creepy, not 'we see your every move.' Lucas: Something simple. A single email, sent 24 hours after the card update: 'Thanks for keeping your billing info current. By the way, we noticed you're using a new card — if you ever have questions about your plan, we're here.' That's it. No segmentation, no deep personalization. Just acknowledgment. Luna: And that would reduce churn? Just an acknowledgment? Lucas: I found one company that tried it — a pet food subscription brand. They added a 'new card detected' trigger to their email flow. Their retention for customers who switched cards went up by 4 percentage points. That's a meaningful lift for zero additional media spend. Luna: Four points. And they probably spent less than an hour setting up the workflow. What about the banks themselves? Do Chase or AmEx share card-change signals with merchants? Lucas: Generally no. The card networks provide tokenized payment credentials through services like Visa Account Updater — that's how recurring billing keeps working when a card expires or gets reissued. But the merchant just gets a 'token successfully updated' message. No indication that the underlying card changed. Luna: So the signal has to come from the payment processor on the merchant side. Stripe, Braintree, Adyen — they all have webhooks for 'payment_method.updated' events. Most marketers don't know those exist. Lucas: Right. And even if they do, the marketing automation platform might not have a native way to ingest that event. HubSpot can take custom webhook data, but it requires a Zapier or a custom integration. Marketo has more rigid data models. So the friction is real. Luna: It's a classic 'low-hanging fruit that nobody picks' situation. The data exists, the tooling exists, but the process doesn't. Lucas: And the cost of inaction is measurable. Let's say you have 10,000 subscribers paying $50 a month. If 1% change cards in a given month, that's 100 accounts at risk. If 11% of them churn, you lose 11 subscribers — $550 a month in recurring revenue. Over a year, that's $6,600. For one email. Luna: And that's a conservative estimate. For a bigger base, it adds up fast. Plus the cost of acquiring those subscribers in the first place. Lucas: There's also a customer experience angle. The first time a customer realizes their card expired and their subscription lapsed is when they go to use the service. That's a bad moment. A proactive 'hey, your card needs updating' email is better, but a 'thanks for updating your card' email is even better — it builds goodwill. Luna: So why aren't more brands doing this? Is it technical, cultural, or just unawareness? Lucas: All three. Technically, it requires someone to connect payment data to marketing data. Culturally, marketing teams think about browsing behavior, email opens, purchase history — not payment method changes. And most people simply don't know the event exists. I didn't until a payments engineer mentioned it at a conference. Luna: So what's the first step for a marketing ops person listening right now? How do they check if their own platform can do this? Lucas: Go to your payment processor's developer docs and search for 'webhook events.' If you're on Stripe, look for 'customer.source.updated' or 'payment_method.attached.' If you use Braintree, it's 'transaction.sale' plus the card token change. Then check whether your marketing automation platform can receive custom webhooks. Most can, with a middleware layer. Luna: And if it can't, you're probably due for a platform upgrade anyway. This is one of those 'easy wins' that separates modern stacks from legacy ones. Lucas: It really is. I think in five years, a 'card switch detected' trigger will be as standard as a 'welcome email' trigger. It just needs a few brands to prove the ROI first. Luna: We'll be watching. Maybe we should follow up in six months and see if any listeners implemented it. Lucas: Good idea. If you try it, let us know what happens. That kind of real-world data is gold for this show.