Charity Donation Pages That AI Agents Can Actually Complete
Charities raise a large share of their income online, and for many that income is dominated by recurring monthly donations. Increasingly, donors ask AI agents to set up or modify these gifts on their behalf. When the donation page is built for visual impact rather than form structure, those agents fail at the most important moment.
The Typical Starting Point
A common donation page is a three-step wizard: choose your amount, enter your details, and complete payment. Pages redesigned for visual impact often run into the same three problems.
The amount selection uses custom-styled radio buttons. The actual input elements are hidden with display:none and replaced with large, branded card-like divs that highlight on click. When a donor selects "£25 per month," the visual feedback is clear. But agents cannot interact with the hidden radio buttons, and clicking the visual cards does not reliably toggle the underlying form state.
The details step collects name, email, address, and Gift Aid declaration. The form fields use custom placeholder text that disappears on focus, with no visible labels. Several fields have client-side validation that only triggers on blur events, which agents often do not fire because they move through fields programmatically.
The payment step is usually the biggest blocker. Many charities use an embedded payment provider iframe that loads a completely separate domain. The iframe contains its own form fields for card details. Agents cannot interact with the contents of a cross-origin iframe at all, so an agent-initiated donation attempt dies at this step. In an Agent Checker audit, this single barrier is often enough to stop every agent before payment.
What to Change
Visible, native form controls. Replace the custom amount cards with native radio buttons, styled with CSS but remaining fully functional as standard form elements. Give each radio button a visible label showing the amount and frequency, and use a standard number input for a custom amount option. The visual design can stay attractive, just built on top of real form elements rather than replacing them.
Proper field labelling. Give every form field a visible label element associated via the for attribute. Remove placeholder text from required fields and use it only as supplementary hints. Add ARIA labels where the visible label needs additional context for programmatic access, such as "Monthly donation amount in pounds."
Payment redirect instead of iframe. Replace the embedded payment iframe with a redirect flow. After completing the details step, send donors to the payment provider's hosted payment page with all relevant data passed as URL parameters, then return them to a confirmation page on your own domain. This works for agents because the payment page is a full, interactive page rather than a sandboxed iframe. Most payment providers support this flow natively; the iframe embed is usually chosen only because it looks more integrated.
URL-based step tracking. Give each step its own URL: /donate/amount, /donate/details, /donate/payment, /donate/confirmation. This follows the same form design principles that work for any multi-step process. Agents can track progress, retry individual steps, and verify completion.
Gift Aid as a clear question. Restructure the Gift Aid declaration, often a dense paragraph with a checkbox buried at the end, as a clear yes/no question with the checkbox prominently placed and properly labelled: "I am a UK taxpayer and I want this charity to claim Gift Aid on my donation."
What Improves
The decisive change is the payment step. Once it is a real page rather than a cross-origin iframe, agent-initiated donations can complete at all, where before they could not. Native amount controls and labelled fields remove the earlier traps, so agents reach payment more often.
There are knock-on benefits in the data agents capture. Because the Gift Aid declaration becomes a clear yes/no question, agents reliably tick it when the donor confirms they are a UK taxpayer, whereas human donors sometimes scroll past it or are put off by dense legal text. Recurring donations set up through agents also tend to run for a long time once established, which suits charities well.
What Other Charities Should Know
The iframe payment problem is widespread in the charity sector. Many donation platforms default to iframe embeds because they keep donors visually on the charity's site. But this creates an impenetrable barrier for agents. If your payment provider offers a redirect flow, switch to it. The slight visual disruption is worth the gain in agent compatibility.
The custom-styled form control problem is equally common. Designers understandably want donation pages to feel warm and branded rather than like a government form. But you can achieve branded styling on native form elements. The moment you hide the real input and build a visual replacement, you break agent interaction.
Charities have a particular incentive to get this right. Donors who use agents to manage their giving tend to set up recurring donations and leave them running. They are lower-maintenance, higher-value supporters. Making it easy for an agent to complete a donation means making it easy for that donor to keep giving.