Hypertune · email copy

Email copy: Failed payment

Failed payment · 25 September 2026

From Vinson · 25 September 2026 · part of the email plan. Sender, links and build rules for every email: build rules.

Now

Triggers on every failed payment, with no re-entry rule, so each Stripe retry starts it again. The flow logged 26,802 message recipients in 90 days. That is a send count across its messages, not 26,802 unique people.

Email	Sent (90 days)	Clicked	What it is
At once · "Ugh oh, your payment declined"	13,544	26 (0.2%)	Says "try re-entering a different card" but has no link to do it. The only links go to Discord, three times. Opens "It's APEX AKA Austin". Typos in the subject and the footer image ("It;s time to start winning agian").
Day 1 · "Some ways you can still enjoy Hypertune"	13,176	5 (0.04%)	"Feel like there's a mistake? Join Discord", over a screenshot of Discord.
Day 2 · "Enjoy a free month of Hypertune"	82	0	Only reaches people declined for insufficient funds. Old red design. Everyone else leaves the flow on day 2.

Klaviyo credits this flow with 176 payments ($1,258.40) against 31 clicks. The payment count exceeding the click count is consistent with Stripe's automatic retries succeeding; it does not show that the emails caused the payments.

It also catches trials whose first charge fails. 7,055 trial users have ended that way, and those people get the same Discord emails instead of a way to pay.

New

Trigger: Failed Payment. Re-entry: once per 30 days.
Who: only people who have paid before (flow filter: Successfully Paid at least once, all time). A trial whose first charge fails stays in the trial flow, which has its own email for it, so nobody gets both.
Exit: Successfully Paid.
Timing: day 0, 3, 7 and 14, matching Stripe's new 14-day retry window.
Branch: email 1 has two versions, chosen by the decline reason. Emails 2 to 4 are the same for everyone.
Settings: Smart Sending off, transactional.

Email 1 · Day 0, within the hour

*Version A · card declined, expired or other*

Subject: Your payment didn't go through
Preview: Update your card to keep Hypertune running.
Body:

> Hi there,

> Your latest Hypertune payment didn't go through. Usually that means the card has expired or the bank declined it.

> You can update your card in the billing portal. Nothing else changes: your plan, price and settings stay as they are.

> Austin

Button: Update payment method · billing portal

*Version B · insufficient funds*

Subject: Your payment didn't go through
Preview: We'll try again, or you can use another card.
Body:

> Hi there,

> Your latest Hypertune payment didn't go through because the card didn't have enough funds.

> We'll try it again over the next few days. If you'd rather use a different card, you can switch it in the billing portal. Your plan and price stay as they are.

> Austin

Button: Use a different card · billing portal

Email 2 · Day 3

Subject: Still can't take your payment
Preview: Update your card in the billing portal.
Body:

> Hi there,

> We still haven't been able to take your Hypertune payment. You can update your card in the billing portal, and nothing else about your plan changes.

> Austin

Button: Update payment method

Email 3 · Day 7

Subject: Action needed to keep your plan
Preview: Update your card before your plan ends.
Body:

> Hi there,

> We've tried your card several times. If the payment stays unpaid, your plan is due to end on {{ person.plan_end_date }}.

> Update your card now to keep it active. If the plan ends and you rejoin later, the available price may be different.

> Austin

Button: Keep my plan · billing portal

Email 4 · Day 14

Subject: Action needed for your plan
Preview: Update your card to keep Hypertune active.
Body:

> Hi there,

> Your Hypertune payment is still unpaid and your plan is due to end. Update your card now to keep it active.

> Austin

Button: Keep my plan

Build notes:

Branch on the Reason property of Failed Payment for versions A and B.
Delete the day-1 Discord email, the day-2 split and the free-month test (all three versions).
Needs Kamil: the billing portal link; Stripe retries to 14 days with Smart Retries on; Stripe's own failed-payment emails off on go-live day.
Confirm with Kamil before go-live: the exact event that marks the plan ended on day 14, the plan-end date property, and whether a successful card update during the retry window always preserves the current price.