Guides / How to build

How to Build a Nonprofit Donation Website

Build a nonprofit donation website: one-off and monthly gifts with Stripe, receipts, donor records, impact pages, and when a donation platform is simpler.

Mythex Team · 2026-09-29 · 6 min read

A nonprofit donation website tells your story, shows the difference a gift makes, and takes one-off and monthly donations through a secure payment provider such as Stripe. Behind it you need a record of every donor and gift, receipts that meet your local rules, and an easy way for monthly donors to change their gift. You can build this with an AI app builder, but for many small organisations a hosted donation platform is the quicker start — this guide covers both honestly.

What a donation site has to do

A good donation site does four jobs:

1. Make the case. Who you help, how, and why now. Real photos, real numbers from your own work, and a short story beat a long mission statement.
2. Take the gift with as little friction as possible. Suggested amounts, a one-off / monthly switch, and a fast checkout that works on a phone.
3. Say thank you and issue a receipt. Immediately, by email, with whatever details your country requires.
4. Show where the money goes. Impact pages, annual reports and financial summaries build the trust that brings donors back.

Everything else — events, volunteer sign-ups, newsletters, a shop — can come later.

Pages you need

The donation flow

The form

• Suggested amounts with a line on what each achieves ("£25 pays for a week of meals") — but only if the claim is true for your work.
• A custom amount field with a sensible minimum.
• One-off or monthly, clearly labelled. Many organisations default to one of them; test which your donors prefer rather than assuming.
• Optional extras: a fund or campaign to direct the gift to, a dedication, and a checkbox for anything your tax rules require (for example a Gift Aid declaration in the UK).
• Contact details only as far as you need them: name and email for the receipt; address only if your receipts or tax schemes require it.

Taking the payment

Don't collect card numbers on your own pages. Use a hosted checkout from the payment provider:

• One-off gifts go through a checkout for the chosen amount.
• Monthly gifts are subscriptions. Stripe Checkout supports both one-off payments and subscriptions.
• Confirmation by webhook. The provider calls your app when a payment succeeds (and each month when a recurring gift renews or fails). Record the gift then — not when the donor lands on the thank-you page. Our guide to adding payments explains webhooks and test mode.
• Let donors manage recurring gifts. A hosted customer portal from the provider lets them update their card or cancel without emailing you.

Receipts

Send an email receipt as soon as the gift is confirmed, and store a copy. What it must say — organisation details, registration number, amount, date, whether anything was received in return — depends on your country and status. We can't advise on that; check with an accountant or adviser, then give the AI the exact wording.

Donor records

Every gift should end up in a database table you can search and export:

• Donors — name, email, address if collected, communication preferences, consent date.
• Gifts — donor, amount, currency, date, one-off or recurring, campaign, payment reference, receipt sent.
• Recurring plans — donor, amount, status, start date, last payment.

Add a private admin area, behind login, where staff can see totals by month and campaign, look up a donor, resend a receipt and export to CSV for your accountant. If fundraising grows into relationship management — major donors, notes, follow-ups — that's a CRM; see how to build a CRM.

Consent and privacy

Donor data is personal data. Record marketing consent separately from the donation itself, don't pre-tick boxes, keep only what you need, and restrict the admin area to people who need it. Data protection rules differ by country, so check what applies to you.

A first prompt that works

Build a donation website for a small food bank called Northside Pantry. Pages: home with our mission and a big Donate button, Our Work with three programme sections, About with our trustees and charity number, Transparency with links to annual reports, and Donate. The donate form offers £10, £25, £50 and a custom amount, a one-off or monthly choice, an optional campaign dropdown, and name and email. Payments use Stripe Checkout with my own keys from project secrets; monthly gifts are Stripe subscriptions. Record gifts from Stripe webhooks, not the thank-you page. Send an email receipt after each confirmed gift. Staff log in to an admin page showing gifts by month and campaign with CSV export. Warm, trustworthy design, fast on phones.

Build steps

1. Content pages first. Get the story, photos and structure right on the home, work and about pages.
2. Donate form on test mode. Add your provider's test keys as secrets and make test donations, one-off and monthly.
3. Webhooks and records. Confirm each test gift appears in the admin, and a failed test card doesn't.
4. Receipts. Add the email provider, send yourself receipts, and check the wording with your adviser. See sending emails from your app.
5. Recurring management. Change and cancel a test monthly gift through the portal link and check your records update.
6. Security and access. Make sure admin pages need login and donor data isn't exposed anywhere public. Run through the security checklist for AI-built apps.
7. Go live. Switch to live keys, make one small real donation yourself, refund it, then publish on your own domain.

Common mistakes

• Trusting the thank-you page. Recording gifts on redirect creates phantom donations. Use webhooks.
• Too many form fields. Every extra field loses donors. Ask only for what the receipt and your tax schemes require.
• Hiding monthly giving. Monthly donors are often the most valuable; make the option visible.
• Unverified impact claims. "£25 feeds a family for a week" must be something you can stand behind.
• No way to cancel. Donors who can't easily stop a monthly gift complain to their bank instead.
• Live keys in the code. Keys belong in secrets, never in the page source.

Costs

When a donation platform is the better choice

Hosted donation platforms and fundraising tools give you a form, recurring gifts, receipts and donor lists in an afternoon, with no code to maintain. Choose one when:

• You have no one to look after a custom site.
• You need peer-to-peer fundraising, text-to-give, or integrations with an established fundraising CRM.
• You want to start taking donations this week.

Build your own when platform fees or donor tips bother you at your volume, when you want the donation experience fully inside your own site and brand, or when giving is connected to other things you run — events, memberships, volunteer schedules. For event ticketing alongside donations, see how to build an event registration site.

Building it with Mythex

On Mythex you describe the site in chat and see it in a live preview; it adds a database for gifts and donors when needed. Payments use your own Stripe account and keys stored as project secrets — the Stripe recipe walks through it, and Mythex has no built-in payments product of its own. Publish to a mythex.ai address, or your own domain on Pro. For a starting point, see the charity donation site template or the AI nonprofit website builder.