7 Drupal modules for NGO donations: a buyer's guide

Editor's note: This article was originally published in 2022 and was last updated in June 2026 to reflect current realities. All guidance and figures below reflect 2026.

The right Drupal donation platform does not win because it has the most modules. It wins because it does five things well: it makes recurring giving easy, it accepts payment in every market you fundraise in, it keeps donor data and card details secure, it syncs cleanly with your CRM, and it stays up when a crisis appeal sends traffic spiking. For NGOs like UNHCR, UNRWA, and Médecins Sans Frontières, those capabilities, not a module checklist, are what move donations.

A strong Drupal donation platform for an NGO is judged by capabilities, not modules: recurring giving, multi-currency and multi-market payments, payment-page security that meets PCI DSS 4.0.1, donor data sync to a CRM such as Salesforce, and the ability to absorb crisis-driven traffic. Drupal modules like Commerce and Commerce Recurring are how those capabilities get delivered, not the reason to choose the platform.

What should an NGO look for in a Drupal donation platform today?

An NGO choosing a Drupal donation platform today should evaluate it on five buyer capabilities, not on a list of modules: cost to run, speed to launch campaigns, security of payments and data, sovereignty over where data lives, and scale under crisis traffic. The technology landscape has shifted enough since 2022 that an old module checklist now points at the wrong things.

Three changes since 2022 reset what a donation platform has to do:

• Payment-page security became a hard compliance line. Under PCI DSS v4.0.1, requirements 6.4.3 and 11.6.1 require every script on a payment page to be authorized, integrity-checked, and monitored for tampering. These moved from best practice to mandatory on 31 March 2025, in direct response to e-skimming attacks on checkout and donation forms.
• The analytics ground moved. Universal Analytics stopped processing data on 1 July 2023, and the standalone Google Analytics module for Drupal is now end-of-life. Current platforms track through Google Tag (GA4 and Google Tag Manager), with consent handling built in.
• Drupal 7 reached end-of-life in January 2025. Any donation platform still framed around Drupal 7 era assumptions is pointing donors and staff at an unsupported world. Enterprise NGO builds now run on Drupal 10 and 11.

CRM integration also crossed from nice-to-have to table stakes. A large NGO expects donor activity to flow into the system its fundraising team already runs, not to live in an island database on the website.

Why a list of Drupal modules is the wrong way to choose

A list of Drupal modules is the wrong way to choose a donation platform because modules are implementation details, and the buyer is rarely the person who picks them. Fundraising directors, digital leads, and procurement teams control donation-platform budgets, and they care whether the platform raises more money safely, not whether it runs a particular contributed module.

There is a second reason to be wary of module lists: not every module on a generic list is a donations capability. Many are ordinary site-building tools that any website uses. The features that actually differentiate a donation platform, recurring billing, fraud defense, multi-currency, CRM sync, are the ones a generic list tends to omit.

Two trade-offs matter more than any single module name:

• Own versus rent. A hosted donation widget is fast to switch on, but you rent the donor relationship and the data. A platform you own on Drupal keeps the donor data, the design, and the roadmap under your control. The cost is that you, or your partner, carry more of the burden.
• Core and contrib versus custom code. Capabilities built on well-maintained Drupal core and widely used contributed modules are lower risk: community-supported, security-patched, and resilient when staff changes. Bespoke custom code is powerful, but it becomes a maintenance liability. For a CTO, "we build on a maintained open-source base, not a pile of custom code" is more reassuring than any single module name.

Our view: a donation platform's resilience is decided before any module is installed

Our view: the donation platforms that survive a crisis appeal are the ones where security, donor-data sync, and multi-market payments were architectural decisions, not plugins added after launch. On the platforms, Vardot, a Drupal Diamond Certified Partner, builds and runs for humanitarian and UN-family organizations, and the failure mode is rarely a missing feature.

