Callback error

  • Resolved webrightnow

    (@webrightnow)


    7 years, 6 months ago

    Hi there, the plugin seems to be working fine for taking customers to Worldpay but not redirecting back to the store after purchase. Also, customers are not receiving a confirmation email from the store. Client received this report in an email from Worldpay:

    Error reported: Callback to https://www.mysite.co.uk/wc-api/MDS_Worldpay_Gateway/: NOT OK, recevied HTTP status: 403

    I followed all instructions in your documentation regarding payment response setup. Also uploaded resultC.html and resultY.html as instructed. What else could be wrong? I read somewhere that it may be a conflict with Bulletproof Security. Can you confirm this? I’d rather not disable the security plugin unless necessary.

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author mdsilviu

    (@mdsilviu)

    If you are getting that error means your website endpoints are not available to public, meaning worldpay can’t access that url to post the transaction data. If you are on localhost or have an under construction plugin the transaction won’t be finalized. The website needs to be live to test it.
    As i can see when i access that url for the website it’s just a blank page.

    • This reply was modified 7 years, 6 months ago by mdsilviu.
    Thread Starter webrightnow

    (@webrightnow)

    Hi, the site is already live and taking payments from Paypal: gardiners-scotland.co.uk. The actual URL in the above error should be https://www.gardiners-scotland.co.uk/wc-api/MDS_Worldpay_Gateway/. I didn’t use the real URL before as I didn’t want to make it public. But the URL https://www.gardiners-scotland.co.uk/wc-api/MDS_Worldpay_Gateway/ doesn’t exist either, there is no wc-api folder at all in the root. Should there be one? When would this have been created? I didn’t generate that URL myself, so I’m guessing it’s generated by either your plugin or WorldPay. Sorry, I’m just a bit confused, can you clarify? Thanks

    Thread Starter webrightnow

    (@webrightnow)

    Just to confirm, the problem was indeed the Bulletproof Security plugin. Although I had disabled it, I forgot that it had overwritten the default .htaccess file. As soon as I reverted to the original .htaccess, payment response started working again. It may be worth mentioning in your plugin description “not compatible with Bulletproof Security”, many people use BPS and it would save them a major headache.

    Thanks

    It would not be an “incompatibility” thing. You would just need to create a whitelist rule for whatever is being blocked by BPS. These are the standard BPS troubleshooting steps: https://forum.ait-pro.com/forums/topic/read-me-first-free/#bps-free-general-troubleshooting

    Go to your BPS Security Log and post the Security Log entry that shows what is/was being blocked by BPS so that I can post the BPS whitelist rule that will allow/not block whatever is being blocked.

    I believe this is the documented working solution for this issue/problem: https://forum.ait-pro.com/forums/topic/woocommerce-worldpay-403-error/

    And on a personal note: These days everything should be completely automated and not require anyone to do any sort of troubleshooting of even get a solution from our forum. So we are currently building this automation into the BPS Setup Wizard, which will automatically detect the problem and display a message to run the BPS Setup Wizard to fix the problem/any/every known issue/problem. In other words, a simple one button click solution vs having to figure anything out, which is the way everything should be these days. ??

    Thread Starter webrightnow

    (@webrightnow)

    Ok thanks, I’ll keep this in mind for a future implementation. In this case the client said they are not fussed about BPS so I’ll just install Limit Login for now and keep things simple…

    Yep, completely understand. Sometimes less website security protection (with fingers crossed ha ha ha) is the simpler/better way to go. ??

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Callback error’ is closed to new replies.