BillingWebhookKit

Lemon Squeezy download email not received

A missing download email should not turn into a public private-link leak or duplicate delivery. Use a small support runbook that proves the order is paid, resends safely, and records delivery evidence.

Generate delivery emails Review delivery policy

Support triage checklist

Paid order state

Confirm the order is paid, the product or variant matches the expected digital kit, and the buyer email matches the support request.

Delivery log

Check whether the webhook or delivery job recorded a sent email, private ZIP delivery, checksum, and template version.

Safe resend

Use a private support channel for resend links. Never paste private ZIP links, license keys, API keys, or customer data into public issues.

Refund boundary

Separate spam-folder issues, typo corrections, duplicate purchases, broken archives, and genuine delivery failure so refunds stay consistent.

Resend evidence record

Keep the record short enough for support but complete enough for launch review. Do not store the private download URL in public artifacts.

{
  "order_state": "paid",
  "variant_match": true,
  "buyer_email_checked": true,
  "delivery_channel": "private_support_email",
  "zip_sha256": "public-manifest-checksum",
  "resend_reason": "buyer did not receive original email",
  "public_safe": true
}

Buyer-facing reply shape

  1. Acknowledge the missing email without exposing order details publicly.
  2. Ask the buyer to reply from the purchase email or provide the Lemon Squeezy order reference privately.
  3. Confirm paid state and resend the private download link through the approved private channel.
  4. Include checksum verification and support scope so the buyer can confirm the archive is intact.
  5. Record whether the case was resend, duplicate purchase, broken archive, or refund review.

FAQ

What should a seller check when a Lemon Squeezy download email is not received?

Verify paid order state, product or variant match, buyer email, delivery log, checksum evidence, and whether the issue is spam filtering, typo, duplicate purchase, broken archive, or a real fulfillment failure.

Should private download links be posted in public support threads?

No. Public support threads should use order references, checksum evidence, and safe status notes. Private ZIP or license links should only be sent through the approved private support channel after paid-state verification.

Turn delivery support into buyer trust

The free delivery email generator helps draft resend and support replies. The CNY 69 Pro Kit is for teams that want delivery evidence, replay-safe fulfillment tests, support templates, and rollback notes already packaged.