25 WordPress plugins for donations and fundraising: costs, campaigns and tracking

Choose between a support button, a campaign and a project platform

Receiving one-off support for a project, tracking an association’s donations and hosting campaigns from several organisers do not require the same system. A button can link to a payment page already prepared. A donation form adds amounts, donor information and tracking. A crowdfunding platform must also organise projects, their owners and the destination of funds. Start by describing what your team must find after a contribution. This result helps the choice more than a long list of gateways advertised on a sales listing.

The 25 families in this selection are dedicated to donations or fundraising. Their free and commercial editions and alternative connectors are not counted multiple times. General-purpose forms, shops and membership tools already covered are not used to make up the number. Some solutions remain in WordPress; others display an external service whose account holds the donation history. A Ko-fi contribution therefore does not have the same scope as a GiveWP-managed campaign or an IgnitionDeck project platform. First select the necessary level, then compare a few tools in that family.

Prepare a simple case: a named project, a one-off donation, a person responsible for tracking and an amount the team can reconcile with funds received. Add recurring payments only if you know how the donor will recognise and stop them. If several owners can create campaigns, specify who approves them and controls their destination. This is documentary research: no fundraising account, payment, receipt or public campaign was created for the article. Run the proposed journeys in your environment with working data and available test facilities.

Compare subscriptions, commissions and payment fees on the same basis

Separate three lines in your estimate: plugin licence, platform commission and payment processing. Free may describe only the download: Charitable Lite adds 3% per transaction and Accept Donations advertises 1% in its free edition. Donorbox Standard charges 2.95% on basic forms, then the processor charges apply. Givecloud combines a subscription, commission and separate processing. Compare the same frequency, country, volume and options. For a working donation of 100 euros, record percentage fees and the fixed amount separately; this preparatory calculation does not replace the provider’s contract.

Terms were consulted on November 3, 2026. Charitable Basic displays 69 USD for the first year against a normal price of 149 USD per year; SureDonation Pro displays 79 USD for the first year, then 149 USD, with a different website scope. These introductory amounts must not become the permanent budget. For an annually billed platform, also distinguish the prepaid amount from its monthly equivalent. Do not transfer a card rate presented for a US organisation or an account in another currency to your association. The notice flags taxes or terms that could not be established.

Optional service contributions and donors covering fees form another line. Examine the total displayed before confirmation, who receives each amount and what happens if the donor refuses the supplement. Raisely presents a model with optional contributions and an alternative with platform fees; Zeffy advertises fee-free fundraising for eligible organisations, funded by optional contributions to the service. These offerings do not automatically cover the same countries or structures. A zero platform percentage alone does not establish that every payment will be free.

Check country, data and dependencies before installation

The first filter is service access. HelloAsso presents itself as a solution for French associations; GoFundMe Pro states that the organisation must be headquartered in the United States. Also check currency, documents needed for the account, who may change the beneficiary and payment methods actually available. A banner showing several currency symbols does not answer these questions. First exclude offerings whose scope does not match your organisation, even if the plugin can technically be installed in WordPress. Zeffy now admits six countries, including the United Kingdom, Ireland and Germany, but not France. Donor country and organisation country are not interchangeable: a form accessible from France does not guarantee that a French organisation can receive funds through the service.

Next identify where the team will work. With Donorbox, Funraise or Givecloud, the plugin embeds a platform retaining an essential part of administration. With a local solution, WordPress and its database need their own monitoring, backup and suitable permissions. Prepare the necessary information list: donation reference, campaign, gross amount, fees, status, payout and possible recurrence. A public counter does not replace this record. Request an example export or consult its description before depending on a format the organisation cannot reuse.

Finally read dependencies at the level of the journey used. Donation Platform for WooCommerce requires a subscriptions module for recurring donations and its documentation recommends classic checkout for all features. SUMO Donations requires SUMO Subscriptions for recurring donations. The first plugin’s cost therefore does not necessarily cover your entire project. Prepare a working copy, disable real notifications and integrations, then back up the configuration before the trial. If you use WordPress.com, check that your plan permits the necessary extensions. Do not open a production multisite network merely to examine a new form.

Journey 1: link an already prepared fundraiser without installing a plugin

This journey suits an organisation that already has an approved public fundraising page in the chosen service. It requires access to edit a WordPress page and the campaign’s exact public URL, supplied by its administrator. Use a copy or working page; do not copy a login address or private management link. Note beneficiary and campaign names to compare after clicking. The aim is clear access to this existing fundraiser; WordPress will not handle its payment or donor history.

