When a Stripe payment fails, the subscription moves to past-due status. But that status never reaches HubSpot on its own, because billing data and CRM records aren't connected out of the box.
That gap is where involuntary churn happens. Failed payments that go unnoticed for even a few days can result in canceled subscriptions and lost revenue that's hard to win back.
This guide walks through six steps to get past-due Stripe statuses into HubSpot and build automated recovery workflows, using ClearSync to sync billing data in real time.
Quick Guide: How to Monitor Past-Due Stripe Subscribers in 6 Steps
Connect ClearSync to Stripe and HubSpot. Set up real-time subscription status syncing so past-due flags appear on HubSpot records automatically.
Create a past-due subscriber list. Build a HubSpot active list that filters by subscription status equals "past due."
Build your retention workflow trigger. Set up a HubSpot workflow that enrolls contacts the moment their subscription status changes to past due.
Design your churn prevention email sequence. Write 2–4 recovery emails with personalization tokens for plan name, MRR, and account owner.
Set unenrollment rules. Remove contacts from the workflow when their payment recovers or their subscription cancels.
Track recovery metrics. Monitor recovery rates, time to recovery, and churn from past-due status to optimize your sequence.
How to Flag Past-Due Stripe Subscribers in HubSpot Before They Churn
1. Connect ClearSync to Stripe and HubSpot
Head to clearsync.ai and start a free trial. The ClearSync setup walks you through connecting both Stripe and HubSpot. You'll log into each platform when prompted and authorize the connection. No API keys or code required.
ClearSync syncs Stripe subscriptions as native app objects in HubSpot with the fields you need for past-due monitoring: subscription status, MRR, plan name, and billing contact associations. Status changes sync in near real-time, so the moment Stripe marks a subscription as past due, that flag appears in HubSpot.
After connecting, check a few customer records in HubSpot. You should see a ClearSync Stripe Subscription object associated with each paying customer, showing their current status and MRR.
2. Create a Past-Due Subscriber List
Go to CRM > Segments (Lists) in HubSpot and create a new active list. Active lists update automatically, so any subscriber whose payment fails will appear here as soon as ClearSync syncs the status change.
Set your filter criteria to: ClearSync Stripe Subscription > Subscription Status > is any of > "Past Due". If you have multiple products, add filters for plan name or MRR threshold to prioritize high-value accounts.
This list gives you immediate visibility into payment problems. You can review it daily, and a dashboard widget showing the count over time helps you spot systemic issues with specific payment methods or customer segments.
3. Build Your Retention Workflow Trigger
Navigate to Automation > HubSpot workflows and create a new workflow from scratch. For your enrollment trigger, select "Property Value Changed". Choose the ClearSync Stripe Subscription object and set it to fire when Subscription Status changes to "Past Due."
Enable re-enrollment in your workflow settings. Payment failures can happen multiple times during a subscription lifecycle, and each occurrence deserves a recovery attempt.
Add a delay of 1-2 days before your first action. This gives Stripe's built-in retry logic a chance to resolve transient failures (like a bank's temporary hold) before you reach out. No one wants an urgent email about a payment issue that resolved itself a few hours later.
4. Design Your Churn Prevention Email Sequence
Generic "your payment failed" messages feel impersonal and get ignored. Build a sequence that references the customer's specific plan and feels like it's coming from a real person. ClearSync's failed payment recovery playbook walks through a full example.
A three-email sequence spread over 7–10 days works well:
Email 1 (Day 1): Friendly heads-up that references their specific plan and offers to help. Use personalization tokens to pull in the customer's name, plan name, and account owner name.
Email 2 (Day 3): More direct, explaining what happens if the payment isn't resolved. Include a link to update their payment method if your billing setup supports it.
Email 3 (Day 7): Final reminder before the subscription cancels, sent from a senior team member. This escalation often gets attention when earlier emails didn't.
ClearSync syncs fields like MRR, plan name, and subscription start date that you can use as personalization tokens. An email that says "Your $299/month Growth plan" is far more effective than "Your subscription."
5. Set Unenrollment Rules
Before turning on your workflow, configure unenrollment to remove contacts when their Subscription Status changes back to "Active." This prevents recovered customers from receiving continued payment failure emails.
Also set unenrollment for when Subscription Status becomes "Canceled." If someone churns before you can recover them, continuing the sequence serves no purpose and could damage the relationship if they return later.
6. Track Recovery Metrics
Create a simple HubSpot report tracking:
Recovery rate (how many return to active status)
Average time to recovery
Churn rate from past-due status
These metrics help you optimize your email sequence over time. If recovery rates are low, test different subject lines, sending times, or escalation paths. If most recoveries happen in the first 24 hours, you might be able to shorten the sequence.
What Causes Stripe Subscriptions to Go Past Due?
Understanding why subscriptions enter past-due status helps you write better recovery emails and identify systemic issues. Stripe has documented a full list of their decline codes that you can review to help you understand why cards get declined.
Expired or declined cards represent the largest share of failed payments. Credit cards have expiration dates, and customers don't always update them proactively. Some banks also decline transactions they flag as unusual, even when the customer has sufficient funds.
Insufficient funds happen more often than you'd expect, especially with annual billing cycles or customers who use dedicated payment cards with set limits. Charges that hit right before or after payday can have different outcomes.
Payment processor issues occasionally cause failures that aren't the customer's fault at all. Network timeouts, bank maintenance windows, and regional infrastructure problems can all trigger a past-due status that resolves on retry.
Stripe's Smart Retries feature attempts to recover failed payments by retrying at optimal times based on what it knows about your business. However, this doesn't replace direct customer outreach. Some failures require the customer to take action, like updating an expired card or resolving a fraud hold with their bank.
How Long Should You Wait Before Flagging a Past-Due Account?
The timing of your outreach significantly impacts recovery rates. Move too fast and you'll contact customers about issues that resolve themselves. Wait too long and you've lost valuable intervention time.
A 24-48 hour delay after the initial failure works well. This gives Stripe's automatic retry logic time to resolve transient issues while ensuring you reach customers quickly enough to prevent churn.
For high-value accounts, consider a faster response time and a phone call from the account owner rather than email alone. The personal touch can make the difference between a recovered payment and a lost customer.
Your workflow should also factor in the number of retry attempts. Stripe typically retries failed payments over several days (usually 8 times over 2 weeks). Align your email sequence with these retries so each email arrives between attempts, giving customers multiple opportunities to update their payment information or contact their bank.
How ClearSync Helps You Flag Past-Due Subscribers Faster
ClearSync syncs Stripe subscription data to HubSpot in near real-time, which is what makes past-due monitoring work. The moment a payment fails, the status change appears on the associated HubSpot contact and company records. Your workflows trigger immediately.
Automatic contact and company association ensures your recovery emails reach the right person. ClearSync matches Stripe billing contacts to HubSpot records automatically, so you never have to manually link subscription data to customer records.
MRR tracking on every subscription record means you can prioritize recovery efforts by revenue impact. A past-due subscriber paying $2,000/month deserves faster attention than one paying $29/month. You can build MRR dashboards in HubSpot to track at-risk revenue alongside your broader metrics.
Historical data import lets you backfill past subscription events, so you can analyze payment failure patterns and recovery rates for customers who had issues before you set up the workflow.
Start a free ClearSync trial and connect your Stripe account in minutes.
FAQs About Monitoring Past-Due Stripe Subscribers in HubSpot
What does "past due" mean in Stripe?
In Stripe, "past due" means an invoice for a subscription has not been paid by its due date. The subscription stays active while Stripe attempts automatic retries, but revenue has not been collected.
Stripe status | What it means |
Active | Payment current, subscription running |
Past due | Invoice unpaid, retries in progress |
Canceled | Subscription ended |
Trialing | Free trial, no payment yet |
Unpaid | All retry attempts failed |
ClearSync syncs these statuses to HubSpot so you can see payment issues on customer records directly.
Can HubSpot natively track Stripe subscription status?
HubSpot's native Stripe Data Sync app syncs basic subscription information but doesn't include real-time status changes or MRR calculations. For workflow triggers based on status transitions (like moving to past due), you need ClearSync to sync these changes as they happen.
How quickly should I contact past-due subscribers?
A 24-48 hour delay after the initial failure works well. This allows Stripe's automatic retry logic to resolve transient issues while ensuring timely outreach. ClearSync syncs status changes in near real-time, so you control the timing through your workflow delay settings.
What's the difference between voluntary and involuntary churn?
| Voluntary churn | Involuntary churn |
Cause | Customer cancels intentionally | Payment failure goes unrecovered |
Signal | Cancellation request | Past-due status in Stripe |
Prevention | Retention offers, product value | Payment recovery workflows |
Past-due monitoring targets involuntary churn by catching payment issues before they result in cancellation. ClearSync syncs both churn types as distinct events in HubSpot so you can report on them separately.
How many recovery emails should I send?
Two to four emails spread over 7–10 days works well. The sequence should escalate in urgency while remaining helpful. ClearSync syncs personalization fields like plan name and MRR that make each email specific to the customer's account.
Can I track payment recovery rates in HubSpot?
Yes. By tracking workflow enrollment and unenrollment, you can calculate what percentage of past-due subscribers return to active status. ClearSync's historical data import also lets you analyze recovery patterns for customers who experienced payment issues in the past.
