Charitable Documentation

Learn how to make the most of Charitable with clear, step-by-step instructions.

Charitable has noticed some recent donation attempts via the donation form have failed due to invalid security checks

If you see a dashboard notice that reads “Charitable has noticed some recent donation attempts via the donation form have failed due to invalid security checks,” this guide explains what it means and how to resolve it.

The important thing to know first is that this single notice can point to two very different situations. One of them can block real donors and needs your attention. The other is Charitable correctly blocking automated spam and is usually harmless. Before you change any settings, identify which one you are dealing with.

What This Notice Means

Every time your donation form loads, Charitable adds hidden security checks to make sure the submission is genuine. Two of those checks are:

  • A security token (nonce) – a unique, time-limited code that proves the form was loaded normally and submitted from your site.
  • A honeypot – a hidden field that real visitors never see or fill in. Automated bots routinely fill in every field they find, so a completed honeypot is a reliable sign of spam.

When either check fails, Charitable blocks that submission and records it. If enough blocked submissions happen in a short window, the dashboard notice appears. Because the notice uses the same wording for both checks, the only way to know what is actually happening is to look at which check failed.

First, Identify the Cause

Charitable logs every blocked submission so you can see the exact reason. To view the log:

  1. In your WordPress admin, go to Charitable > Tools > System Info.
  2. Find the Form Errors section, which shows the number of errors today and this week. You can also export the full log to a CSV file.
  3. Look at the error code on each entry.

The error code tells you which path to follow:

  • nonce_failed – the security token did not match. This is almost always a caching problem, and it can turn away real donors. Follow Cause 1.
  • honeypot_failed – the hidden anti-spam field was filled in. This means an automated bot was blocked, not a real donor. Follow Cause 2.

Two context clues in each log entry help confirm the honeypot case: the submission usually comes from a logged-out visitor, and the user agent is often an outdated or automated browser rather than a normal, current one.

Cause 1: Caching and Security Tokens (nonce_failed)

If your log shows nonce_failed entries, the cause is almost always caching. When a page that contains a donation form is cached, visitors can be served an old copy of the page with an expired security token. The form then fails verification, and the donor sees: “Unfortunately, we were unable to verify your form submission. Please reload the page and try again.”

Other, less common causes are a conflicting plugin or theme, or an aggressive browser cache.

Work through these steps:

  1. Check for caching plugins. Review whether caching is active, either through a plugin or through your hosting provider or CDN (such as Cloudflare).
  2. Exclude your donation pages from caching. In your caching plugin or host settings, add the URLs of any page that contains a donation form (such as your campaign and donation pages) to the cache exclusion or bypass list. Exclude server-level and CDN caching as well, not just the plugin.
  3. Test for plugin conflicts. If caching has been ruled out, temporarily deactivate other plugins (after taking a backup) to check whether another script is interfering with the form.
  4. Clear your browser cache. This is separate from server-side caching and worth ruling out.

As a last resort, if your host cannot bypass caching on specific pages, a WPCode snippet can relax the form’s security check. This is not recommended and should only be used if the steps above are not possible: https://library.wpcode.com/snippet/7oq3yl5w/

Cause 2: Spam Bots Caught by the Honeypot (honeypot_failed)

If your log shows honeypot_failed entries, the news is good. These are automated spam bots that probed your donation form and were caught by the hidden honeypot field. Charitable blocked them before they ever reached your payment gateway. Your real donations are not affected, and no genuine donor is being turned away.

A small, steady trickle of blocked bots is normal for any public donation form, and it is enough to trigger the dashboard notice. In this case the notice is simply letting you know the protection is working.

You do not have to do anything. If you would like to cut down on the bot attempts, and how often the notice appears, add another layer of protection in front of the form:

  1. Enable a CAPTCHA. Go to Charitable > Settings > Security and turn on one of the CAPTCHA options, such as Google reCAPTCHA or Cloudflare Turnstile. A CAPTCHA stops most bots before they can submit, which reduces these blocked attempts.
  2. Turn on additional bot protection. In the same Security settings, you can enable extra measures such as the honeypot and time-trap bot protection, rate limiting, and email validation for stronger coverage.

Dismissing the Notice

The notice can remain for several days even after the underlying cause is addressed. It clears on its own once there are no new failures, and you can dismiss it manually at any time from the dashboard.

Still Need Help

If you have identified the error code and worked through the matching steps above and donations are still failing, contact Charitable support. It helps us if you include the error code from your Form Errors log (nonce_failed or honeypot_failed), since that tells us immediately which cause we are dealing with.

Still have questions? We’re here to help!

Last Modified:

What's New In Charitable

View The Latest Updates
🔔 Subscribe to get our latest updates
📧 Subscribe to Emails

Email Subscription

Join our Newsletter

We won’t spam you. We only send an email when we think it will genuinely help you. Unsubscribe at any time!

Donations New

👥 Introducing Donor Merging: Two Records, One Supporter!