Under Pages, open Add New Page or the working page to edit. In the block editor, use the plus button to add the Buttons block, then write a label identifying the supported project. Select the button, open its link control and paste the full public address. Save the draft and use the preview. Check text, destination and campaign name on a small screen and computer. Avoid labels promising a receipt or deduction if the organisation has not defined the relevant terms. A correct destination matters more than button colour.

Then open the preview as a visitor and follow the link to the public page without entering a card or confirming a donation. You should find the expected campaign and beneficiary, with the service’s displayed terms. This check establishes only that the link reaches its destination; it does not validate collection of funds. The team must complete the payment journey in the provided test mode, where available and authorised. To reverse the change, remove the block from the working page or restore its revision. No new plugin or local form was needed.

• Obtain the campaign’s approved public URL and prepare a working page.
• Add a Buttons block, enter the project label and set the link.
• Save the draft, then verify campaign and beneficiary from the preview.
• Stop the check before any real payment; remove the block or restore the revision if the destination is unsuitable.

Journey 2: display a simple button with Donations via PayPal

This proposed journey concerns a website wanting to display a PayPal button configured in WordPress without building complete campaign management. It requires a suitable beneficiary account and administrator access to a working copy. Under Plugins > Add New, search for Donations via PayPal and check the paypal-donations slug to avoid a namesake. After installation and activation, the documentation places settings under Settings > PayPal Donations. Record the initial configuration before changing it. The prototype aims to check the destination address, currency and purpose without triggering a real transfer.

Enter the authorised beneficiary’s PayPal identifier, then the currency and useful optional values, such as the purpose or return page. Do not enter a PayPal password in a field intended for an identifier. Save settings, then open a working page in the editor. Add a Shortcode block and paste [paypal-donation], the simple form documented by the plugin. It uses the values defined in settings. Initially keep these shared values so you can compare the result instead of multiplying per-page variations. Save the draft and examine its preview.

Click the button only to check the destination and presented information, then stop before confirming any payment. If the information does not match the expected beneficiary, restore settings and remove the shortcode. Returning to a thank-you page alone does not establish that a donation is paid; payment validation requires the test journey actually supported by the integration. To abandon the prototype, first remove its button, then deactivate the extension on the copy. Keep useful settings: the documentation states that deleting the plugin erases its options.

• Install the paypal-donations plugin on a copy and open Settings > PayPal Donations.
• Enter the authorised beneficiary identifier, currency and purpose, then save.
• Add [paypal-donation] in a Shortcode block on a working page.
• Check the preview and destination without payment; restore settings or remove the block if there is a discrepancy.

Journey 3: prepare a donation project in WooCommerce

This journey is for a team already possessing a shop copy and wanting to examine Donation Platform for WooCommerce there. It requires configured WooCommerce, product management access and a gateway with correctly enabled test mode. Disable real emails, webhooks and integrations on the copy. First check that checkout uses the classic shortcode: the plugin documentation recommends classic checkout for full support, notably fee and ranking checkboxes, and reports incompatibility with the new product editor. If your journey depends on these elements, choose another prototype instead of globally modifying the active shop.

Under Products > Add New, prepare a working item with an explicit name and regular price used as the default donation amount. Enable Donation Project in its data, then open the Donation Form tab for form settings. A goal and end date may be entered, but the documentation states that they do not automatically prevent new donations. On the protected copy only, publish this working product to make it purchasable, then check its page. A product left in draft does not offer visitors the complete journey. The expected result is a chosen amount linked to this project, with a path to test checkout whose every step the team understands.

If the copy already uses the official WooCommerce Stripe extension, open WooCommerce > Settings > Payments > Stripe > Settings. In account details, choose Configure connection, then Test: the test connection is separate from Live. Connect an authorised test account and check its status and test webhooks. Then tick Enable test mode and save. Merely changing the display in the Stripe dashboard does not switch the shop. For the card, use only test number 4242 4242 4242 4242 with a future date and fictitious CVC; never a real card. This mode simulates payment without verifying an actual bank payout.

Make the donation only with the gateway’s test data and check its status in the working order. Compare campaign, amount, currency and any supplements against the expected result. General settings are documented under WooCommerce > Settings > Donations; if the copy also serves as a shop, examine compatibility mode before extending use. To stop the campaign, the documentation suggests the out-of-stock product status; returning the test product to draft also removes its publication. Keep records and configuration before removing the plugin, without deleting historical orders to tidy the screen. Do not reconnect the copy to Live mode after the trial. Keep the test isolated and remove the working product; real publication will require separate configuration.

