Paymentsense Direct spinning wheel “loading”

@paymentsense

Sending plugin users to write you per email and marking their topics as resolved is bad way to provide support for free plugins available from www.ads-software.com plugin repo.
You can and should to so for paid plugins and components, but for free plugins you can at least to provide some help on forums.

If your plugin provides some service on YOUR side, then clearly state it, when asking to email you, that you’re directing user off-forum because their problem is with the service, not the plugin itself.

You can ask any kind of debugging information or logs, but you can NOT ask for access to users site (admin login, ftp, whatever).

• This reply was modified 4 years, 5 months ago by Yui.

@fierevere

My apologies if I was not clear, the reason we require support requests to be sent in via email is that the first part of our diagnostic process involves checking the user’s account and its configuration.
In order to do this we need the account details which, understandably, we cannot ask for on a public forum. I hope this clears things up.

@cfprosecrets If you are still having issues could you please email our Developer Support team and we will be happy to help.

I have had the same issue reported to me by a client. I hope this can be resolved shortly.

Hi @gilesholder

The most common cause of this issue is Port 4430 not being open on the server the plugin is running on.

Could you please Email Devsupport ([email protected]) we will be happy to help.

We look forward to hearing from you.

Kind Regards

Paymentsense

I’m getting the same problem, spinning wheel on checkout for some of our customers (not all) but enough that customers are complaining that they can’t complete purchases. Opening Port 4430 didn’t seem to do anything for us. It’s useful having solutions here in the forum so that others can see what works (and what didn’t)

So i contacted the support team regarding this issue after opening Port 4430 did nothing and, apparently, the Direct option will only work with the following SSL cyphers enabled

LS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028) ECDH secp256r1
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (0xc027) ECDH secp256r1
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp256r1
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (0xc013) ECDH secp256r1
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)
TLS_RSA_WITH_AES_128_GCM_SHA256 (0x9c)
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d)
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)
TLS_RSA_WITH_AES_128_CBC_SHA256 (0x3c)
TLS_RSA_WITH_AES_128_CBC_SHA (0x2f)

which should surely be documented somewhere; the plugin states about the direct option “This has a higher level of PCI compliance and also requires an active SSL certificate.” but doesn’t specify any of the details. Our hosting has lots of other cyphers enabled, the alternative they say is to use the hosted option.

As mentioned previously the Direct option only works with the SSL cyphers above, however, all of these cyphers are WEAK thus leaving you more vulnerable to attacks – not something you want when you’re running an e-commerce website.

The problem has been resolved I binned the plugin and switched to stripe.

@cfprosecrets That was my solution too! No issues on Stripe. Just a shame Stripe cant do Card Machines as I would switch all my clients from PaymentSense.

Yep, i cannot recommend using this service based on what i’ve experienced. Going through all that, opening port 4430, changing the SSL cyphers, and the problem still persists and their support don’t know what to do about it