Skip to main content

Share a Public Donate Page

Goal: Have a clean, shareable URL on your own (Ayuna) domain that you can put in emails, on social media, in print materials, and anywhere else where embedding into your affiliate website isn't an option.

When to use a public page vs. an embedded form​

  • Public page (/donate on the Ayuna domain) — when you need a URL you can paste anywhere: a link in an email signature, a QR code on a flyer, a social post, a partner organization's website. Your affiliate's branding shows; the URL is on the Ayuna domain.
  • Embedded form — when the donor is already on your affiliate's website and you want them to stay. The URL never appears.

Most affiliates use both. The public page is the URL of record; the embedded form is the home-website experience.

What the public donate page provides​

The public page at /donate (on the Ayuna app) shows:

  • Affiliate branding and logo
  • A streamlined donate form (the "simple donate" variant)
  • Amount presets and a custom amount option
  • Optional recurring toggle
  • Optional tribute toggle
  • Payment by card or ACH (where enabled)
  • Confirmation and receipt

The page is designed to convert efficiently — minimal fields, fast checkout.

Sharing the URL​

The URL is short enough to use directly:

https://app.ayunacore.com/donate

Where to share:

  • Email signature — every staff member's signature can include "Donate at [link]"
  • Social posts — link in bio, link in tweets, link in fundraising posts
  • Print materials — flyers, brochures, event programs (use a QR code that resolves to the URL for paper)
  • Partner websites — when a partner wants to send their audience to give to you, this URL is what you give them
  • Earned media — when a press piece runs, the URL is what readers will visit

Pre-filling​

Like embedded forms, the public page can pre-fill campaign or fund:

https://app.ayunacore.com/donate?campaign=holiday-match-2026

For campaign-specific outreach (an email campaign for the holiday match), use the pre-filled URL so gifts attribute correctly without the donor having to remember to select the campaign.

What the donor experiences​

A donor visiting the public page:

  1. Lands on a clean affiliate-branded page
  2. Picks an amount (preset or custom)
  3. Optionally toggles recurring or tribute
  4. Enters payment details
  5. Submits and sees confirmation
  6. Receives email receipt

Because the page is hosted by Ayuna, it's fast and consistent — no risk of a broken iframe on your website causing problems.

Distinguishing public-page donations in reporting​

Donations from the public page are tagged with the source so you can report on:

  • How many gifts came through the public URL
  • Average gift size from public-URL donors
  • Which channels drove the most public-URL traffic

Useful for evaluating where to invest in promotion next.

Privacy and security​

The public page is served over HTTPS. Card data is tokenized by Finix and never stored by Ayuna in raw form. Donors can give without creating an Ayuna account — their donation creates a person record in your affiliate's database, but they don't see a "create account" prompt unless they want one.

Automatic protection against card testing​

Public donation forms are a common target for "card testing," where a fraudster runs stolen card numbers through a form in small amounts to find which ones still work. Ayuna watches for that pattern on every public payment form and on gifts made from a signed-in donor account, since anyone can register one. When an affiliate sees a burst of declined cards in a short window, the form stops accepting online payments for that affiliate for an hour, longer while attempts keep coming (up to four hours), and each attempt is refused before it ever reaches the card processor. Donors who try during that window see "We're unable to process online payments right now. Please try again later or contact the organization directly." Normal giving, even a busy event night, does not trigger it: the check counts distinct declined cards, so one donor retrying a card does not add up, and at volume it looks at the share of attempts that are declined rather than the count. If you believe your form has been targeted, refund any small unexplained approvals from the same window before they turn into chargebacks.

Ayuna can also ask each donor's browser to prove it is a real browser before a gift is submitted, using Cloudflare Turnstile — on the public page and for donors who are signed in alike. For almost every donor this is invisible: no puzzle and no extra click. Occasionally a donor sees a small "Verifying" box near the card fields that completes on its own. It is managed by Ayuna for every affiliate, so there is nothing for you to set up. A donor whose browser blocks the check (a strict content blocker, for example) sees "We couldn't confirm this request came from your browser. Please reload the page and try again, or contact the organization directly." Reloading the page usually resolves it; otherwise you can take the gift by phone.

Anonymous donations​

The public form supports anonymous gifts via a checkbox. When checked, the donor's name is not attributed publicly, though their identity is still stored in your affiliate's records for tax-receipt and acknowledgment purposes (anonymity from public displays, not from the affiliate).