Collect the right context
Organisation, authorised contact, registration claims, appeal evidence, funding purpose, recipient model, countries and currencies.
For charities · structured review
Less administration. A deliberate final decision.
Prepare a structured appeal, automate repetitive completeness checks and give a human reviewer one clear final approval step—without confusing automation with verification.
Current release: local workflow preview only. No real application, verification, payment onboarding or publishing is connected.
Proposed production workflow
Automate the checklist, not accountability.
Each stage has a distinct result. A complete form is not a verified organisation, and an approved organisation is not automatic approval for every appeal, country or recipient.
Flag missing information
Check required fields, syntax, currency precision, internal consistency and material changes before a reviewer spends time on the entry.
Connect independent checks
Production services must authenticate the account and check registry evidence, domain control, recipient permission, safeguarding and provider eligibility.
Keep final approval human
Show the reviewer the evidence, unresolved items, provider state and revision history before one deliberate publishing decision.
Re-review material changes
Recipient, payout, country and restriction changes should pause publication or payouts until their new scope is reviewed.
Reconcile money and work
Separate gross gifts, processing charges, net funds, grants, completed payments and dated delivery updates without exposing private records.
Available to test now
A transparent local prototype.
The application and review pages demonstrate the intended handoff using fictional data. Nothing leaves the browser, and approved entries do not become public campaigns.
- Seven automated completeness and syntax checks
- Guarded browser storage with blocked-storage feedback
- Pending and approved-preview states
- One-click final preview approval with visible limitations
Required before real launch
Backend controls still to build.
- Authenticated accountsRole-based reviewer access, audit logs and secure server-side records.
- Independent evidence checksRegistry, identity, domain, recipient and safeguarding results with provenance.
- Payment-provider onboardingOrganisation, campaign, currency, country and payout eligibility—not just a currency selector.
- Controlled publishingServer-authorised approval, versioning, re-review rules and takedown controls.
Local experience, separate eligibility.
Translated content and local-currency formatting can make an application easier to understand. They never prove that a charity, appeal, donor payment or recipient payout is legally or technically available.
Read country and currency guidancePrivacy from the first field.
The prototype deliberately avoids document uploads and asks for fictional details. A production application would need secure upload controls, retention rules, access restrictions and a revised privacy notice before accepting evidence.
Read the draft privacy noticeCharity onboarding questions
What should a charity expect?
Direct answers about the current prototype and the controls required for a real service.
Can a charity publish a fundraiser automatically?
No. The current preview cannot publish a fundraiser. It checks that required demonstration fields are complete and places the entry in a same-browser queue. A final click changes only local preview status. Production publishing would require authenticated accounts, server-side review, verified recipients and approved payment settings.
What can be automated safely before approval?
Automation can check required fields, email and website syntax, funding-plan completeness, currency precision and whether material answers have changed. In production, connected services may also retrieve registry or provider results. Those external results must retain their source and date rather than being reduced to a generic verified badge.
Does one-click approval connect to Stripe?
No. The approval button in this preview only updates local browser storage. It does not contact Stripe, create an account, check a charity regulator, approve a recipient or enable payments. Live activation would need separate provider onboarding and explicit eligibility results for the organisation, campaign and payout route.
What happens when an approved appeal changes?
A production service should compare revisions and return material changes to review, especially recipient identity, bank or payout details, fund restrictions, country and evidence. Editorial typo fixes may follow a lighter process. The change history and current approval scope should remain visible to the final reviewer.
Helpful resources
Useful places for your next step.
CharityCompareLook up a UK charity’s register details and published accounts before you give or fundraise for it.charitycompare.org.ukKode NirlabaWebsite and technology support for Indonesian foundations, NGOs and community groups.kodenirlaba.org
FundraiserFlow’s team builds or maintains websites for some of the organisations linked here. These links are not paid placements or endorsements of each organisation’s work.