If you run a UK charity, you already know Gift Aid can add 25p to every £1 donated at no extra cost to the donor. What’s less obvious is how much of that uplift depends on how your website’s donation form is built. A poorly designed Gift Aid checkbox, a missing declaration, or an unclear form can mean donors skip it entirely – leaving real money unclaimed.
This guide covers what charities and their web developers need to get right.
What Gift Aid Actually Requires From Your Website
For a donation to qualify for Gift Aid, the donor needs to make a valid declaration confirming they’re a UK taxpayer and understand they need to have paid enough tax in that year to cover the amount being claimed. Your website’s job is to capture that declaration clearly, at the point of donation, and store it in a way that’s retrievable if HMRC ever asks for records.
In practice, this means your donation form needs:
- A clearly visible Gift Aid opt-in (not buried in fine print or a secondary screen)
- Plain-language wording of the declaration itself, not just a vague “add Gift Aid” checkbox
- Capture of the donor’s full name and home address (required for a valid declaration – this trips up a lot of forms that only ask for email)
- A confirmation the donor is a UK taxpayer
- Secure, retained records of each declaration, tied to the donation record
Common Technical Mistakes
Having audited and rebuilt several charity donation flows, the same issues come up repeatedly:
The checkbox is there, but the address fields aren’t. A Gift Aid declaration isn’t valid without a name and address, but a lot of quick-build donation forms only ask for what the payment gateway strictly requires (name, email, card details). If Gift Aid is ticked, the form needs to expand to capture the additional required fields, not just fire a flag to your CRM.
Gift Aid status isn’t recorded against the transaction. It’s common to see the payment go through cleanly, but the Gift Aid declaration data lives in a separate, disconnected record – or nowhere at all. Every claimable donation needs its declaration data properly linked, exportable, and ready for your HMRC submission (whether that’s via the Charities Online service or a bulk claim spreadsheet).
No annual reminder for regular/recurring donors. If someone sets up a recurring monthly gift, their Gift Aid declaration should be treated as ongoing – but it’s good practice (and increasingly expected) to periodically confirm they’re still a UK taxpayer, especially if personal circumstances may have changed.
Mobile forms hide the Gift Aid section. On smaller screens, Gift Aid is often the first thing collapsed or scrolled past. Given how much charity donation traffic now comes from mobile, burying this costs real revenue.
What Good Implementation Looks Like
A well-built Gift Aid flow on a charity website should:
- Present the Gift Aid option clearly during the donation process, not after
- Explain the benefit in one plain sentence (“Add 25p to every £1 at no cost to you”)
- Dynamically show the required address fields only when Gift Aid is selected, keeping the form short for donors who don’t need them
- Store the declaration with a timestamp, linked to the specific donation
- Make declarations exportable in a format ready for HMRC submission
- Work identically well on mobile as on desktop
A Note on Platforms
Whether you’re on WordPress with a donations plugin, a dedicated platform like Donorfy or Enthuse, or a custom-built form, the underlying requirements above don’t change – only the implementation does. WordPress charities in particular should check that their chosen donation plugin actually stores full Gift Aid declaration data, rather than just tagging a donation as “Gift Aid eligible” with no retrievable record behind it.
If you’re planning a website rebuild or reviewing your current donation flow, it’s worth an audit specifically focused on Gift Aid capture – it’s a small piece of the build that has an outsized effect on funds actually claimed.