• Prepare a protected copy with classic checkout and real emails/integrations disabled.
• Create a product with a regular price, enable Donation Project, configure Donation Form, then publish only on the protected copy.
• With WooCommerce Stripe already present: connect the account under Configure connection > Test, check test webhooks, enable Enable test mode and save.
• Make a donation with Stripe test data; reconcile the order reference and payment in the test account.
• Unpublish the working project, retain useful records and keep the copy away from real payments.

Check the recorded donation, payout and recurrence separately

A thank-you screen, a donation marked paid and a payout to the organisation’s account are three elements to reconcile. Prepare a checklist with campaign reference, requested amount, optional supplements, currency and expected status. In the available test mode, examine a successful payment, abandonment and declined attempt. A failed attempt must not be treated as funds collected in your tracking. Compare plugin or service data with gateway data. This check avoids treating simply opening a form as completed fundraising. In WooCommerce, a test order may resemble a real order and trigger automation: the gateway’s test mode alone does not disable shipping, accounting or emails.

For recurrence, note the frequency, start date and amount presented before confirmation. Identify where the donor will view their commitment and request its termination. Test this journey only with the actually documented test mechanism and a working subscription, never with a real debit created to see what happens. Check the distinction between a paid instalment and an active series, then how a declined payment is handled. No plugin lets you infer a different gateway’s behaviour from the success of a single one-off form.

Finally assign payout reconciliation to one person and tracking verification to another if the organisation provides for it. Keep useful references without copying card data into WordPress or a diagnostic spreadsheet. When an export combines several campaigns, check that a contribution remains assigned to the correct project and fees are not confused with the gross amount. Also define refund handling and its record in the tools used. These are system acceptance criteria; no payout, subscription or refund was executed for this selection.

Organise receipts, public data and team access

A thank-you email and PDF do not prove that the organisation may issue a tax receipt. Technical document production and organisational eligibility are separate questions. In France, Service Public describes the charitable giving tax ruling process for asking the administration about an association’s situation and ability to issue receipts entitling donors to a tax reduction. Therefore have rules and an authorised template defined before enabling automatic issuance. This article does not calculate a tax reduction or validate your organisation’s status; it helps choose and verify a WordPress tool.

Define what should appear publicly on a campaign. A donor list, comment and amount may be displayed differently from a name retained for internal tracking. Prepare a working donor, an anonymous contribution choice where the tool offers it and a logged-out page view. Compare what is visible with the expected result, including progress blocks and lists reused elsewhere on the website. Do not use real people as test data. An option labelled anonymous is insufficient to prove that every website output hides identity.

Assign access by task: editing the page, reading donations and changing the beneficiary account should not be conflated for convenience. Also check external accounts shared by the team and how access is removed when someone leaves. Prepare a local data backup and hosted data export according to your needs. A retrieved file must be readable and linked to the correct campaigns; a mere export promise in a sales offering does not guarantee recovery of every necessary detail. Keep working documents in a space suited to the organisation.

Choose a maintainable solution and prepare a clean exit

For fundraising already administered elsewhere, start with a link or suitable connector instead of recreating the same form in several tools. For local management with campaigns and history, compare free-core and module features on your example. If the shop already exists, examine the WooCommerce route without assuming every block or gateway will work with the donation plugin. A project platform run by several organisers additionally requires clearly defined permissions, approvals and fund handling. The advertised feature count remains secondary to that journey.

Connector maintenance and external service maintenance are separate checks. Funraise and Raisely update fields date to 2025; this calls for a prototype on the targeted WordPress version, even if the platform continues evolving. SUMO and WP Attractive also display 2025 dates, without proving abandonment. The notices specify observed versions and discrepancies. WP Crowdfunding now advertises a tool towards Growfund, but its licence and data migration are not assumed. For GiveWP, the current pricing table covers a Liquid Web suite: its price does not become the plugin-only price.

Before changing tools, inventory forms used, public links, campaigns, donations and recurring commitments. Prepare data retrieval, then a plan to remove old buttons without losing tracking of contributions already recorded. Disabling a plugin does not necessarily stop payments managed by an external service. Have this confirmed in the relevant exit procedure. Once the prototype is selected and checked, document a few reference cases to replay after an update. The team must recognise correct fundraising and explain where it finds its history.