Lemon Squeezy subscription_payment_failed

Lemon Squeezy fires subscription_payment_failed when a recurring subscription renewal charge fails. Usually because the card on file was declined, expired, or hit an issuer block. It can fire multiple times across the retry window as Lemon Squeezy re-attempts the charge.

order_failed fires for any failed Lemon Squeezy order, including initial purchases and one-time charges. subscription_payment_failed is subscription-specific and fires only on renewal failures. For SaaS dunning, subscription_payment_failed is the event you want.

The payload includes the subscription ID, customer ID, customer email, the failed invoice details, the failure reason from the payment processor, and the next retry timestamp. Use the subscription ID to dedupe across multiple retry events.

Yes. Lemon Squeezy automatically retries failed renewal charges over a multi-day window. Your job in dunning is to layer email follow-up on top so the customer knows to log in and update their card. Lemon Squeezy's automatic retry can't fix an expired card on its own.

Yes. Without dedupe by subscription ID, you'll send the customer one 'your payment failed' email per retry attempt, which can mean 3-4 nearly identical emails in a few days. The right pattern: trigger your dunning sequence on the first event, then suppress subsequent events for the same subscription ID until either subscription_payment_success or subscription_expired fires.

Lemon Squeezy's customer portal update-payment-method URL. The customer logs in and updates their card without leaving the LS ecosystem. Generic 'click here to pay' links break trust because customers don't know what site they're being sent to.

ChurnNote registers a webhook on your Lemon Squeezy store, dedupes subscription_payment_failed events by subscription ID, and sends a 3-email recovery sequence with the LS customer-portal update link. The sequence stops automatically when subscription_payment_success fires.