Skip to content
Formward
Log inStart free

Donation forms · 6 fields

Charity donation form template

Records a pledge: who gives, how much, how often and whether their name may be shown. The money itself moves through a payment provider, and the form sends the donor there once the pledge is saved.

Get the code

Charity donation

Live demo: try the fields. Submitting sends nothing.

Why these fields

  • Full name

    text · required

    Required. Needed for a receipt and for matching the pledge to the payment.

  • Email

    email · required

    Required. The thank-you and any receipt go here.

  • Donation amount

    number · required

    Required number with no minimum, currency or decimals defined. Add min="1" and step="0.01", and write the currency in the label.

  • Frequency

    select · optional

    Optional. One-time is first in the list and therefore the default, which is the safe way round. Choosing Monthly here does not set up a recurring payment; your payment provider does that.

  • Make this donation anonymous

    checkbox · optional

    Unticked by default. A tick means do not publish my name; you still know who gave, so explain the difference beside the box.

  • Message (optional)

    textarea · optional

    Optional. Donors sometimes dedicate a gift or say why they give, which is worth reading before you write to thank them.

When to use it

Use it for small charities, clubs and appeals that take gifts by payment link, bank transfer or standing order and want the donor's details and wishes first. If you already use a donation platform's own checkout, you do not need this form.

Set the form's redirect URL to your payment page so a donor who submits the pledge continues straight to paying.

Privacy and GDPR

  • A donor list says something about people's beliefs and sympathies, and for some causes that is sensitive. Keep access narrow and never publish names without the donor's yes.
  • Card numbers and bank logins have no place in this form. The payment page of your provider collects them.
  • A pledge is not permission for appeals by email. Ask for that separately.

Choose your stack. Copy your form.

Replace the example endpoint with your Formward endpoint, then adapt the fields to your needs.

<form action="https://forms.formward.eu/f/your-form-id" method="POST">
  <label for="name">Full name</label>
  <input type="text" name="name" id="name" required />
  <label for="email">Email</label>
  <input type="email" name="email" id="email" required />
  <label for="amount">Donation amount</label>
  <input type="number" name="amount" id="amount" required />
  <label for="frequency">Frequency</label>
  <select name="frequency" id="frequency">
    <option value="One-time">One-time</option>
    <option value="Monthly">Monthly</option>
    <option value="Annually">Annually</option>
  </select>
  <label>
    <input type="checkbox" name="anonymous" id="anonymous" /> Make this donation anonymous
  </label>
  <label for="message">Message (optional)</label>
  <textarea name="message" id="message"></textarea>
  <input type="text" name="_gotcha" tabindex="-1" autocomplete="off" style="position:absolute;left:-9999px" aria-hidden="true" />
  <button type="submit">Send</button>
</form>

Accessible by default, and how to keep it that way

  • Every field in the code has a visible label tied to it with for and id, so screen readers announce what to enter and a click on the label focuses the field.
  • Required fields carry the required attribute, so the browser explains a missing answer before anything is sent. Say “required” in words as well; an asterisk or a colour alone is easy to miss.
  • The spam trap field (_gotcha) is hidden from screen readers with aria-hidden and skipped by the Tab key, so people never meet it.
  • In the JavaScript versions, show the confirmation or error in an element with role="status" so the result is announced, and keep the entered answers when sending fails.

Changed the fields? Paste your version into the HTML form tester to see exactly what it sends, or run it through the GDPR form checker.

How the code talks to Formward

Each form you create gets its own endpoint in the form https://forms.formward.eu/f/your-form-id. The HTML version posts to it directly and the browser is redirected to a thank-you page, so it works without JavaScript.

The Next.js version below sends the same fields with fetch and an Accept: application/json header. Formward then answers with { ok: true, id }, or an error body with 402 when the account is over its allowance and its Over limit folder is full, and 429 when the rate limit kicks in. See responses and status codes.

Next.js client component

"use client";

import { useState } from "react";

export function CharityDonationForm() {
  const [sent, setSent] = useState(false);
  const [error, setError] = useState("");

  async function onSubmit(e: React.FormEvent<HTMLFormElement>) {
    e.preventDefault();
    const form = e.currentTarget;
    setError("");
    try {
      const res = await fetch("https://forms.formward.eu/f/your-form-id", {
        method: "POST",
        headers: { Accept: "application/json" },
        body: new FormData(form),
      });
      if (res.ok) {
        setSent(true);
        form.reset();
        return;
      }
    } catch {
      // Network failure: fall through to the same message.
    }
    // The answers stay in the form so the visitor can try again.
    setError("Sending failed. Please try again.");
  }

  if (sent) return <p role="status">Thanks! Your message has been sent.</p>;

  return (
    <form onSubmit={onSubmit}>
      <label htmlFor="name">Full name</label>
      <input type="text" name="name" id="name" required />
      <label htmlFor="email">Email</label>
      <input type="email" name="email" id="email" required />
      <label htmlFor="amount">Donation amount</label>
      <input type="number" name="amount" id="amount" required />
      <label htmlFor="frequency">Frequency</label>
      <select name="frequency" id="frequency">
        <option value="One-time">One-time</option>
        <option value="Monthly">Monthly</option>
        <option value="Annually">Annually</option>
      </select>
      <label>
        <input type="checkbox" name="anonymous" id="anonymous" /> Make this donation anonymous
      </label>
      <label htmlFor="message">Message (optional)</label>
      <textarea name="message" id="message" />
      <input
        type="text"
        name="_gotcha"
        tabIndex={-1}
        autoComplete="off"
        style={{ position: "absolute", left: "-9999px" }}
        aria-hidden="true"
      />
      <button type="submit">Send</button>
      <p role="status">{error}</p>
    </form>
  );
}

Spam protection

  • The generated code already includes the hidden _gotcha honeypot. Leave it in: a bot that fills it gets a normal success response, the submission is filed as spam and no email is sent.
  • Every form has a per-IP rate limit, and you can restrict it to your own domains with the allowed-origins list in the form settings.
  • Cloudflare Turnstile is optional and works on every plan, including Free. Turn it on in the form settings, add the widget to your markup and Formward checks the token server-side.
  • The form settings can also reject disposable email addresses, which is worth turning on when a fake address would waste your time.

What happens after submit

  • Each pledge is emailed to your notification address and stored in the dashboard on every plan.
  • From Personal, an automatic reply can thank the donor and repeat the pledged amount by inserting the submitted amount field into your own template.
  • From Personal, the CSV export lets a treasurer reconcile pledges against the payments that arrived.

Questions

Does this form take the payment?
No. It stores the pledge and can redirect the donor to your payment page, where the payment provider collects the card or bank details.
How do I match pledges to payments?
Ask donors to pay the pledged amount and to use the same email address at the payment provider, then compare the two lists by email and amount. For bank transfers, give a reference to quote.

Customize before publishing

  • Remove fields you do not need and mark only essential answers as required.
  • Replace placeholder wording with terms your audience already understands.
  • Add your privacy notice, retention details and expected response time.
  • Test keyboard focus, validation errors and the confirmation state on mobile.

Use this template

Create a free account and the form is set up from this template. Copy your endpoint and replace https://forms.formward.eu/f/your-form-id in the code above.

Use this template →