Run a Pre-Launch Check on Your Charitable Donation Setup with AI
Before Giving Tuesday or any big push, get a plain-English check of your payment gateways, test mode, campaign end dates, and donation forms.
Prerequisites
A connected site running Charitable 1.8.18 or newer on WordPress 6.9 or newer. The check is read-only.
I use Charitable on my WordPress site and I have a big fundraising push coming up on [date]. Run a pre-launch check. Use the Charitable abilities, and only read-only ones: do not create or change anything. Get the plugin info, the site environment, and the payment gateway status. Then give me a checklist with a clear pass, warning, or fail for each of these: whether at least one payment gateway is enabled, whether each enabled gateway is connected, whether any gateway is still in test mode, which gateway is the default, and the versions of Charitable, WordPress, and PHP. Then list my campaigns and flag any published campaign that has already ended or ends before my push date, any with no goal set, and any that are still drafts, and tell me which campaign looks like the one I am about to promote so I can confirm it. For that campaign, read its details and tell me the suggested amounts, whether custom amounts are allowed, and the minimum donation. For every warning or fail, give me one line on why it matters and the wp-admin screen where I fix it. Do not guess at anything the abilities do not return; say it was not checked. End by reminding me to make one small real donation on the live page and refund it, since that is the only full test.
Skip pasting the full prompt. Drop this into your AI on a site that already has WPVibe:
Run the “Run a Pre-Launch Check on Your Charitable Donation Setup with AI” recipe from the WPVibe cookbook on my connected site.
Giving days are won or lost in a few hours, and the failures are dull ones. The gateway was still in test mode. The Stripe connection had lapsed. The campaign everyone is being sent to ended last Friday. Nobody finds out until a supporter replies to the appeal email to say the page would not take their card, and by then the email has gone to the whole list.
The AI runs Charitable's diagnostic abilities, which report your plugin and site environment and the status of every payment gateway: enabled or not, live or test mode, connected or not. Payment credentials are never part of what Charitable lets an AI read, only the status. Then it goes through your campaigns and flags the ones that have ended or are about to, that have no goal, or that are still drafts. Everything is read-only. You get a checklist, and you make the fixes.
Paste the prompt as it is, a few days before the push and again that morning. Then do the one thing no check can do for you: make a real donation of a small amount on the live campaign page, with a real card, and refund it afterwards. A connected gateway in live mode is a very good sign. A receipt in your inbox is proof.
Outcome
A pass, warning, or fail for everything that could stop a donation on launch day, with where to fix each one.