7 Mistakes Nonprofits Make Choosing a Donation Platform

This is written for the technology and fundraising leaders at enterprise nonprofits who will own this decision for years after the procurement process ends. 

1. Comparing Monthly Price Instead of Total Cost of Ownership

Compare five-year totals, not monthly subscriptions, because the subscription is rarely the largest number. Most donation platforms combine a recurring platform charge with a percentage taken from each donation, and the percentage is the line that grows with your fundraising rather than with the cost of serving you.

The arithmetic is worth doing with your own contract in hand rather than with a market average. Take your platform's percentage rate, apply it to last year's total processed, and multiply by five. Add the recurring subscription across the same period. Then add the staff hours spent on workarounds the platform requires, which is a real cost that never appears on an invoice. That total is the number to compare against alternatives.

2. Treating Integration as a Checkbox Rather Than an Architecture

Ask how data reaches your CRM, not whether the platform integrates with it, because almost every platform claims the integration and few describe the mechanism. The difference between a native sync and a nightly CSV import shows up as reconciliation work for your finance team every month for the life of the contract.

Three integrations decide most of the operational load. CRM, so donor and gift records land where fundraising already works. Payment gateways, so each market can use the methods donors there actually trust. Analytics and tag management, so attribution survives the redirects a multi-market campaign depends on.

3. Underestimating Multilingual and Regional Giving

Language and giving-model support determine which donors can give at all, which makes this a reach decision rather than a localization detail. More than 400 million people speak Arabic, and a donation flow that presents Arabic as translated English text in a left-to-right layout asks those donors to work harder than donors in other markets.

Right-to-left support is a layout question, not a translation one. The interface mirrors, form fields and progress indicators reverse, numerals and date formats change, and the donation amount selector has to read correctly in both directions. Translation alone leaves a page that is technically Arabic and practically awkward.

How Large Is the Islamic Giving Opportunity?

Large, and widely misquoted, so it is worth stating carefully. Credible estimates of annual global zakat range from roughly $200 billion to $1 trillion, with figures around $550 to $600 billion most commonly cited from World Bank and Islamic Development Bank research. Higher numbers circulating in marketing material usually conflate zakat with the size of the Islamic finance industry, which is a different thing entirely.

The more useful figure is the gap underneath the headline. The UNDP notes that formal zakat institutions handle only a small fraction of the total, because most zakat is given informally and directly, often in goods rather than cash.

For an international nonprofit, that gap is an infrastructure question rather than a demand question: the giving exists, and the routes to receive it institutionally are underbuilt.

4. Discovering Your Crisis Response Time During a Crisis

Time a rehearsal before you need one, because the giving window for a disaster closes quickly. Good360, citing the Center for Disaster Philanthropy, reports that around 80% of charitable giving happens in the first 72 hours of a disaster. Estimates of the curve vary across sources, but every version of it is measured in days.

The same research carries a second finding worth holding alongside the first: only about 2% of disaster giving goes toward long-term recovery, down from a high of 17% in 2016. Speed matters, and so does a platform that keeps an appeal converting through the recovery period after attention moves elsewhere.

5. Accepting Security Claims Without Evidence

Ask for artifacts rather than assurances, because compliance status is documented and therefore verifiable. Three regimes usually apply: PCI DSS for card processing, GDPR where EU residents donate, and a growing set of US state privacy laws. Each produces evidence a vendor either has or does not.

On PCI specifically, note that the Security Standards Council does not issue certificates to merchants or service providers. Validation is evidenced through an Attestation of Compliance, a Report on Compliance or Self-Assessment Questionnaire depending on scope, and quarterly scans by an Approved Scanning Vendor. Since 31 March 2025, all applicable requirements in PCI DSS v4.0.1 are mandatory at assessment.

6. Not Establishing What You Can Change Without the Vendor

Establish the boundary before signing: which changes your team can make, which require a support request, and what the turnaround is on each. Every platform draws that line somewhere, and a hosted product draws it deliberately, because a constrained surface is what makes the product maintainable for everyone on it.

The constraint is reasonable and still worth measuring against your requirements. If your organization needs a bespoke donation flow for a specific programme, a custom field structure for a regional data law, or a checkout variation for a partner campaign, find out now whether that is configuration, a feature request, or out of scope.

7. Leaving Exit Terms Until You Need Them

Settle the exit at signing, when you have leverage, rather than at renewal, when you do not. Vendors change: prices move, companies are acquired, products are retired, and strategy shifts. None of that is misconduct, and all of it is reason to know in advance what leaving would involve.

Donation records alone are not portability. A complete export covers donor records, recurring agreements with their billing schedules, campaign content and configuration, integration mappings, and full historical transaction data, in an open format that loads elsewhere without a rebuild. Recurring agreements are the item most often missing and the most expensive to reconstruct.

What Should a CIO Take From This?

Vardot's position: six of these seven mistakes are procurement failures rather than platform failures, and they are repeatable on any platform, including an owned one. An organization that buys an open-source donation platform without measuring integration depth, testing crisis response, or funding maintenance will arrive at the same problems by a different route. The platform model is the second decision. The first is whether the evaluation asked for evidence.

Ownership earns its place where the answers to these seven questions have to be yours to give: at multi-market scale, where percentage fees have become a budget line, where data residency must be evidenced directly, and where campaign requirements outrun a shared product roadmap. Below that threshold, a well-chosen hosted platform is the right answer and worth renewing with confidence.

Where Should You Start?

Answer question four first, because it is the only one you can measure without contacting anyone. Pick a plausible emergency, start a clock when the decision is made, and stop it when a donor in every market you serve could complete a gift. That number is your real response time, and it usually differs from the assumed one.

Then work backward through the other six with your contract open. Vardot builds enterprise donation infrastructure on Drupal as a Drupal Diamond Certified Partner, with 200+ platforms launched and a 4.9/5 Clutch rating across verified reviews, for organizations including UNHCR, UNICEF, UNESCO, and UNRWA. VarGive is the open-source donation platform that we produced.