diff --git a/docs/LAUNCH_READINESS.md b/docs/LAUNCH_READINESS.md
index 775b93c..f2cdec5 100644
--- a/docs/LAUNCH_READINESS.md
+++ b/docs/LAUNCH_READINESS.md
@@ -60,6 +60,9 @@ Applies when the site is connected to Netlify / production hosting. Nothing here
 - [ ] Set `NUXT_HELCIM_MONTHLY_PLAN_ID=50302` in production env.
 - [ ] Set `NUXT_HELCIM_ANNUAL_PLAN_ID=50303` in production env.
 - [ ] Decide on the 6 failing tests in `tests/server/api/helcim-payment.test.js` — either fix or consciously accept. Not launch-blocking, but pre-existing red tests tend to mask new regressions.
+- [ ] **Run `node scripts/reconcile-helcim-payments.mjs --apply` against prod Mongo AFTER the new code serves traffic** to backfill Payment records for pre-existing members. Idempotent (unique `helcimTransactionId`); safe to re-run as a nightly reconciliation job post-launch.
+- [ ] **Helcim dashboard: disable the default payment-confirmation email for plans 50302 + 50303.** We send our own CRA-safe confirmation via Resend (`server/emails/paymentConfirmation.js`) triggered from `upsertPaymentFromHelcim`; leaving Helcim's default on = duplicate emails.
+- [ ] **Run one real test charge on staging** via the cloudflared tunnel and verify (a) a Payment doc in Mongo with `amount`, `paymentType`, `status: 'success'`, and (b) exactly one CRA-compliant confirmation email (charity name + "not an official donation receipt" disclaimer; no banned assertive phrasing).
 
 **Env vars required in production (reference):**
 - `MONGODB_URI`