Hi @ripperman, thanks for dropping us a message about this.
I would still certainly see if your payment gateway provider has any kind of error logs or way to view further details of a transaction. “Pending payment” naturally could be showing transactions that were unable to complete due to blocking, but it’d be good to rule out other causes like user abandoning the page before completing.
We generally don’t recommend allowlisting IPs as it allows them to bypass all Wordfence security, so if those are ever reassigned it could be problematic.
It sounds like learning mode could possibly help you out.
From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. If you’re able to replicate real transactions with test data on your payment gateway, run through the process with this enabled to teach Wordfence what’s happening is normal and should be allowed in future. After you have finished, switch the WAF from Learning Mode back to Enabled and Protecting.
Thanks,
Peter.
Oh that’s interesting. I didn’t think of learning mode.
We’ve enabled learning and carried out a number of transactions (all successful). Do we allow the firewall to remain in learning mode for another few days? I am aware that we’re not fully protected here while in this mode though, so would understand your hesitancy to advise so if that were the case.
Thanks for the reply. Most appreciated.
Hi @ripperman, you’re welcome and glad to see the tests were successful!
Generally it’d be good practice to switch back to Enabled and Protecting immediately, but if you were able to get any external users who’d experienced problems to try again, then leaving it in Learning Mode for this test period would be acceptable. Just don’t forget to switch it back again before too long.
Thanks again,
Peter.
Ok great. Thanks for the advice.
Marking as resolved.
