Troubleshooting Common Issues
Solutions to the most common AshePay issues: missed payments, cron problems, RPC failures, and more.
Payments are not being detected
This is the most common issue and is almost always caused by one of three things:
Quick checklist
- Did the customer send to the exact wallet address shown on the payment page?
- Did the customer send the exact amount (within 0.5%)?
- Is WP-Cron running? (check the admin health notice)
- Is the RPC endpoint working? (use the Test Connection button)
- Is the order still within the payment window (not expired)?
WP-Cron is not running
AshePay relies on WordPress's built-in WP-Cron to scan the blockchain every minute. WP-Cron only fires when someone visits your site - on low-traffic sites, there may be long gaps between scans.
If you see a "Cron health warning" banner in your admin, it means the cron has not run in over 5 minutes.
[IMAGE: WordPress admin notice reading "AshePay Warning: WP-Cron has not run in the last 5 minutes. Payments may be delayed." with a yellow warning icon]
Fix: Set up a real server cron job to call WP-Cron on a schedule:
- Connect to your server via SSH or cPanel cron manager
- Add this cron job to run every minute:
* * * * * wget -q -O /dev/null https://yoursite.com/wp-cron.php?doing_wp_cronReplace yoursite.com with your actual domain.
RPC connection failure
If the default RPC endpoint for a chain is down or rate-limited, AshePay cannot scan the blockchain for that chain.
Fix:
- Go to WooCommerce → Settings → Payments → AshePay
- Click Test Connection on the affected chain
- If it fails, replace the RPC URL with a private endpoint from Infura, Alchemy, or QuickNode (free accounts available)
See the Custom RPC Endpoints guide for details.
Wrong amount sent
If the customer sent an amount that is more than 0.5% below the expected amount, the payment is flagged but not auto-accepted. You can find it in the Transactions tab. Options:
- Manually complete the WooCommerce order if you decide to accept the underpayment
- Ask the customer to send the remaining difference
Database tables are missing
If you see a notice like "AshePay database tables are missing", the setup process did not complete correctly during activation.
Fix: Click the Re-run Setup link in the notice. This recreates all tables and is safe to run on an existing installation without data loss.
Admin bar badge is not showing
The badge only appears when there are active pending crypto payments. If no orders are awaiting payment, the badge is intentionally hidden.
If you have pending orders but no badge:
- Confirm the Enable admin bar badge option is turned on in AshePay settings
- Check that you are logged in as an admin or shop manager
- Clear any caching plugin that might be serving a cached admin bar
Order stuck on "On-Hold" after payment confirmed on-chain
AshePay runs a retroactive scan every time you open the Transactions tab. This scan detects payments that were confirmed on-chain but not automatically picked up (e.g., during a cron outage) and updates the order status.
Fix: Go to WooCommerce → AshePay → Transactions. The scan runs automatically on page load. If the order is still not updated, you can manually complete it directly in WooCommerce - AshePay will sync its own record automatically when you do.
Conflict with a caching plugin
Caching plugins (WP Rocket, W3 Total Cache, LiteSpeed Cache, etc.) should be configured to exclude:
- All WooCommerce pages (cart, checkout, account, order-pay)
- Any URL containing
order-pay - The admin area
Most caching plugins have a built-in WooCommerce exclusion setting - make sure it is enabled.
Need more help?
Free version: WordPress.org support forum
Pro version: Email [email protected] - include your order ID and a description of the issue.