3D secure transactions not completing

Can you confirm that cURL is enabled on your server?

Just checking in on this as I have not heard from you. If I don’t hear back soon I’m going to go ahead and close this ticket.

Apologies for the delay, I’ve been waiting on a response from the host as it’s not my usual development environment.

They have now confirmed that cURL is enabled.

Thanks,

Rob

@aproimage, I can help you get this resolved, but it’s going to require some time digging around in log files and troubleshooting the issue with Cardinal Commerce. That sort of thing is beyond the scope of our general install and config free support, so that will require a premium support ticket.

Thanks, would it be better to wait until we have the site installed on the server it will ultimately be running on, then everything can be set up and tested in the correct environment, As soon as the client has added content to the site it should be possible to revisit this.

Probably a good idea, yes.

Hi, we are nearly there with the production site so should be looking to visit premium support soon.

In the meantime, I’ve come across a new problem on the production server.

When I am on the options page for “PayPal Website Payments Pro (DoDirectPayment)” a lot of code is printed out at the bottom of the screen followed by the credit card details form itself, and the credit card form does not display at checkout.

The code that’s printed out looks like the it is probably the plugin code itself rather than an error message and is as follows

enabled==”yes”) : if ( $this->testmode == “no” && get_option(‘woocommerce_force_ssl_checkout’)==’no’ && !class_exists( ‘WordPressHTTPS’ ) ) return false; // Currency check if ( ! in_array( get_woocommerce_currency(), apply_filters( ‘woocommerce_paypal_pro_allowed_currencies’, array( ‘AUD’, ‘CAD’, ‘CZK’, ‘DKK’, ‘EUR’, ‘HUF’, ‘JPY’, ‘NOK’, ‘NZD’, ‘PLN’, ‘GBP’, ‘SGD’, ‘SEK’, ‘CHF’, ‘USD’ ) ) ) ) return false; // Required fields check if (!$this->api_username || !$this->api_password || !$this->api_signature) return false; return isset($this->avaiable_card_types[WC()->countries->get_base_country()]); endif; return false; } /** * Payment form on checkout page */ function payment_fields() { $available_cards = $this->avaiable_card_types[WC()->countries->get_base_country()]; ?>

Do I need to configure something specific on my server? I have asked to check whether cURL is currently enabled and am awaiting a response.

Many thanks

I think I’ve seen this happen because of either a PHP version issue or a short tags issue. Can you check what version of PHP you’re running and whether or not you have short tags enabled?

I’m pretty sure it’s the short tag issue. I’m going to remove all opening short tags in a future release. In the mean-time, if you can’t enable short tags on your server let me know and I’ll show you where to fix it in the plugin for now.

Thanks, that makes sense, I’ve now asked for short tags to be enabled, and in the meantime I’ve adjusted the shortened tag that appeared to be causing the problem, all seems to be doing what it should now.

Glad to hear it. Let me know if anything else comes up.

Hi

I had the same problem on my site.

Was getting the number one symbol on this page https://www.mydomain.com/?wc-api=WC_Gateway_PayPal_Pro

I disabled cURLSSL and enabled cURL instead.

Now I don’t even get the 3d verification page. I just get a 8030 error as soon as I press check out.

Can you help?

Thank you

BTW I also have short_open_tag as on globally on my server.

Running PHP 5.4 and the latest version of Paypal for woocommerce Version 1.1.5

Woocommerce Version 2.2.8

WordPress 4.0

Hope this helps. Have had a few fraud purchases attempts (some successful) would be great to get this implemented.

Sorry for the spam. Had to re-enable the cURLssl because it broke your plugin.

So I now have cURL disabled and cURLssl enabled.

Hi cveronese,

I’ve actually always used cURL without any issues. I’ve never messed with cURLssl. Is that actually different, or is it just cURL with some specific options set?

The code that handles the 3DSecure stuff is still left over from the original Woo plugin that we started with to turn this into what it is today. We haven’t touched any of the 3DSecure stuff, and unfortunately, it seems to have some pretty lousy error handling included within it, which is why we just get the blank screen with a 1 instead of actual errors.

If you want to submit a ticket here and provide me with WP admin credentials as well as FTP credentials I can jump in there and spit out an actual error log from Cardinal Commerce’s server so we can see what the error is.

Also, please provide details about when it would be ok for me to change the site to sandbox mode for testing purposes. If you have a test server that mirrors your live site that would be even better.