@clickforafrica Thank you very much for helping with the plugin’s support! It’s true that transactions can stay in the mempool for long if the fees are set too low for the current network conditions.
@enochdavid, since you are using the CoinPayments adapter, the actual network fees are set for you, so you don’t need to worry about them.
I suspect that you are on a site that’s currently under development, or otherwise receives very little traffic. Some background:
For withdrawals to proceed, the cron jobs must be triggered a few times. Normally WordPress cron jobs get a chance to trigger only if someone visits your site. Otherwise, WordPress doesn’t get a chance to run and therefore cannot process transactions. If this is the case, then your withdrawals should be staying in an unconfirmed or pending state for a long time. On the other hand, IF the transaction has already been submitted to CoinPayments and you can see it in the list of pending withdrawals in your CoinPayments screens, then this means that the plugin has done all it can, and it’s now on CP to execute the transaction.
If the transactions are not being attempted (and therefore take a long time to reach the CP server), then the solution is to trigger the cron url manually from an external source. See *Wallets* → *Cron job* → *PRO TIP* for details. If you set something to trigger that url every one minute then the cron jobs can run without delays.
Hope this helps. Please let me know if something was not clear. Do your withdrawals reach the CP server quickly and then get delayed there, or do they get delayed at the plugin before being attempted?
with regards,
Alex
