How Do I Stop Losing Members to Failed Payments in MemberPress?
When a MemberPress payment fails, the plugin can send a single notification email automatically. That one email recovers some members, but a single touch is rarely enough. Krom Automation, our free WordPress workflow plugin, lets you build a full recovery sequence triggered by that failed payment event, including a follow-up email 48 hours later, a Slack alert to your team, and a win-back offer if the member cancels.
The free version covers the core sequence. The Pro version adds the visual email builder and Slack integration for richer alerts.
The setup takes roughly 30 minutes end to end. The sections below walk through MemberPress configuration first, then the automation layer on top of it, then what to actually write in each message because none of the official docs cover that part.
Browse the full Krom Automation feature list to see every trigger and action available before you start building.
What Does MemberPress Actually Do When a Payment Fails?
MemberPress handles failed payments differently depending on your gateway. With Stripe, the gateway itself retries the charge on a schedule you configure inside Stripe’s dashboard, typically 3 attempts over 7 to 14 days.
With PayPal, retry logic sits inside PayPal’s subscription settings. MemberPress does not control retry timing directly. It listens for the gateway’s webhook and reacts when a failure event arrives.
When that failure webhook lands, MemberPress can do three things automatically:
- Send a “failed transaction notice” email to the member, if the toggle is enabled in Settings
- Send the same notice to the admin email address
- Suspend or cancel the subscription depending on how many consecutive failures you allow in your gateway settings
That built-in email is a starting point, not a recovery strategy. It fires once, carries default MemberPress branding, and contains no logic for what happens if the member ignores it.
How Do I Enable the Failed Payment Email in MemberPress?
The setting is buried two levels deep. Navigate to MemberPress > Settings > Emails. Scroll to the “Failed Transaction Notice” row.
You will see two toggles: one for the member and one for the admin. Enable both.
Inside that same row, click “Edit” to open the template editor. MemberPress gives you a subject line field and a body field with a small set of merge parameters such as {member_name}, {membership_title}, and {account_url}.
The account URL parameter is important because it links the member directly to the page where they can update their card. Without it, a member who wants to fix the problem has to find that page themselves, and most will not.
A minimal subject line that performs well in practice: “Your [membership name] payment needs attention”. Keep the body under 120 words. State what happened in one sentence, give them the link to update their card in the next sentence, and close with a clear deadline so the message carries urgency.
Telling someone their payment failed is table stakes. Telling them exactly what to click and what happens if they do not act within 48 hours is what actually recovers the member.
Why Isn’t the MemberPress Failed Payment Email Sending?
This is the most common support question on this topic, and it almost always comes down to one of four causes. Work through them in this order, because the first fix resolves the problem in the majority of cases.
- The toggle is off. MemberPress ships with the failed transaction notice disabled. Go to MemberPress > Settings > Emails and confirm both toggles are on. This takes 30 seconds to check.
- WordPress is using
wp_mail()without an SMTP relay. Shared hosting providers regularly blacklist PHP mail. Install an SMTP plugin such as WP Mail SMTP and connect it to a transactional mail service. Without this, emails either land in spam or never leave the server. - The transaction was not recorded as complete. MemberPress only fires the failed notice when a subscription renewal fails. A payment that never completed the initial checkout does not trigger the same hook. Check the transaction log under MemberPress > Transactions.
- Site migration broke the gateway webhook URL. If you migrated the site and the domain changed, Stripe or PayPal may still be sending webhooks to the old URL. Log into your gateway and update the endpoint to the new domain. The MemberPress webhook URL follows the pattern
yourdomain.com/?memberpress-listener=stripe.
If none of those apply, confirm the member’s email address is stored correctly under MemberPress > Members and test a manual email send using the WP Mail SMTP diagnostic tool.
What Should I Actually Write in the Failed Payment Email?
No official documentation covers this, which is why members slip away even when the email is technically sending. The goal of the first email is one action: get the member to click the account link and update their card. Everything else is noise.
A structure that converts reliably:
- Subject: “Your [Membership Name] payment didn’t go through”, plain language, no urgency theatrics on the first attempt
- Opening line: State the fact plainly. “We tried to renew your [Membership Name] subscription on [date] and the payment didn’t complete.”
- One sentence on consequence: “Your access will continue for the next 48 hours while we wait for you to update your details.”
- The link: A single, clear call to action pointing to the account page. “Update your payment method here.” No other links in the email.
- Closing: A low-pressure reassurance. “If you have questions, reply to this email and we will sort it out.”
The second email, sent 48 hours later if the payment is still unpaid, shifts tone slightly. Keep it short and raise the stakes honestly: access is about to suspend.
The third touch, if you build one, can include a discount or a personal note from the site owner. That third email is where Krom Automation earns its place, because you cannot time a manual email to fire 5 days after a specific member’s payment failure.
How Do I Build a Recovery Sequence With Krom Automation?
The MemberPress integration in Krom Automation exposes subscription and payment events as triggers. The failed payment trigger fires every time MemberPress records a failed renewal, and from that single trigger you can branch into a full sequence.
The free version of Krom Automation gives you the Send Email action, delay scheduling in minutes, hours, days or weeks, conditional branching with Yes and No paths, and merge tags to inject the member’s name and membership details into every message. That is enough to build a 3-touch recovery sequence without paying for anything.
Here is the workflow shape that recovers the most members in practice:
- Trigger fires immediately: MemberPress failed payment event received
- Action 1, instant: Send the first recovery email using the copy structure above
- Delay: 48 hours
- Conditional branch: Check whether the subscription is still in a failed state
- Yes path (still unpaid): Send the second email with a firmer tone and a specific deadline
- Delay: 72 more hours
- Yes path (still unpaid): Send a win-back email with a recovery offer or a personal message
- No path (payment recovered at any branch): Send a confirmation email and end the sequence
The delay scheduling documentation covers the exact options available and how to configure them on the canvas. The merge tags documentation shows which MemberPress fields you can inject into email subject lines and bodies.
A single email is a notification. A timed, conditional sequence is a recovery system. The difference in recovered revenue over 12 months is not marginal.
How Do I Send a Slack Alert When a Payment Fails?
Relying on an email to your admin address means you might not see a failed payment for hours. A Slack alert lands where your team already works.
The Krom Automation messaging integration covers Slack, Discord, Twilio, and Telegram. Slack alerts are a Pro feature.
The practical setup is a parallel branch on the same workflow: when the failed payment trigger fires, one branch sends the member email sequence and a second branch posts immediately to your Slack channel. The Slack message should carry the member’s name, the membership they hold, and the amount that failed.
A team that sees “Jane Smith, Pro Plan, $119 renewal failed” can make a personal follow-up call the same day. That human touch recovers members that automated emails miss.
If you run a high-volume membership site and want to see failure patterns over time, the Krom Automation analytics dashboard shows failure counts and execution trends. A workflow failing more than 10 percent of the time signals a configuration problem rather than a payment problem.
How Do I Build a Cancellation Win-Back Sequence?
Some members will not update their card in time and their subscription will cancel. That is not the end of the relationship. A win-back sequence, triggered when MemberPress records a cancellation following a failed payment, can recover 10 to 20 percent of those lapsed members over a 30-day window, based on industry benchmarks for membership sites.
The MemberPress integration trigger covers subscription cancellation events. Pair it with a 3-step win-back sequence:
- Day 1 after cancellation: A short email acknowledging the lapse, no pressure, just an open door. Include a direct re-subscribe link.
- Day 7: A value reminder email. What did they have access to? What are they missing? Keep it factual rather than emotional.
- Day 21: A time-limited offer. A discount coupon, a free month, or a content bundle. Make it specific and give it a hard expiry date.
The conditions and branching documentation shows how to stop the sequence automatically once the member re-subscribes, so you do not send a discount offer to someone who already paid.
If your membership site also runs on WooCommerce Subscriptions, the same pattern applies. See our guide on automating WooCommerce subscription renewal reminder emails for a parallel setup.
What Are the Real Limits of This Setup?
Honest constraints matter here. Three things can go wrong with this automation that the setup guides do not mention.
WP-Cron timing on low-traffic sites. Krom Automation uses Action Scheduler for background execution, which is the same queue system WooCommerce relies on. But Action Scheduler still depends on WordPress Cron firing. On a site that receives fewer than a few dozen visits per day, WP-Cron can run hours late.
A “48 hour delay” in the workflow may actually fire at 50 or 52 hours. For most membership sites this is acceptable. For high-stakes sequences where timing matters, configure a real server cron job to trigger wp-cron.php on a fixed schedule.
Gateway webhook failures are invisible to Krom Automation. If Stripe’s webhook to your site fails silently, MemberPress never sees the failed payment event, and the trigger never fires. Check your Stripe webhook dashboard monthly and confirm delivery success rates stay above 98 percent.
The free plugin does not include the visual email builder. The Send Email action in the free version sends plain HTML email. It works, and most recovery emails perform better in plain text anyway. The visual email builder is a Pro feature for teams that want branded, block-based email design matching their membership site’s look.
Cost Comparison: Manual Recovery vs. Automated Sequence
| Approach | Setup time | Ongoing time per 10 failed payments | Annual cost | Recovery touches per member |
|---|---|---|---|---|
| MemberPress email only, manual admin follow-up | 15 minutes | 2 to 3 hours | Staff time only, approx. $50 to $120/month at $25/hr for a busy site | 1 automated, 1 to 2 manual |
| Krom Automation free, 3-touch sequence | 30 minutes | Under 10 minutes (review logs only) | $0 | 3 automated, timed and conditional |
| Krom Automation Pro, sequence plus Slack alerts | 45 minutes | Under 10 minutes | Starts at $69/year for 1 site | 3 automated, plus team Slack alert for manual follow-up |
| Zapier plus ActiveCampaign (external tools) | 2 to 4 hours | Under 10 minutes | Zapier Professional approx. $240/year plus ActiveCampaign plan cost, as of September 2026 | 3 or more automated |
The Zapier route works but moves your member data and execution logs off your server. If GDPR compliance matters to your membership business, self-hosted automation is a material difference. Our article on self-hosted automation and GDPR covers what actually transfers to third-party services and what does not.
Which Krom Automation Plan Do I Actually Need?
| Feature | Free | Pro (from $69/year) |
|---|---|---|
| MemberPress failed payment trigger | Yes | Yes |
| Send Email action (plain HTML) | Yes | Yes |
| Delay scheduling (hours, days) | Yes | Yes |
| Conditional branching | Yes | Yes |
| Merge tags for member data | Yes | Yes |
| Execution logs and analytics dashboard | Yes | Yes |
| Slack / Discord / Twilio alert | No | Yes |
| Visual email builder (block-based) | No | Yes |
| Schedule trigger (daily digest of failures) | No | Yes |
| ActiveCampaign / FluentCRM / Mailchimp sync | No | Yes |
For most membership sites running under 500 active members, the free version builds a complete recovery sequence. Pro becomes worth the $69/year once you want Slack alerts on failures, branded email templates, or CRM sync so your marketing list stays clean when a member lapses. If you run sites for multiple clients, the Standard plan at $149/year covers 5 site activations.
The free plugin covers every part of the recovery sequence. Pro earns its cost the first time a Slack alert lets someone on your team make a personal call that saves a $200/year membership.
Before You Build: Test the Workflow First
Never push a recovery sequence live without dry-running it. Krom Automation includes a workflow simulator that executes the entire flow with zero side effects.
No emails send, no delays fire, no CRM contacts update. You see exactly which branch would run and which merge tags resolve to which values.
The workflow simulator documentation covers how to load a test payload that mimics a MemberPress failed payment event. Run the simulator before you toggle the workflow to active, and run it again any time you edit a branch condition. Our article on testing WordPress automations before they go live explains the full testing approach for sequences like this one.
Also from wpRigel
Pollify is our Gutenberg native poll, survey and quiz plugin. Polls are real blocks built inside the editor, so there are no shortcodes to paste and no separate configuration screen to learn. It is the fastest way to add a membership satisfaction survey directly inside a post or page.
Commandify is a command palette for the WordPress admin. Press Cmd or Ctrl plus K to jump anywhere in the dashboard, search members and orders, and run admin actions without clicking through menus. It is the only WordPress command palette with real WooCommerce order, product and customer management built in, which makes it worth knowing about if you run a membership site with a commerce component.
Our Verdict: Who Should Act on This and Who Should Not
If you run a MemberPress site with recurring subscriptions and you have not built a multi-touch recovery sequence, you are leaving a recoverable percentage of your churned revenue on the table every month. The free Krom Automation plugin closes that gap in under an hour of setup, with no ongoing cost and no member data leaving your server.
If your membership site has fewer than 50 active recurring members, the built-in MemberPress email plus a manual admin notification is probably enough. The complexity of a 3-touch automation is not worth maintaining below that threshold. Above 50 recurring members, the math flips: even recovering 2 additional members per month at a $10/month membership price exceeds the cost of Krom Automation Pro in the first year.
Download the free Krom Automation plugin from the WordPress.org plugin directory and build the first workflow today. Upgrade to Pro only when you need Slack alerts or branded email templates. The step-by-step workflow builder guide walks through the canvas from a blank trigger to a published workflow if this is your first automation.
See all Krom Automation plans and pricing, including the lifetime options that start at $199 for a single site.
Frequently Asked Questions
Does MemberPress retry failed payments automatically?
MemberPress itself does not control retry timing. Retry logic lives inside your payment gateway. Stripe retries on a schedule you configure in the Stripe dashboard, typically 3 attempts over 7 to 14 days.
PayPal handles retries inside its own subscription settings. MemberPress listens for the gateway webhook and reacts when each failure or success event arrives.
Can I send the failed payment email to a custom address instead of the site admin?
The admin notice in MemberPress Settings > Emails sends to the address set under WordPress Settings > General. To route alerts to a different address, such as a billing team inbox, use a Krom Automation workflow with a separate Send Email action pointing to whatever address you choose. This also lets you send to multiple recipients from one trigger.
Will Krom Automation stop sending recovery emails once the member pays?
Yes, if you build the workflow with a conditional branch that checks subscription status before each follow-up email. The conditions and branching documentation shows how to add a Yes/No check so the sequence exits cleanly when the payment is recovered, without sending a discount offer to a member who has already updated their card.
How do I sync lapsed MemberPress members to my email marketing list automatically?
Add a CRM or email marketing action to the same workflow that handles the failed payment trigger. The ActiveCampaign integration, the FluentCRM integration, and the Mailchimp integration all support adding a tag or moving a contact to a different list when a trigger fires. Tag the member as “payment-lapsed” at the moment of failure so your marketing list reflects the real subscription state.
Why did my members lose access immediately after a failed payment instead of getting a grace period?
MemberPress does not have a built-in grace period setting in the way some membership plugins do. Access suspension is controlled by your gateway’s retry window and the subscription status MemberPress receives via webhook.
If your gateway cancels the subscription after the first failed attempt, MemberPress marks the subscription as cancelled immediately. Extend the grace period by configuring more retries inside your gateway dashboard before it marks the subscription as failed.
Can I use this setup across multiple MemberPress sites for client work?
Yes. Krom Automation Pro Standard covers 5 site activations at $149/year, and the Enterprise plan covers unlimited sites at $299/year.
The workflow you build on one site exports as a portable JSON file that you can import on any other site running Krom Automation. The workflow settings documentation covers the import and export process.