The challenge
A US nonprofit was using GiveWP with Authorize.Net to accept donations. Some payments appeared in Authorize.Net but were missing from the corresponding WordPress donation records. The site also had failed and pending Action Scheduler jobs, making it difficult to trust that background tasks were being processed consistently.
Investigation and fix
I investigated the WordPress scheduled-task setup and the Action Scheduler queue, then coordinated with the hosting provider. WordPress's built-in cron approach was replaced with a server-side cron job configured to run approximately every 10 minutes, helping the site process queued tasks more reliably.
- Investigated pending and failed Action Scheduler jobs.
- Reviewed the WordPress cron configuration and coordinated the hosting-side change.
- Set up a recurring server cron to process scheduled tasks approximately every 10 minutes.
- Helped simplify conflicting anti-spam measures by using Cloudflare Turnstile with WP Armour.
- Recommended additional Authorize.Net security-setting changes for the site owner to review.
Outcome
The client tested the donation workflow and confirmed that synchronization was working again, although records could appear with a small delay. The change addressed the underlying scheduled-task processing issue rather than treating each missing donation as an isolated problem.
After the anti-spam changes, reported spam and suspected fraudulent donation attempts also decreased—from roughly 5–10 attempts in the earlier period to around 1–2 per month afterwards.
What this demonstrates
Donation systems rely on more than the payment gateway alone. WordPress cron, background queues, hosting configuration and spam controls can all affect the reliability of the full workflow. A structured investigation can help identify where processing is breaking down.