Treat clarity as part of the donation experience
A donation form asks someone to make several decisions in a small space. How much should they give? Is it a one-time gift or a recurring commitment? What will it support? What happens when they press the payment button? A form becomes difficult when those decisions are hidden, repeated or explained differently at each step.
The goal is not to remove information a donor needs. It is to present the right information at the moment it matters. Compact frequency choices, visible custom amount entry and a clear designation can reduce unnecessary navigation while preserving the donor’s ability to make a deliberate choice. Avoid claiming that a design change guarantees more donations; evaluate whether people can understand and complete the flow.
In EvidofOS, organization defaults and campaign overrides help keep forms consistent without forcing every campaign to use identical settings. Start by deciding what the campaign actually needs, then preview the result. Configuration is only useful if the public donation box displays the intended choices and carries them correctly into payment.
Choose amounts that are easy to interpret
Preset amounts give donors a quick way to choose, while custom entry lets them use a different amount within supported limits. Review the actual denominations saved for the campaign. If your organization intends a set such as 25, 50, 100, 250, 500 and 1,000 in its supported currency, confirm that the public form shows that set rather than assuming a default has changed everywhere.
Keep the custom amount field visible. A donor should not have to click an unexplained Other button and discover another hidden input before continuing. Check the currency label, amount validation and selected state. If a donor enters a custom amount after choosing a preset, the review step should make the effective amount unambiguous.
Be careful when connecting amounts to impact language. “This amount helps support our program” differs from “this amount guarantees a particular outcome.” Use an exact unit-of-service claim only when the organization can explain the calculation and its limitations. The form should make giving understandable without presenting an unsupported price tag for a human outcome.
Offer recurring choices with a clear explanation
Organizations may want one-time, monthly, quarterly or annual gifts, or a selected combination. Choose the options that fit the campaign and payment capabilities, and review them in a compact layout that remains usable on mobile. A single-row design should not make labels unreadable or touch targets difficult to select.
Explain recurring support in relation to the work. An ongoing program may benefit from a predictable pattern of support, while a time-bound project may require a different explanation. Do not assume a donor understands the relationship simply because Monthly appears beside One-time. The selected frequency should remain visible when the donor reviews the gift and reaches secure payment.
A successful first payment is not the same as all future installments being received. Recurring transactions can have later failures, changes or cancellations. Use the actual payment and subscription records when reviewing results. For donor communication, distinguish the intended commitment from money already received, and direct financial questions to the authorized workflow rather than promising a change that has not been made.
Make the designation mean what the page says
A campaign page tells a particular story and asks for support for a particular purpose. Its default designation should reinforce that story. In EvidofOS, Where Needed Most on a campaign page supports that campaign’s greatest need. It does not silently redirect the gift to an organization-wide general fund.
Write a concise explanation of the designation beside the form. A donor should understand what flexibility the campaign needs and how the selected purpose relates to the work. Avoid vague wording that lets two colleagues describe the same gift in incompatible ways. If the campaign is intended to support a specific project, review its story and designation together.
When another eligible campaign is explicitly opted into cross-campaign giving, it may appear as an alternative. Explain its purpose clearly so the donor can make a conscious choice. Do not opt existing campaigns in by assumption, and do not describe the resulting gift as supporting the original page’s campaign if the donor selected a different destination. The transaction record and the donor’s choice should agree.
Keep independent campaigns independent
An organization can run several campaigns for different programs, projects or periods. Each campaign should have its own published page, evidence, images and purpose. A designation dropdown is a way to offer a permitted alternative at checkout; it is not a reason to combine all campaign narratives into one page.
This distinction also matters for Engagement. Select one primary donation campaign for an Engagement campaign and verify the actual URL. A post about a project should not send a supporter to an unrelated fundraising purpose without explanation. If a QR code is included in a graphic, scan the generated image and inspect the destination before approving it.
Review the implications of any campaign change. If a campaign is closed, revised or no longer suitable as a cross-campaign destination, inspect the relevant configuration and public forms. Keep the public choices current. A donor should not encounter an appealing designation whose page or checkout is no longer ready, and staff should not need to infer the donor’s original intention from a confusing mixture of campaign names.
Carry the donor’s choices through inline checkout
A donor who has chosen an amount, frequency and purpose should not feel that the next step starts a different transaction. The review and secure-payment stages should preserve those choices and explain what remains to be done. EvidofOS uses an inline flow so the campaign remains the context for payment, rather than requiring an unrelated browsing journey and return.
Inspect the complete sequence, including any optional contribution toward processing or platform costs. The donor should be able to see the selected values before completing payment. Do not describe every displayed total as money available for program spending without considering the actual transaction breakdown. Keep the organization statement and relevant identification details accurate and reviewed.
If secure payment reports an error, check the reference and connected-account readiness. Avoid repeatedly submitting when the outcome is uncertain. The nonprofit’s own Stripe connection must be ready for the intended environment. Test-mode validation belongs in the sandbox; it does not prove that a separate live account has completed its requirements.
Review the form as a donor and as an operator
Before publishing, use a simple evaluation script. Select every allowed frequency. Try a preset and a custom amount. Change the designation where alternatives are offered. Inspect the review step and the inline payment state on desktop and mobile. Confirm that the visible selection matches the intended transaction and that error messages explain a useful next action.
After an authorized test, inspect the recorded outcome and receipt information. Check the campaign destination, frequency and amount. Preserve the reference if something is wrong, and use the authorized financial workflow for any correction. Do not create a second campaign or another organization account merely to bypass a setup error.
Finally, listen to the questions people ask. If several testers misunderstand a designation, the explanation needs work even if the form is technically functional. If they cannot tell whether a gift is recurring, the selected state needs attention. A clear donation form supports informed giving and gives staff a reliable record they can use for stewardship, reporting and future improvement.