Somewhere in your donor list is a supporter who appears twice, because they gave from a work address one year and a personal one the next. Every donation is still recorded and every receipt still went out, but a loyal supporter who has given for years can look like two people who gave half as much. From the Charitable Pro plugin 1.8.19.1 you can find those records and merge them from the Donors screen. Why this is important:

  • 🔍 A Find Duplicates link where you already work: Head to Charitable » Donors and it sits next to Filter and Export, then tells you how many groups of possible duplicates it found.
  • 🧩 Grouped by name, not by email: Charitable compares the first and last name together and ignores capital letters, spacing and punctuation, which is what catches the same person under two different addresses.
  • 📊 A preview before anything changes: Each group shows every record with its email address, its donation count and its lifetime total, and the preview shows you the combined totals and the email that will be added.
  • ↩️ Every merge can be undone: Nothing is merged until you choose to merge it, and you can reverse any merge afterwards, so a wrong guess costs you nothing.
  • 📥 Built for the week after an import: Moving donors over from another plugin is where most duplicates come from, and it is also when they are hardest to spot, because every record is new to you.

Check out our announcement here.

ambassadors New

🔑 Introducing Passwordless Fundraisers: Sign Up With Just an Email!

Supporters arrive wanting to help, and then the form asks them to invent a password for a website they may only visit twice. A lot of them stop right there. Passwordless Fundraiser Accounts, new in Charitable Ambassadors 3.5.0, let a supporter start a peer to peer fundraiser with nothing but an email address. Why this is important:

  • 🔑 No password step to lose them at: Switch it on in Charitable » Ambassadors » Templates » Submit Form and the create-fundraiser form asks only for a name, an email address and a page title.
  • 👤 Still a real WordPress account: One click in one email confirms the address, signs them in and creates the account, so they can come back later to edit their story, change their photo and see who has donated.
  • 🎚️ Your call on every campaign: Each peer to peer campaign can follow the site default or override it, which matters when a campaign pays fundraisers through Stripe Connect and those people do need a password.
  • 📋 See who has not clicked yet: The Charitable » Ambassadors » Directory » Awaiting Sign-In tab lists everyone still waiting, with the campaign they joined and a Resend button, so a typo or a spam folder is something you can spot and fix.
  • 🛡️ Links a scanner cannot use up: Opening the link only shows a page, and your fundraiser is signed in when they press the button on it, so corporate email scanners never burn the link. Each one works once, expires on its own and is stored only as a hash.

Check out our announcement here.

ambassadors New

🏃 Introducing Activity: Show Progress on More Than Money!

Most peer-to-peer fundraisers are about more than the money. A read-a-thon is about minutes read, a walkathon is about miles walked, and a food drive is about meals packed. Activity for Charitable Ambassadors lets your fundraisers show that effort right beside the dollars they raise. Why this is important:

  • 🎯 Progress on what you actually count: A progress bar shows each thing you count against its own target, sitting right beside the money raised.
  • 🏅 Milestones for the yes or no things: A milestone badge marks the efforts that are simply done or not done, with no number to chase.
  • ✍️ Fundraisers log their own numbers: Your supporters enter their totals from their own pages, so the effort stops living in a spreadsheet, a comment, or nowhere at all.
  • 🤖 Some numbers count themselves: An AUTOMATIC tag appears wherever the site worked the figure out from completed donations, so you can see at a glance what nobody typed in.
  • 🧩 Set it up once, use it anywhere: You decide what gets counted one time, then choose which campaigns count it. Available now in Charitable Ambassadors 3.4.7, with no new plugin and no developer.

Check out our announcement here.

ambassadors New

🖨️ Introducing Fliers and Posters: Raise Money Away From the Screen!

A lot of peer-to-peer fundraising happens away from a screen: at the finish line of a 5K, on a school noticeboard, in an office kitchen. Charitable Ambassadors 3.4.7 adds 2 printables, a fundraiser flier carrying each fundraiser’s own story and QR code, and a recruitment poster that signs new fundraisers up. Both open as a normal web page and print straight from the browser. Why this is important:

  • 🏁 A flier for every fundraiser: Each one carries that fundraiser’s own photo, story and goal, with a QR code that opens their page rather than your main campaign.
  • 📌 A poster that recruits: It shows “Now Recruiting” above your campaign name with a large QR code that opens your sign-up form, so someone can start fundraising without waiting on a link from you.
  • 🪄 No design tool needed: Both printables render as a normal web page and print from the browser, with no PDF plugin and no designer.
  • 📄 2 flier layouts: Hand out carries the full story for giving to friends and family, and Post up carries a short hook with 5 tear-off tabs for a noticeboard.
  • 🛡️ Off until you switch it on: Fliers stay off after the update until you enable them under Charitable » Ambassadors » Other » Fliers, and only the owner or an administrator can open one.

Check out our announcement here.

Improvement Payments

💸 Introducing Tiered Rates for Fee Relief: Match the Ask to the Gift!

Fee Relief asks your donors one short question at checkout: would you like to cover the processing fee on this gift? Until now that question used a single rate for every donation on a gateway, so a $10 gift and a $500 gift were asked for the same percentage. Fee Relief 1.3.0 lets you set as many donation bands as you like, each carrying its own rate. Why this is important:

  • 🪙 Gentler on small gifts: A fixed transaction cost is a far bigger share of a $10 donation than a $500 one, so bands let you ask for less at the bottom.
  • 🎚️ As many bands as you need: Each band carries its own percentage and its own fixed amount, and the top band runs on with no upper limit.
  • 🛑 An optional ceiling: A Maximum fee field stops any donor being asked for more than a number you choose, however large the gift.
  • 🔌 Set per payment gateway: Stripe can run on four bands while Windcave and Payfast stay on a single rate, because bands belong to a gateway and not to your whole site.
  • 🛡️ Nothing changes until you say so: Your current rates stay exactly as they are until you switch Use Tiered Rates on under Charitable » Settings » Advanced » Fee Relief.

Check out our announcement here.