For NGOs and charities
Your donation data already exists. It just lives in six places.
Donativus connects the website you already run, the forms you already publish and the processors you already use, then turns what arrives into one analyzed record you can act on.
In short
Donativus helps a single-organization NGO or charity stop reconciling fundraising by hand and start acting on it. It connects your website and donation forms, your payment processors such as Stripe, Redsys, PayPal or Square, your CSV imports and your email tool, then turns what arrives into one transaction ledger, one supporter timeline, and the analytics and recommendations that come from them. Your team can see which campaign produced a gift, whether a recurring donor is still active, what this month actually raised, and what to do about it, without exporting anything to a spreadsheet first.
What goes wrong today
- The month-end spreadsheet
- Someone exports payouts from the processor, exports submissions from the form tool, and matches them by hand against the donor list. It takes a day, it never comes out the same way twice, and it gets bigger every year you succeed.
- Two supporters who are the same person
- A donor gives by card in March, joins your newsletter in June with a different email, then sets up a monthly gift in November. In three separate tools that is three records, and nobody sees the one relationship underneath them.
- Recurring gifts that stop quietly
- A card expires and a monthly gift just stops arriving. Nothing flags it, so you find out months later as a dip in the annual figures, not as a conversation you could have had while the donor was still reachable.
- No answer to “what worked?”
- The spring appeal did well, but the evidence for why is split across a mail tool, an analytics property and a payout report. Planning the next one turns into an argument about who remembers what, instead of a look at the data.
What connects, and on whose authorization
Each source below is read only after your organization configures and authorizes it.
- WordPress & WooCommerce
- Most NGOs already have a WordPress site they are not about to rebuild. Donativus connects to it, so donation activity flows in while the site stays exactly where it is.
- Stripe
- Card giving arrives with its charges, refunds and recurring events intact, so your ledger shows what actually settled, not what was pledged.
- Donativus forms
- For an appeal that needs its own page, hosted forms produce submissions already linked to a supporter record.
- CSV & spreadsheet imports
- Years of history sitting in a spreadsheet or a legacy CRM export join the same supporter timeline, instead of staying an archive nobody opens.
- Mailchimp
- Email engagement sits beside giving history, so a lapsed monthly donor who still opens every newsletter reads as an opportunity, not a statistic.
The operating loop for this work
-
Connect
Authorize your processors, your website, your forms and your email tool. Nothing is read until you switch it on.
-
Unify
Provider events land as transactions carrying their reference, status and the campaign that produced them, attached to one supporter record.
-
Analyze
Lifetime giving, recurring status and campaign performance stop being three separate lookups and become one view.
-
Act
Build an audience from what the data actually shows, lapsed monthly donors, first-time givers from the spring appeal, then run the campaign against it from the same native tools.
-
Measure and improve
Results trace back to the campaign and source that produced them, so next year’s appeal is a decision, not a guess.
Do we have to replace our website?
No, and that is the point. You have already spent real money on a site that reflects your work, and the last thing a fundraising platform should ask is that you rebuild it. Donativus sits behind the site you already run.
Connect WordPress or WooCommerce and donation activity and supporter details reach Donativus as they happen. If you also want a dedicated page for one appeal, hosted Donativus forms are there for that. They are an addition, not a migration. Campaign and source attribution travels with the gift either way, so a donation that started from a newsletter link is still recognisable as one when it lands in the ledger.
Campaign attribution
Recording which campaign, appeal or link produced a gift, and carrying that fact through to the transaction record, so you can read results by campaign, not only by total.
Reconciliation: the trustworthy foundation under the analytics
Reconciliation is proving that the money you think you raised is the money that actually arrived. In most small fundraising teams that is a monthly spreadsheet exercise, and it is the first thing to slip when a campaign gets busy. It is also the foundation everything else in this page depends on: analytics are only as good as the transactions behind them.
Donativus takes in provider events as they happen and turns them into transactions that keep their provider reference, their status changes and their link to a supporter and a campaign. A refund is a recorded event, not a manual correction. A failed recurring charge shows up as a state, not an absence. When your treasurer or auditor asks where a figure came from, you point to a record with evidence attached, not a spreadsheet you have to rebuild.
This does not make Donativus a payment system. Your processors still take the payment and charge their own fees. Donativus is the layer that makes their output trustworthy enough to analyze and act on.
Transaction reconciliation
Matching each payment a processor recorded to the supporter, campaign and expected amount in your own records, and keeping the evidence of that match.
Keeping recurring giving healthy
For most charities, regular monthly gifts are the difference between planning a year and surviving it. They are also the easiest income to lose without noticing, because losing one looks like nothing happening.
Recurring payment events arrive as part of ingestion, so Donativus shows recurring giving as a state, not a total: who is active, whose payment failed, whose gift stopped after a card expired. That turns retention into conversations your fundraiser can have this week, and gives leadership a forward view of committed income instead of a number looking backward.
Recurring funding health
The current state of your regular giving: active gifts, failed payments, recently lapsed supporters, read as a live picture rather than a total raised.
Built for teams where one person wears several hats
In a small charity, the person running the appeal is often the same person chasing the failed payment and putting together the trustee report. A platform that needs an administrator is a platform that will not get used.
Access is role-aware, so a volunteer helping with a campaign does not need a finance lead’s permissions, and the finance lead does not have to work through a fundraising screen to answer an audit question. Everyone looks at the same underlying records, which ends the recurring argument about whose export is right.
What changes
- Month-end stops being a project
- Provider data arrives reconciled, so closing the month is a review, not a rebuild.
- One supporter, one history
- Gifts, form submissions, imports and email engagement resolve to the same person.
- Appeals you can evaluate
- Campaign and source attribution makes “what worked” a query, not a recollection.
- Regular giving you can defend
- Failed and lapsed recurring gifts surface while there is still time to act on them.
How it fits with what you run
- Donativus is not a payment processor. Your provider captures and settles the payment, and their fees are separate from what you pay us.
- Your website stays yours. Donativus connects to supported website, form, import and processor sources. No rebuild required.
- Every source is read only after you configure and authorize it. Nothing is tracked before that.
- Built-in analytics cover fundraising and operational reporting. Power BI is optional, for teams that already work in it.
Questions we hear from ngos & charities
01 Can we keep our current donation page?
Yes. Donativus connects to supported website and form sources, including WordPress and WooCommerce, so your existing donation page keeps working exactly as it does now. Hosted Donativus forms are there if you want a dedicated page for one appeal, but they are optional.
02 What happens to the giving history we already have?
Bring it in through a CSV or spreadsheet import, including an export from a legacy CRM. Imported gifts join the same supporter timeline as everything arriving live, so a donor’s history is not split across an old system and a new one.
03 Do we still pay processor fees?
Yes. Donativus does not process payments. Your providers capture and settle the money and charge their own fees. Donativus reads, normalizes and reconciles what they produce. Processor charges are separate from what you pay us.
04 Is this usable by a team without technical staff?
Setting up a source is a configuration step, done once, with the credentials you already hold for that provider. Day to day, your team works in the supporter, transaction, campaign and analytics views. No engineering required to keep data flowing.
05 Can we see which campaign produced a donation?
Yes, where the gift carries campaign or source attribution from the form, link or provider metadata. That attribution sits on the transaction itself, so you read campaign results directly instead of rebuilding them from separate reports.
See the platform working with real fundraising data
Book a demo for a straightforward walkthrough of analytics, supporter records and campaign tools, or bring your own questions about how your organization would connect.
Donativus is in beta. See the reduced beta price on our pricing page. See pricing