Before you start
Gather these before you open Orgo. Every one of them is asked for during setup, and stopping halfway to find a bank statement or write a thank-you message is how half-built campaigns end up published.- A Stripe account you can sign into, or the legal entity and bank details to create one during setup
- Your organisation’s country, which Stripe fixes at account creation and cannot change afterwards
- Campaign copy written: a title, a short story, and the thank-you message donors read after paying
- A hero image, or the URL of a hero video
- A decision on suggested amounts: the figures you want offered, or a plan to press Generate and start from what Orgo proposes
- A decision on frequency: one-off gifts, monthly giving, or both
- Someone with
ADMIN_TENANTto change the settings, and someone withFINANCIAL_TENANTto build the campaign
What to turn on
Everything in this table lives under Settings. Module settings pages all requireADMIN_TENANT, which is what the permission column says when the setting itself is what you are changing.
Setup order
Do these in order. The main reason is Stripe: several controls stay greyed out until an account is connected, and a campaign saved without them needs revisiting. Each step says where in the interface it happens and how you can tell it worked, so you can follow along with Orgo open beside you.Set the organisation country
Connect Stripe

Decide the checkout rules once, for all campaigns

Create the campaign

Add suggested amounts

Add designations, if gifts are restricted
Set the goal
Build the public page

Point the shortcuts at the right campaign
/donate, and which one grants the Supporter flag on member profiles.
Rewrite the thank-you email
Turn on the email campaign module last
What you get
Everything below lands on one public page or one click from it. This is a campaign mid-flight: story and progress on the left, the donation form pinned on the right, recent gifts underneath it.
Where you read the results
Two tabs on the campaign answer different questions. Payments is the ledger: one row per gift. Stats is the campaign view: money over time above the page analytics.
Recipes
Three worked configurations. These are examples, not defaults. Nothing below is preconfigured, and none of it is the only way to set the feature up.Example: a year-end appeal
A six-week campaign with a published target, tested ask amounts, and two emails.
Example: a monthly giving programme
Example: an appeal tied to an event
Orgo has no donation step inside event checkout, so an event-linked appeal is a normal campaign with the event used as the audience and the designation.Add a product option named after the event
Send to the attendees
Tag the links you share
Report on the designation

