Complete GiveWP Setup Guide: Accept Donations on WordPress (2026)

Installing GiveWP takes two minutes. Configuring it so donors actually complete their gift takes about ninety. The gap between those two numbers is where most nonprofit websites lose money.

This guide covers the full setup: connecting a payment processor, building your first form, enabling recurring gifts, handling tax receipts, and the settings that measurably affect completion rates. We use GiveWP because it’s the most widely deployed donation plugin for WordPress, with over 100,000 active installations and a mature feature set built specifically for nonprofits rather than adapted from eCommerce.

If you haven’t built your site yet, start with our step-by-step guide to building a nonprofit website in WordPress and come back here for the donations layer.

Before you start: three things to have ready

• Your organization’s legal name and address exactly as registered. This goes on tax receipts and can’t be casual.
• Your 501(c)(3) determination letter (or equivalent registration in your country). Stripe and PayPal both offer reduced nonprofit rates, but only after you verify status.
• A decision on your donation tiers. Have three or four amounts in mind, and know what each one buys. “$50 provides clean water for a family for six months” converts far better than a bare number.

That third item is the one people skip, and it’s the one that affects revenue most. Work it out before you touch the plugin.

Step 1: Install GiveWP and run the onboarding wizard

In WordPress admin, go to Plugins → Add New, search for GiveWP, then install and activate. The free core plugin handles one-time donations, receipts, and donor records enough to start accepting money today.

The setup wizard launches automatically. It asks for:

• Your cause type affects which default templates GiveWP suggests
• Country and currency set this correctly now; changing currency after you have donation records creates reporting mess
• Your organization name appears on receipts and donor-facing emails

Finish the wizard. Don’t worry about getting every choice right everything here is editable later under Donations → Settings.

Step 2: Connect Stripe (and why we recommend it first)

Go to Donations → Settings → Payment Gateways. You’ll see Stripe, PayPal, offline donations, and a test gateway.

Start with Stripe. It handles card payments natively inside your donation form, which means donors never leave your site and every extra page in a donation flow costs you completions. PayPal redirects by default, which is why we treat it as a secondary option rather than the primary one.

Connecting Stripe

1. Click Connect with Stripe. You’ll be handed off to Stripe to authorize or create an account.
2. Complete Stripe’s business verification. For a registered nonprofit this needs your EIN and organization details.
3. Once returned to WordPress, confirm the connection shows as active.
4. Enable Stripe Payment Element if offered it renders the card fields inline and supports Apple Pay and Google Pay, which convert noticeably better on mobile.

Apply for nonprofit rates

Stripe’s standard rate is 2.9% + 30¢ per transaction. Registered nonprofits can apply for a reduced rate of 2.2% + 30¢. On $50,000 raised annually that’s roughly $350 back to your mission. Apply through Stripe’s nonprofit program after your account is verified it isn’t automatic and it isn’t retroactive, so do it early.

Adding PayPal as a second option

Some donors older cohorts especially trust PayPal more than entering a card. Offering both typically lifts completion. Enable PayPal Donations under the same Payment Gateways tab and connect your business account. Just keep Stripe as the default so the fastest path stays the default path.

Step 3: Build your first donation form

Go to Donations → Add Form. Name it something you’ll recognize in reports “General Fund 2026” beats “Donation Form 1” when you have six of them.

Donation levels: use multiple, and label them

Choose Multi-level Donation rather than a single amount or a blank field. A blank field asks the donor to do arithmetic and guess what’s appropriate; preset tiers anchor the decision.

Four levels plus a custom option is the pattern that works:

Two things matter here. First, label every tier with impact, not just currency a labelled tier reliably outperforms a bare number. Second, pre-select your second tier as the default. Whatever you highlight becomes the most-chosen amount, so highlight one step above your comfort level.

Keep required fields to a minimum

Every required field costs you completions. Require first name, last name, and email. That’s it. Address only if you legally must issue mailed receipts. Phone number should be optional or absent it is one of the most common causes of abandoned donation forms and it rarely gets used.

Enable fee coverage

Turn on the option letting donors cover processing fees. Between 60 and 70 percent of donors accept when it’s presented as a simple checkbox “Add $1.75 so 100% of my gift reaches the cause.” It’s one checkbox and it protects your net.

Step 4: Set up recurring donations

This is the highest-leverage step in the entire guide.

A monthly donor is worth several times a one-time donor over their lifetime, and recurring revenue is what lets you plan a budget instead of reacting to it. Recurring donations require the GiveWP Recurring Donations add-on (paid), and for most organizations it pays for itself within the first quarter.

Configuration that works

• Offer monthly as the default, annual as an alternative. Monthly feels smaller and converts better.
• Show the monthly equivalent next to one-time amounts. “$50 once, or $10/month” reframes the ask.
• Let donors set an end date or choose ongoing. Removing the sense of permanent commitment increases sign-ups.
• Enable the donor dashboard so people can update their card or cancel without emailing you. Failed cards are the leading cause of recurring revenue churn, and self-service recovery beats a support queue.

For deeper strategy on moving one-time givers to monthly, we’ve written about converting event attendees into recurring donors.

Step 5: Configure receipts and emails

Under Donations → Settings → Emails, three templates need your attention.

Donation receipt

This is a legal document in most jurisdictions, not just a thank-you. For US 501(c)(3) organizations it must include your legal name, tax ID (EIN), the gift amount and date, and a statement that no goods or services were provided in exchange. Check your own country’s requirements the defaults are a starting point, not compliance.

Beyond the legal minimum, make it warm. This email has the highest open rate of anything you will ever send. Use it: thank them specifically, restate the impact of the amount they chose, and include one link to something worth reading. Do not ask for another donation here.

