Donation Pages That Convert: A Guide for Nonprofits
A working guide to the donation page: suggested amounts, an honest monthly option, the fields you can drop, wallets, receipts donors can use, tracking that survives closed tabs, and protection against card testing.

A donor who reaches your donation page has already decided to give. From that moment the page can only lose the gift: by asking for too much, by looking unfamiliar at the point of payment, or by breaking on a phone. A good nonprofit donation page takes those reasons away one at a time.
We take the decisions in the order a donor meets them, then the parts they never see: receipts, tracking and fraud protection. There are no conversion figures here, because the only numbers worth acting on are your own. Fundraising and tax receipt rules differ by country, and sometimes by state or province, so treat the points on receipts and consent as questions for your accountant or regulator.
Suggested amounts with a sensible default
An empty amount box makes the donor work out what is appropriate. Three or four suggested amounts and an "other" field do that for them. Take the amounts from your own giving history: export last year's online gifts, find the typical single gift, and make it the second button, with one option below and one or two above.
Preselect one amount. Add impact text ("Pays for a week of school meals for one child") only if it is true and you can keep it current. Give the custom amount field inputmode="decimal" so phones show a number pad, and set a minimum amount, which also protects against the fraud described later.
Make monthly giving a clear choice, not a trick
Put a one-time and monthly switch directly above the amounts, with the current selection obvious. When the donor chooses monthly, show a lower set of amounts and change the button to say what will happen: "Give 15 a month". A monthly option that is selected by default, or tucked into a small checkbox, produces donors who did not mean to subscribe. They cancel, complain or dispute the charge with their bank, and disputes cost you fees.
State the charge date and how to stop, then make stopping possible without a phone call: a link in every receipt email to a page where the donor can change the amount, update the card or cancel. Some jurisdictions regulate how recurring charges are disclosed and cancelled, so have the wording checked.
Recurring gifts fail quietly when cards expire. Retry failed payments on a schedule and email the donor a link to update their card, as we explain in reducing subscription churn from failed payments.
Cut the form to what the gift and the receipt need
Every field is a small reason to stop. Justify each one against two tests: is it needed to take the payment, and is it needed to issue the receipt?
| Field | Keep it? | Why |
|---|---|---|
| Name | Yes | Needed on the receipt |
| Yes | Where the receipt and the link to manage the gift go | |
| Payment details | Yes | In the payment provider's own fields, so card data never touches your server |
| Postal address | Only when required | Some tax schemes need it, and some card checks use the postal code |
| Phone number | No, or clearly optional | Not needed for the gift, and donors assume it means calls |
| Consent to updates | Yes, as a separate choice | Never bundled with the gift, worded to match your privacy law |
Show conditional fields only when they apply. In the UK, for example, a Gift Aid declaration needs the donor's full name and home address and their confirmation about the tax they have paid. Those fields should appear when the donor ticks the Gift Aid box, not before.
Do not require an account. Mark up fields with the standard autocomplete values (name, email, postal-code) so browsers fill them in, and show errors beside the field in plain words.
Offer wallets and keep the payment step familiar
Typing a card number on a phone is the hardest part of giving. Apple Pay, Google Pay and PayPal replace it with a confirmation the donor already trusts, and with a payment provider's embedded components they mostly need configuration, not code. With Stripe's embedded fields, for example, each domain and subdomain that shows Apple Pay has to be registered in the dashboard first. Apple also asks nonprofits to be approved before they accept donations through Apple Pay, by a route that depends on the country. The requirements are on Apple's page for nonprofits.
Keep the donor on a page that looks like yours. Being sent to an unfamiliar domain to enter card details is where trust drops, so use an embedded form or a hosted page on your own subdomain.
Around the form, show what a cautious person looks for: the organization's legal name and registration number, a sentence on how gifts are used, and a real contact. Check that the name on the donor's card statement will match the name on the page.
Send receipts donors can use at tax time
Confirm the gift on screen and by email within seconds. A receipt normally carries the organization's legal name and registration number, the donor's name, the amount and date, a unique receipt number, and a statement of whether the donor received anything in return.
What makes a receipt valid for tax purposes is set by each country. In the United States, for example, a donor needs a written acknowledgment from the charity to claim a deduction for any single gift of $250 or more, and it has to say whether goods or services were provided. Other countries prescribe wording, a serial number or a registration number. Your accountant decides the content. The website's job is to store the fields it needs and produce the document the same way every time, including a year-end summary for monthly donors and a correction when a gift is refunded.
Track gifts from the payment provider, not the thank-you page
Many sites count a donation when the thank-you page loads. That misses donors who close the tab after paying and every recurring charge after the first, since no page loads for those at all.
The reliable source is the payment provider's webhooks: server-to-server messages sent when something happens to a payment. On Stripe the ones that matter for donations are:
payment_intent.succeededfor a completed one-time gift;invoice.paidfor each monthly charge;invoice.payment_failedwhen a recurring payment is declined;customer.subscription.deletedwhen a monthly gift ends;charge.refundedwhen money goes back.
Have the website record each event and pass it to your donor database or CRM, so finance and fundraising look at the same numbers. For analytics, send a purchase event with the amount, the currency and a unique transaction_id, and store the campaign parameters from the donor's arrival with the gift, so you can tell which appeal produced it. If payment happens on a different domain, set up cross-domain measurement, or every gift will appear to come from the payment page.
Protect the form from card testing
Donation forms are a favorite target for card testing, where criminals run stolen card numbers through a form to see which still work. A donation form takes any small amount from anyone, with no account, which is what they need. The signs are a sudden burst of small payments, most of them declined, with nonsense names. The results are disputes, fees and more declines for genuine donors afterwards. Defend in layers:
- use the provider's current hosted or embedded payment form, which carries its own protections, not an old custom integration;
- set a minimum gift amount;
- limit how many payment attempts one visitor can make in a short time;
- add a CAPTCHA that appears only when behavior looks automated;
- refund fraudulent payments that got through before the cardholders dispute them.
Stripe's guide to protecting against card testing describes the pattern and the controls, and most of it applies whichever provider you use.
Which tools to build a nonprofit donation page with
A small organization can go a long way with a hosted form from its payment provider or a WordPress donation plugin such as GiveWP. With their add-ons, these cover amounts, recurring gifts, wallets and basic receipts. Start there and measure completion on your own page before spending more.
Custom work earns its cost when the page has to do something the standard tools do not: write gifts into your CRM with campaign codes, issue receipts in a format your tax authority prescribes, or handle several currencies or legal entities. That is form development and CRM integration more than design, and the risk sits in the payment flow, so use someone who has done it before. Our page for nonprofits and associations describes the work we take on, and landing page structure covers the layout itself.
Frequently asked questions
Should we ask donors to cover the processing fee?
Offer it as an optional checkbox that states the exact amount it adds, unticked by default, so the total never changes without the donor choosing it. Ask your accountant how the extra amount should appear on the receipt, because the tax treatment varies.
Is a hosted donation platform better than a form on our own site?
A hosted platform is faster to launch and takes payment security and updates off your hands. A form on your own site gives you control over design, data and how gifts reach your CRM. An embedded form from a payment provider is a common middle route.
Do monthly donors need an account with a password?
No. A secure link sent to their email address, leading to a page where they can change the amount, update the card or cancel, does the job. Several payment providers offer a hosted page for this, so you need not build a login system.
Add worldwincoder.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.