Setup checklist
Work down this before you publish the first link. It mirrors Setup order, so anything unticked tells you which step to go back to.- Country is set on Settings → Organisation info
- The Payment Gateway page reads Fully connected and Complete
- The organisation-wide checkout switches are set the way you want them for every campaign
- The campaign exists, with One-off, Recurring or both switched on
- Every suggested amount has a price row, and exactly one is marked default
- There is a Product option for each restricted purpose, if you take restricted gifts
- A goal type and Goal value are set, plus a Target date if the appeal has a deadline
- Hero, story and thank-you message are saved on the Landing page tab
- Donation Product points at the campaign you are promoting, and Recurring Donation Product at the monthly programme if you run one
- The Donation thank you template is rewritten in your own voice, in the one language every donor will receive
- Enable Email Campaign Module is on, so a newsletter draft can link to the campaign
- You have given a test gift yourself and received the thank-you email
- The link you are about to publish opens the right campaign, with the right designation pre-selected
Limits worth knowing before you start
Stated plainly, because each one has caught somebody out. Donations do not produce invoices or tax receipts. Generate Invoice on a payment row only appears for membership fee and event registration payments; a donation payment is refused. There is no annual giving statement, no Gift Aid support and no donation tax form anywhere in the product. The donor gets the Donation thank you email, and Stripe’s own receipt if you enable Stripe Email Receipts. If your donors need a document for tax purposes, produce it outside Orgo. The PDF Receipts/Proofs setting is not a general donation receipt. It adds a downloadable proof on paid rows, but the document is generated from the payer’s validated identity record, so it only produces anything for donors who went through identity validation. Do not enable it expecting receipts for ordinary card gifts. A chapter designation is a label, not a bank instruction. With Has local center option on, a donor picking a chapter under Designate to stamps the payment with that chapter, which is what the payments filter and the refund permission read. A gift with no designation is treated as organisation-level, and the refund, cancel, accept and proof actions on it requireFINANCIAL_TENANT rather than any one chapter’s FINANCIAL_LOCAL. The money still settles into the Stripe account the campaign resolves to. Only fee payments follow chapter Stripe routing: see Stripe integration.
There is no CSV export on the campaign payments or subscribers lists. Both are filterable and paginated on screen only. For a donor extract, build a payments report in Reports: Payments is one of the builder’s starting points, you can add columns from the product, the price, the payer and the company, and the download holds every matching row rather than one page. The alternative is to ask the question in Ask Orgo and use Export CSV, which returns the first 500 rows; save the query and run it from Database Queries for the whole set. Both routes require ADMIN_TENANT, so a fundraiser holding only FINANCIAL_TENANT cannot do this themselves.
Refunds are all or nothing. Refund returns exactly that payment row’s amount. There is no partial refund in Orgo, so a donor who wants half their gift back has to be refunded in full and give again.
Donor messages publish immediately. A message attached to a successful or on-hold payment is stored as approved and appears in Words of support straight away. Moderation is after the fact: there is no pending queue to approve. Leave Messages of support from donors off if you cannot watch the page.
There is no abandoned-gift reminder for one-off donations. The only checkout reminder in the product chases recurring subscriptions that stalled after identity validation, and it fires once, at least 48 hours later. Somebody who opens your donation page and leaves is never emailed.
Goals are unavailable on multi-currency campaigns, because there is no single number to total toward. Pick one currency for any campaign you want a progress bar on.
Widget ids are public by design. Anyone with the id can render your donation form on their own site. Delete a widget you no longer want live rather than removing the snippet from your page.
A campaign that has taken any money cannot be deleted. Archive it. The page keeps loading and the form is replaced with a notice that payments are disabled.
Orgo is not a peer-to-peer or team fundraising tool. There are no supporter-created pages, no individual fundraiser targets and no team leaderboards for giving.
Troubleshooting
The Recurring or One-off toggle is greyed out on the campaign form
The Recurring or One-off toggle is greyed out on the campaign form
A gift went through but I cannot find it in Orgo
A gift went through but I cannot find it in Orgo
success? A payment on hold shows as on-hold and has not been captured. Was it designated to a chapter you do not hold FINANCIAL_LOCAL on? The payments list is scoped by permission, and the payment-ID and email filters are only offered to FINANCIAL_TENANT. And is it on the right campaign at all? The /donate shortcut resolves to whichever campaign is set as Donation Product, which is not necessarily the one you were promoting.Nobody got a thank-you email
Nobody got a thank-you email
A donor wants a receipt for their accountant
A donor wants a receipt for their accountant
A donor wants their gift back
A donor wants their gift back
FINANCIAL_LOCAL on the chapter the gift was designated to, or FINANCIAL_TENANT when the gift carries no chapter. ADMIN_TENANT qualifies either way, and a chapter treasurer cannot refund an undesignated gift. It only works on a payment already in success; a payment still on hold is cancelled instead, and the full row amount goes back. Refunds you issue in the Stripe Dashboard are picked up and marked in Orgo too, so you do not have to do it twice.A monthly donor wants to stop and cannot find how
A monthly donor wants to stop and cannot find how
The donor wall is empty or names are missing
The donor wall is empty or names are missing
I set Recurring Donation Product but nobody shows as a Supporter
I set Recurring Donation Product but nobody shows as a Supporter
A small custom amount is rejected even though it is above my minimum
A small custom amount is rejected even though it is above my minimum
The goal fields are missing on the campaign form
The goal fields are missing on the campaign form
I cannot open or edit the campaign
I cannot open or edit the campaign
FINANCIAL_TENANT. FINANCIAL_LOCAL reaches only campaigns belonging to a chapter the holder is attached to, which is why a chapter finance admin sees Finance → Local products but not the organisation’s campaigns. Someone without the permission is sent to the login screen rather than shown a permission message, which reads like an expired session and is not one. See Permissions.Related
- Donations: campaigns, suggested amounts, A/B testing, payments and refunds
- Donation pages and widgets: the public page, donor messages, the donor wall, embeds
- Stripe integration: connecting payment processing, statuses and payouts
- Recording a payment: cash, cheque and bank transfer gifts
- Newsletter: appeal emails, audiences and follow-ups
- Insights and Ask Orgo: revenue dashboards and donor questions
- Setup templates: the other playbooks

