Donation Page Launch Checklist for Agencies

First, confirm the money actually flows to the client

Everything else is cosmetic if the money lands in the wrong account. This is the part you check first and check twice.

1. Stripe is connected to the client’s own account. Not yours, not a "we’ll move it later" placeholder. Log into the dashboard and confirm the business name, the bank account on file, and the email on the account all belong to the client.
2. Payout schedule is set and the bank account is verified. A connected Stripe account with an unverified bank will happily take charges and then sit on the money. Confirm the first payout date.
3. The org’s legal name and EIN are on the account if they’re a registered nonprofit, so they can apply for the discounted processing rate later.

If you’re using an embed tool rather than raw Stripe, the same rule holds: the form should pay out to the client’s connected account directly, with no pooled middle account holding funds. That’s the model we built KindLumen around for exactly this reason — agencies shouldn’t be in the custody business.

Make a real donation, then refund it

This is the single highest-value thing on the list, and the one people skip because it costs a few dollars and feels silly. Do it anyway.

1. On the published page (not a staging preview), make a genuine $1–$5 donation with a real card.
2. Confirm the charge appears in the client’s Stripe dashboard within a minute.
3. Confirm a receipt email actually arrives — check spam too.
4. Confirm a donor record was created wherever the client will look for it.
5. Refund the gift from the dashboard and confirm the refund processes cleanly.

Test card numbers in a test environment are fine for catching obvious breakage, but they don’t prove the live keys are wired right. Live keys are a different switch, and "it worked in test mode" is how a lot of launches quietly fail. One real gift end to end is worth ten test-mode runs.

Confirm recurring giving actually recurs

Monthly donors are the most valuable thing most nonprofits have, so a broken recurring toggle is expensive in slow motion. You can’t wait a month to find out, so check the setup instead of the outcome.

• The monthly option is visible and easy to pick, not buried.
• Selecting monthly creates a subscription in Stripe, not a one-time charge that just says "monthly" on the button.
• The subscription shows the right amount and interval in the dashboard.
• There’s a sane plan for failed renewals — most tools retry and email the donor, but confirm it’s on.

If you want the deeper version of this for non-developer sites, collecting donations on a no-code website covers how recurring works when there’s no backend you control.

The donor-facing experience

Now the part the donor actually sees. Run each of these on a real phone, not a desktop browser shrunk down. Most giving happens on mobile, and a form that overflows an iPhone is a dead form.

1. Mobile layout: nothing overflows, the amount buttons are tappable, the keyboard doesn’t cover the submit button.
2. Suggested amounts are set with one sensible default highlighted, plus a working custom-amount field.
3. Thank-you page or message exists and says something human. Don’t leave the donor staring at a spinner or a blank page after they give.
4. Receipt email is branded with the client’s name and includes tax language — the org’s legal name, EIN, and a line about the gift being tax-deductible to the extent allowed. Get the client to sign off on this wording; it’s their compliance, not yours.
5. The form loads without shoving your layout down as it appears. Reserve space for it so the page doesn’t jump.

Tracking, accessibility, and fees

The stuff that doesn’t break loudly but bites later.

None of these are glamorous, but they’re the items that generate "why is our number off?" emails three weeks after launch.

The handoff: a one-page "who to call" doc

The launch isn’t done when the page goes live. It’s done when the client can run it without you. Write a single page — literally one page — and include:

• Where to log in to see donations and run a basic report.
• How to edit suggested amounts and form copy themselves, with a screenshot.
• Where receipts come from and how to resend one.
• Who to contact for a payment issue (the processor) versus a form issue (you or the tool), so they don’t email the wrong party in a panic.
• Their payout schedule and where the money lands.

This document is what turns a one-time project into a happy reference and, often, a referral. A client who can edit their own donation amounts at 9pm without a support ticket is a client who renews. For more on what they’re really judging you on, see what nonprofit clients actually want from a donation form.