New donation notification

Goes to your team. Route it to a shared inbox rather than one person’s address so gifts don’t sit unacknowledged when someone’s on leave.

Recurring donation reminders

If you enabled recurring giving, configure the renewal reminder and the failed-payment notice. The failed-payment email is the one that matters an expired card that nobody follows up on is silent, permanent revenue loss.

Make sure email actually sends

WordPress’s built-in mail function is unreliable and frequently lands in spam. Install an SMTP plugin WP Mail SMTP or similar and route transactional email through a real sending service like Postmark, SendGrid, or Amazon SES.

This is not optional. A donation receipt that goes to spam looks to the donor exactly like a payment that failed, and you’ll spend support time on a problem you could have prevented in fifteen minutes.

Step 6: Place donation forms where people will use them

A form nobody sees raises nothing. Put yours in these places, in this order of priority:

1. A dedicated /donate/ page. This is what you’ll link from email, social, and print. Make the URL short enough to say out loud.
2. Homepage hero. Either an embedded form or a prominent button. Above the fold.
3. Persistent header button. Available on every page without hunting.
4. Inside campaign and story pages. Place the ask directly after the story that motivates it, while the emotion is present.
5. Footer. Catches people who read to the end.

Embed a form with the shortcode GiveWP generates for it, or use the GiveWP block in the editor. If you’re running Alone, the donation form templates are pre-styled to match the theme, so embedded forms won’t look bolted on.

Step 7: Test the whole flow before you announce it

Enable test mode under Donations → Settings → Payment Gateways → Test Mode, then run a complete donation using Stripe’s test card 4242 4242 4242 4242 with any future expiry and any CVC.

Verify all six of these:

• The form submits without an error
• The donation appears under Donations → Donations
• The receipt email arrives check spam too
• The receipt contains your legal name, EIN, amount, and date
• Your team notification arrives at the right inbox
• The thank-you page displays rather than a blank screen

Then switch off test mode and process one real $1 donation with your own card. Test mode and live mode use different credentials and different webhooks; passing in test mode does not prove live mode works. Refund the dollar afterward, which also confirms your refund flow.

Run the mobile test separately. More than half of donations now come from phones, and a form that works on desktop can still be unusable on a small screen.

Common mistakes worth avoiding

These come up repeatedly in support:

• Leaving test mode on after launch. Donations appear to succeed and no money moves. It happens more often than you’d think check this first if gifts stop appearing.
• Requiring too many fields. Every additional required field measurably reduces completion. Audit yours and cut anything you won’t use.
• No recurring option. Leaving monthly giving off the table is the single largest missed opportunity in nonprofit fundraising.
• Unstyled forms. A donation form that looks different from the rest of your site reads as a security concern to donors, even when they can’t articulate why.
• Not connecting a proper email service. Receipts in spam generate support tickets and erode trust.
• Never testing on mobile. Most of your traffic; frequently the least-tested path.
• Ignoring failed recurring payments. Expired cards churn your most valuable donors silently unless someone follows up.

Frequently asked questions

Is GiveWP free?

The core plugin is free and handles one-time donations, receipts, and donor records. Paid add-ons cover recurring donations, peer-to-peer fundraising, additional gateways, and CRM integrations. Most nonprofits start free and add recurring donations once monthly giving justifies the cost.

What are the total fees on a donation?

GiveWP itself takes no cut. You pay your payment processor: Stripe’s standard 2.9% + 30¢, or 2.2% + 30¢ on the nonprofit rate. On a $50 gift at the nonprofit rate that’s about $1.40. Enabling fee coverage lets donors absorb this.

Can donors give without creating an account?

Yes, and they should be able to. Guest donations are enabled by default. Requiring registration before giving is one of the most damaging things you can do to your completion rate.

Does GiveWP work with any WordPress theme?

It works with any theme, but forms inherit whatever styling the theme provides which often means they look generic. Themes with dedicated GiveWP integration ship pre-styled templates instead. Alone is one of them, which removes the CSS work from this step.

How do I issue tax receipts automatically?

The donation receipt email doubles as the tax receipt once it contains your legal name, tax ID, gift amount, date, and the no-goods-or-services statement. Configure this under Donations → Settings → Emails. Verify the requirements for your own jurisdiction rather than assuming the defaults are sufficient.

Can I run multiple campaigns with separate tracking?

Yes. Create a separate form per campaign and each reports independently under Donations → Reports. Useful for comparing appeals, tracking specific projects, or restricted-fund accounting.

GiveWP or Charitable which should I use?

Both are solid. GiveWP has a larger install base, a deeper add-on ecosystem, and stronger recurring-donation tooling. Charitable is lighter and cheaper at the entry tier. If you expect to grow into recurring giving and peer-to-peer campaigns, GiveWP has more room to grow into.

What happens to donations if I switch themes?

Nothing. Donation records, donor data, and forms live in GiveWP, independent of your theme. Switching themes may change how forms look, but no data is lost.

After launch: what to watch

Setup is the beginning. These are the numbers that tell you whether it’s working:

• Form completion rate. Of the people who start a donation, how many finish? Below 50% means something in the form is losing them usually too many fields or a gateway problem on mobile.
• Average gift size. If it clusters at your lowest tier, your tiers are anchored too low. Try raising them.
• Recurring conversion rate. What share of donors choose monthly? Under 10% means the option isn’t prominent enough.
• Failed recurring payments. Check monthly. Every unresolved failure is a lapsed donor who intended to keep giving.
• Mobile versus desktop completion. A large gap points to a mobile-specific problem worth fixing immediately.

Review these monthly for the first quarter, then quarterly. Small improvements to a donation form compound in a way that new content rarely does.