Recommended approach (GDQ-style)

Use a donation platform that supports campaigns + an API (and ideally webhooks). Donors donate on the platform, and we fetch/receive donation events to display totals and verify donors.

How this appears on your website

Why this is best at small scale

Next decision: pick the platform you want to use for donations. Once you pick it, I’ll wire the “Donate” buttons and implement verified tracking.

Start a verified donation (Tiltify Relays)

Once configured, this button will generate a one-time verification code and send you to the donation form. After donating, come back and check your code.

Setup guide: docs/tiltify-relay-setup.md

Embed (optional)

Some platforms provide an embed snippet (script or iframe) for a campaign. If embedding is blocked by the platform, the reliable fallback is always linking out.

When you have an embed snippet: paste it here.
(We’ll replace this placeholder block with the platform-provided code.)

Option A: Direct to charity sites

Lowest effort, but hardest to verify automatically because every charity has different systems.

Verification usually becomes manual (receipts) unless each charity offers an API.

Option B: Platform per charity

Create a campaign page per charity (on one platform). Your site links to each campaign.

We can track totals per charity by querying the platform’s API.

Option C: You collect money

Most control, best tracking, but it means you become the payment receiver and must handle accounting, payouts, refunds, and legal/compliance responsibilities.

Privacy

If we display a donor feed, we should make it opt-in (display name) and keep personal data minimal. A basic privacy policy and data retention notes should be added before launch.

Contact

Add an email address or contact form later. For now you can put a simple email link here.