Fundraising software for member organizations

Each campaign is a hosted landing page with a slug-based URL your organization controls. Configurable per campaign:

• Title, description, and cover image
• Brand colors, plus a light or dark theme
• Suggested donation amounts and a minimum
• An optional goal with a progress bar
• An end date for time-limited appeals

One product is designated as the main donation and drives the primary donate button, while other campaigns keep running alongside it.

A goal with a progress bar suits a defined project, such as replacing fencing at one branch. A permanent, ongoing donation page runs without one, so a general appeal does not display a bar that never fills.

The public donor list shows who gave and any message they left, with a top-donor leaderboard above it.

• Donors can post a message of support alongside their gift
• Donors can choose to appear anonymously
• Each social element is configurable or can be switched off

Organizations that prefer no public donor display disable the section entirely.

Both options sit on the same page. Donors pick a suggested amount or enter their own, above a minimum your organization sets. The minimum prevents micro-transactions that cost more to process than they raise. Monthly recurring gifts give a fundraising program predictable income rather than a series of one-off spikes.

Sponsorships work as custom Stripe products rather than a separate module. A sponsorship product carries its own price tiers, product options, and product page, with recurring billing switched off for a single payment.

Every donation creates a record and an invoice. The donation receipt email is a branded system template your organization can override. Refunds are processed from the admin panel, and the original invoice updates automatically.

Each chapter with its own legal entity connects its own Stripe account. Donations to that chapter's campaigns settle in that chapter's bank account, alongside its local membership fees and event ticket revenue. The national level grants or revokes the Stripe connection per chapter, or enables it across the whole network at once.

A donor paying for a product created by a local chapter sees that chapter's legal entity and its connected Stripe account on the payment screen. The transaction runs between the donor and the chapter, not through the national organization.

A chapter admin or chapter financial manager creates donation products for their own chapter, with permissions isolated to that chapter's data:

• Campaigns scoped to a single chapter
• Local fees and event ticketing through the same account
• Financial reporting restricted to that chapter

Anyone can donate on a chapter page. Donors do not need to be members, and they do not need to live in that chapter's area.

A chapter that is not a separate legal entity uses the parent organization's payment setup. The national office can also create a campaign on that chapter's behalf and transfer the proceeds outside the platform. Both models coexist in one organization, so a network does not wait for every chapter to incorporate before going live.

A single donation page can ask donors which chapter, region, or project their gift supports. The designation is stored against the donation and available for reporting.

The money still settles in the Stripe account connected to that page. Stripe does not split one card payment across two accounts, so a chapter that needs funds landing in its own bank account needs its own page and its own Stripe connection.

The national dashboard reports donations per chapter alongside membership growth and recurring revenue, filterable by period. A national office sees which chapters are raising money and which have gone dormant without requesting a report from each one.

The same campaign can be surfaced in more than one place on a site:

• An inline block placed inside a page or a news article
• A pop-up triggered from anywhere on the site
• A sticky donate button that stays visible while visitors scroll

Widgets load through an iframe and carry your campaign's branding rather than Orgo's. They work on WordPress, Squarespace, Wix, and any site that accepts an HTML embed. Donors complete the payment in place, without a redirect to another domain.

Each widget reports its own views, conversions, and revenue. An organization running a sticky button, a pop-up, and an in-article block sees which placement produces donations and which does not.

The widget detects the visitor's location and displays the local currency. A donor in London sees pounds and a donor in New York sees dollars, which removes one reason to abandon a donation. Stripe processes more than 120 currencies.

The donation widget can carry a newsletter subscription option, so a first gift also produces a subscriber and a contact record rather than an anonymous transaction.

Stripe offers the relevant methods automatically, based on the donor's device and region:

• Cards
• Apple Pay and Google Pay
• Revolut Pay and other digital wallets
• Direct debit

Orgo charges a platform fee on donations processed through the platform. The rate is set by your plan and agreed in your contract, and reaches zero at the highest tier. Stripe's own processing fee is charged separately by Stripe. Donors can be offered the option to cover both at checkout, so the full intended amount reaches the organization. Nonprofits can also apply to Stripe directly for a reduced processing rate.

Monthly gifts renew automatically through Stripe. Failed payments retry automatically, and webhooks update the donor record in real time, so the database reflects the payment state without manual reconciliation.

Not every donation arrives by card, and each other route has a place in the same records:

• Invoices payable by bank transfer, reconciled through a unique payment reference and marked as paid
• Cash donations recorded by an admin
• Historical and offline donations imported by CSV

Donation flows can include identity checks. In the Romanian presidential campaign run on Orgo, donor identity was validated by OCR scanning of Romanian ID documents, so every contribution met the legal thresholds applying to political donations.

A donor who gives without an account becomes a contact record automatically, with their full donation history attached. Contacts carry no login, so donors never have to register in order to give.

When an existing member donates, the donation appears on their profile next to their events, payments, documents, email logs, and tags. Membership history and giving history sit on one screen instead of in two systems.

Converting a contact into a member keeps every donation, event attendance, and email in place. Duplicate records, common where the same person gave under two email addresses, are detected automatically and merged, with a 30-day rollback.

Donor and non-donor lists are built as filters over the same database and used directly as newsletter segments. Thanking everyone who gave to one campaign takes no export to a separate mailing tool and no re-import afterwards.

Donation data exports to CSV at any time and belongs to the organization outright. Every export and report generation is logged with the user, timestamp, and IP address.

Orgo runs variants of the suggested donation amounts on the same campaign and reports the average donation and the donation count for each variant. Asking for more raises the average up to a point, then depresses it, and the test locates where that point sits for a given audience.

The test needs volume. Around 100 donations per variant is where results become meaningful, so it suits high-traffic campaigns rather than small appeals.

Meta Pixel and Google Tag Manager connect to donation pages and widgets, so paid acquisition reports return on ad spend against actual donations.

Each campaign reports total raised, the split between recurring and one-time gifts, and revenue charted over any period. Chapter admins see the same figures restricted to their own chapter's campaigns.

Ask Orgo answers questions against the whole database in plain language, for example a request for the top 100 donors or the top donors in one region. Results save as reusable reports, export to CSV, or convert into a newsletter segment. Queries run without sending data to external model providers.