Donation Form in HTML — Working Code for Nonprofits

<form action="https://splitforms.com/api/submit" method="POST">
  <input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
  <input type="hidden" name="_subject"   value="New donation intent" />

  <fieldset>
    <legend>Donation amount</legend>
    <label><input type="radio" name="amount" value="25" required /> $25</label>
    <label><input type="radio" name="amount" value="50" /> $50</label>
    <label><input type="radio" name="amount" value="100" /> $100</label>
    <label><input type="radio" name="amount" value="250" /> $250</label>
    <label>
      Custom amount: $<input name="amount_custom" type="number" min="1" step="1" />
    </label>
  </fieldset>

  <fieldset>
    <legend>Frequency</legend>
    <label><input type="radio" name="frequency" value="one-time" checked /> One-time</label>
    <label><input type="radio" name="frequency" value="monthly" /> Monthly (recurring)</label>
  </fieldset>

  <fieldset>
    <legend>Your details</legend>
    <label>Full name<input name="name" required /></label>
    <label>Email<input name="email" type="email" required /></label>
    <label>Make this donation anonymous
      <input type="checkbox" name="anonymous" value="yes" />
    </label>
    <label>Note (optional)
      <textarea name="note" rows="3"></textarea>
    </label>
  </fieldset>

  <input type="checkbox" name="botcheck" style="display:none" tabindex="-1" />
  <button type="submit">Continue to payment →</button>
</form>

Donation forms have a specific UX shape that converts. Preset amounts (radio buttons, large hit targets) for the common values; a custom amount field for everything else. Frequency toggle (one-time vs monthly) — monthly recurring is the highest-leverage option for nonprofits, so default to it if your audience supports it. Donor info kept minimal: name, email, optional note.

The form above captures the donation *intent*. The actual payment processing happens on the next page via Stripe Payment Element (or your processor of choice). splitforms's `/api/submit` endpoint accepts the intent, emails you, and 302s the donor to your payment page. The payment page reads the amount from URL params or from the splitforms session.

Why split intent from payment? Two reasons. (1) PCI compliance: card data should only touch your Stripe checkout, never your form backend. (2) Conversion: capturing the intent first lets you follow up if the donor abandons before payment — 'You started a $50 donation' email recovery flow.

For tax-deductible donations (US 501c3), capture the donor's mailing address on a follow-up form after payment succeeds. splitforms's dashboard exports CSV that imports cleanly into donor-management platforms (Bloomerang, DonorPerfect, Salesforce NPSP).

Capture intent, redirect to Stripe payment. Don't handle card data in the form.