When a donation platform breaks, the culprit is almost always a capability that was treated as an add-on. A payment-page script no one inventoried. A CRM sync bolted on late. A currency or a regional payment method that was never configured. Each one holds up fine in a demo and then breaks under load, or under audit, exactly when a major appeal is driving record traffic. Module count tells you nothing about whether a platform was built to hold under that pressure. The capability architecture does.

A capability checklist for evaluating a Drupal donation platform

Evaluate a Drupal donation platform against five capability pillars, with the modules and technology treated as supporting evidence rather than the headline. The checklist below maps the buyer question to what good looks like and to how Drupal delivers it.

Recurring giving and multi-market payments sit across the whole table, because they touch cost, speed, and scale at once. Recurring donations are delivered through the Commerce Recurring framework, and multi-currency, multi-country giving through currency resolution plus broad payment coverage (Stripe with Apple Pay and Google Pay, PayPal, and regional providers such as 2c2p in Southeast Asia and Vipps in the Nordics). Regional content and redirects are handled with GeoIP, and right-to-left and multilingual support, essential for Arabic and the wider UN-family audience, are built in rather than retrofitted.

How these capabilities show up in real NGO donation platforms

The clearest test of a capability framework is whether it holds up in production donation platforms, so here is how three of them map to real NGO builds.

UNHCR: one platform, many markets, crisis-scale traffic

The UNHCR global donations platform shows the multi-market and scale capabilities together. Vardot used GeoIP detection to route visitors by location, so each region sees the right campaign or a location-specific prompt, and that approach supported more than 900 published pages across different campaigns, regions, and timeframes. A platform serving that many markets at once is exactly the case where caching, search, and CDN decide whether a crisis appeal stays up or falls over.

Médecins Sans Frontières (MSF): an integrated donation engine

The MSF donation platform shows the donation-engine capability: Vardot rebuilt a previously separate, hard-to-update donation system as a custom, integrated platform inside the CMS.

Building it on Drupal Commerce gave MSF's team more autonomy over the donation flow and connected fundraising, marketing, and knowledge-sharing in one place rather than across disconnected tools. Read the full MSF case study.

Tkiyet Um Ali (TUA): recurring giving that compounds

The Tkiyet Um Ali platform shows the recurring-giving capability, built on the Commerce Recurring framework, so supporters can sign up once and give on a monthly or annual schedule. Because TUA's site is built on Varbase, content teams get a content-moderation and publishing workflow that lets non-technical admins create and edit pages by role and permission, with mobile management and preview, while the platform keeps a clean upgrade path instead of a rebuild every few years. Recurring revenue is the capability that compounds: it turns one-time appeals into predictable funding.

What comes next: AI-ready donor experiences and Drupal Canvas

The next phase for NGO donation platforms is AI-ready architecture and a visual page builder that lets fundraising teams launch campaign pages without waiting on developers. Drupal Canvas, released as version 1.0 in December 2025 and shipping by default in Drupal CMS 2.0, is the builder to plan around. It is the forward-looking replacement for the older Layout Builder approach.

Drupal Canvas matters for three reasons a fundraising leader will care about. It is a visual, drag-and-build interface, so marketers assemble campaign pages from a reusable component library, which feeds the speed pillar directly: appeal pages go live in minutes, not sprints. It is AI-native, with an assistant that can generate page sections and components from a plain-English prompt. And it is built on a modern, component-based architecture, so the donor experience can keep evolving rather than being locked into a legacy layout model.

Vardot, as a Drupal AI initiative Gold sponsor, believes that AI in a Drupal donation platform runs deeper than the page builder. An agent-ready platform, one with well-structured content and a machine-readable repository, lets AI tooling operate on the site safely, and points toward AI applied to donation outcomes: personalization, content structuring, and donor insight. That is what keeps a donation platform current rather than dated.

The bottom line for NGO donation platforms

For an NGO, the decision is not which Drupal modules to install. It is whether the platform delivers the capabilities that raise more money safely: recurring giving, payments in every market, PCI-grade security, donor data you own and can sync, and the headroom to survive a crisis appeal. Modules are how those capabilities get built. The capabilities are what you are buying.