Donating to your foundation
If your organization has a foundation set up, you can give to its funds and campaigns the same way an external donor would — through a public campaign URL. Once a donation is processed and your email matches an active member account, the system links the gift to you so it shows up in your donation history.
public donate page
Two donation paths
There is one donation flow today, and it goes through the public donation page:
| Path | Who | Where |
|---|---|---|
| Public donate page | Anyone (including members and guests) | A campaign URL, e.g., /donate/<foundationId>/<slug> |
Members do not have a "Donate" button inside the authenticated app in v0.62.1. To give to your own foundation, you use the same campaign link as anyone else. Your org typically shares the campaign URL via email, a bulletin, or a QR code.
How a donation works
- Open the campaign page. It shows the campaign description, current raised amount, donor count, and date range.
- Click Donate Now.
- Pick a preset amount (
$25 / $50 / $100 / $250) or type a custom amount. - Fill in your contact info: first name, last name, email, and optionally phone and address.
- Choose options:
- Cover processing fees (a 2.9% + $0.30 surcharge added on top so the campaign receives the full amount).
- Make this a recurring gift — select monthly, quarterly, or annual cadence.
- Make this anonymous — hide your name from public donor lists.
- Enter card details and submit through the foundation's configured payment processor (Stripe).
- You land on a confirmation screen and the foundation emails you a per-donation receipt.
Member linking
When you donate using an email that matches your member account — either your primary email or a verified secondary email — the system links the donation to your user record automatically. This is what makes the donation appear in your history on the member detail page (visible to foundation admins) and counts you against the foundation's "member donor" metrics.
If you donate from a different email that isn't on your account, the donation is recorded against a separate donor profile and won't link back to your member record. Add the email to your account first if you want the gift attributed.
Your donation history
In v0.62.1, the member-facing donor portal (your own list of donations, pledges, and receipts) is not yet surfaced in the app UI — the backend endpoints exist (/api/foundation/my-donations/, /api/foundation/my-pledges/, /api/foundation/my-receipts/) but no member-side page consumes them yet.
What you can rely on today:
- The foundation emails you a receipt each time a donation completes.
- For recurring pledges, the foundation emails you a receipt for each renewal.
- Your foundation admin can pull up your full donation history from your member detail record and email you a copy or generate an annual receipt.
A user-facing donor portal page is on the roadmap.
Tax receipts
Two flavors:
- Per-donation receipts are emailed automatically after each completed donation.
- Annual receipts are generated in mid-January for the previous tax year and emailed to every donor who gave during that year. The PDF is also stored against the donation record.
If you need a duplicate, contact your foundation admin.
Recurring pledges
If you opt in to a recurring gift at donation time, the foundation creates a subscription against your card via Stripe and re-charges on the cadence you picked. Each charge produces a separate donation record and a per-donation receipt.
To stop or change a recurring pledge today: contact your foundation admin. There isn't a self-service "cancel my pledge" button in the member app yet.
Anonymous donations
Checking Make this donation anonymous hides your name from public-facing donor lists and the campaign's recognition feed. The foundation admin can still see who you are — anonymity is a display-level setting, not a privacy guarantee against the foundation's own staff.
Member donations vs. external (guest) donations
| Member donation | Guest donation | |
|---|---|---|
| Email on file | Matches a member account | Doesn't match (or no account exists) |
| Linked to your profile | Yes (automatic) | No (separate donor record) |
| Shows in member detail | Yes | No |
| Counts as "member donor" | Yes | No |
| Receipt | Yes | Yes |
The donation form itself is identical for both; the difference happens at the linking step on the server.
Errors and edge cases
- Payment declined. Stripe surfaces the decline reason. Try a different card or contact your bank.
- Email mismatch but you want the gift attributed. Add the email you donated from as a verified secondary email on your account, then ask your foundation admin to re-link the donation.
- Foundation not configured. If the campaign URL returns a "Foundation not configured" error, the foundation module isn't enabled for your org yet.
Mobile differences
The public donate page is fully responsive — it works in the mobile browser and inside the native app's webview if the campaign link is opened from a bulletin. Card entry uses the native autofill from your saved cards. Apple Pay and Google Pay are available to the extent Stripe offers them for your foundation's configuration.
What foundation admins see that you don't
- Foundation admins see every donation (yours included), donor profiles, campaign progress, and aggregate reports.
- They can pull a Member Donation History for any chapter member.
- They configure the payment processor, funds, campaigns, and bulletin schedule.
Related
- Your profile — manage the secondary emails that get matched.
- Notifications — opt in to "donation received" confirmations.
- Privacy & your data — how donor records relate to your member record.
Last verified against v0.62.1 (2026-05-11).