For the complete documentation index, see llms.txt. This page is also available as Markdown.

Delivery Strategy

FlyCode's recovery email delivery strategy: local-time sending, faster action-specific cadences for hard declines, CAN-SPAM and GDPR compliance, how it differs from Stripe and ProfitWell emails, and 9

When and how a recovery message is delivered matters as much as what it says. FlyCode's delivery strategy is built on behaviour, timing and rules rather than a fixed drip.

What do you mean by "local time delivery"?

FlyCode detects each customer's time zone from the card and billing data and schedules sends for the hours when that customer is most likely to open and act, typically mid-morning local time. A renewal that fails overnight in the customer's region is not announced with a 2 a.m. email that gets buried under the morning's mail. Local-time delivery applies to every message in the sequence and to SMS.

How does FlyCode handle hard declines?

For hard declines the customer must act, so the strategy changes. FlyCode makes the cadence faster than for soft declines, uses dynamic templates with the specific action required ("update your card", "verify with your bank"), links to a one-click payment update page, and sequences follow-ups based on the customer's past engagement, so a customer who opened but did not act gets a different next message from one who never opened. Where a backup payment method is on file, FlyCode charges it first and only messages if that also fails. See Hard Declines & Backup Logic.

Is this compliant with privacy and email laws?

Yes. FlyCode follows CAN-SPAM, GDPR and the other major privacy and email regulations by default. Recovery emails are transactional messages about an existing paid relationship, which is the category these laws treat most permissively, but FlyCode still applies the safeguards: accurate sender identity, your physical address where required, no misleading subject lines, processing of customer data only for the purpose of recovering the payment, and data handling under your data processing agreement. Sending from your authenticated domain also satisfies the sender authentication requirements that mailbox providers now enforce.

How is FlyCode's outreach different from Stripe or ProfitWell emails?

FlyCode's communications are driven by models that coordinate emails with retries. It does not email immediately after a soft decline (that reduces voluntary churn), it runs a distinct schedule for hard declines, it sends at the customer's local time, and it uses plain transactional templates from infrastructure with a 95-plus sender score. Stripe Billing's default recovery settings send an email every time a payment is retried, so a customer can receive up to eight emails for one invoice. ProfitWell applies basic per-retry email logic.

FlyCode
Without FlyCode (Stripe defaults)

Number of emails

Model-based, coordinated with retries

One on every retry, up to 8

Soft declines

Retries first, email only if retries fail

Email at each attempt

Timing

Customer's local time

Whenever the retry runs

Format and deliverability

Plain transactional, 95-plus sender score

Varies

Multiple contacts in a B2B account

Can message different users in the customer's organization

Single billing email

Payment page

Processor's native page with all local payment options

Native page (Stripe) or custom page with limited options (ProfitWell)

Analytics

Full-funnel view by customer and by email

Basic

What does deliverability look like?

Emails are transactional-only and typically achieve a sender score of 95 or higher. FlyCode uses transactional sending infrastructure rather than a marketing platform, enforces SPF and DKIM alignment with your domain, and optimizes the sending subdomain and IP reputation. Open, click and payment-update rates are visible per email in the dashboard so you can see which step in the sequence recovers the most.

Last updated

Was this helpful?