Square WebPay support thread.

[Nick1973]

Hi Carl,

Thanks for the video showing the two scenarios, testing out my concerns.

I went through the exact same two scenarios as yourself earlier today, without touching the Square radio button first, and I get SQ-MISSING-TOKEN each time. (I even used the same card data).

If I then immediately entered the card details again without touching anything else, (the Square radio button is already highlighted at this stage)
when I selected Confirm Order I would get the please wait symbol then GENERIC DECLINE, so potentially all good!

The only way I could make sure the system produced a potential successful procedure and show GENERIC DECLINE was to make sure I had selected the Square radio button before entering the card details, and then this was successful repeatedly.

I then decided to try different browsers (Edge and Chrome) as I mainly use Firefox, but the same results persisted.

I am slightly perplexed now and thinking the only thing different between your testing and mine is the location.

Somehow I will have to force (tell my customers nicely) to make sure they select the Square Payments radio button before entering their card details ( There will be customers that read instructions and customers that don't, and they are the ones that will get an SQ-MISSING-TOKEN).

The ideal situation would be that the radio button gets selected in unison with selecting the data entry fields but I understand you have already mentioned the complexities of trying to do this.

This rather testing problem aside, Webpay is awesome.

Vic

The minute I turned OPC OFF, an order came through. It kind of confirms it. Since installing both of these modules around mid June, I have had hardly any orders :-(

[Valencia]

The minute I turned OPC OFF, an order came through. It kind of confirms it. Since installing both of these modules around mid June, I have had hardly any orders :-(

Hi Nick,

I find as long as the Square radio button is checked before entering card details the whole thing works, no errors. The moment a customer just goes straight for the card input fields first without pre-selecting the radio button the SQ-MISSING-TOKEN message pops up which can scare the customer.
I have had customers that understand when I reply to their emails and they go for the Paypal option I suggest, and I have had customers that just drop their cart and I never hear from again.
If there was some way of automatically selecting the Square option when the card input fields where picked it would stop the customer making errors.

And yes Carl What is just amazing to have brought this module to where it is considering the time pressure of the old Square Modules retirement.

Hope something gets sorted going forward as Square is just the business, i have their hardware in my physical store as well!

Vic

[Nick1973]

Hi Nick,

I find as long as the Square radio button is checked before entering card details the whole thing works, no errors. The moment a customer just goes straight for the card input fields first without pre-selecting the radio button the SQ-MISSING-TOKEN message pops up which can scare the customer.
I have had customers that understand when I reply to their emails and they go for the Paypal option I suggest, and I have had customers that just drop their cart and I never hear from again.
If there was some way of automatically selecting the Square option when the card input fields where picked it would stop the customer making errors.

And yes Carl What is just amazing to have brought this module to where it is considering the time pressure of the old Square Modules retirement.

Hope something gets sorted going forward as Square is just the business, i have their hardware in my physical store as well!

Vic

It seems to be a problem between the module and OPC though as the minute you turn OPC off the problem disappears on the standard checkout. Like you, I prefer square as a solution for card payments these days. It is so easy to use.

[Valencia]

It seems to be a problem between the module and OPC though as the minute you turn OPC off the problem disappears on the standard checkout. Like you, I prefer square as a solution for card payments these days. It is so easy to use.

Yup, just tried turning off OPC and hey presto everything goes through smoothly, I don't even need to select Square, I just input the card data right away and hey presto no more SQ-MISSING-TOKEN.

I really like OPC and Square.

[carlwhat]

The moment a customer just goes straight for the card input fields first without pre-selecting the radio button the SQ-MISSING-TOKEN message pops up which can scare the customer....

vic,
again, without bring able to reproduce the problem, it is hard for me to fix it...

i do not agree that the pre-selection of the radio problem addresses the problem, but i have been wrong before.

if you think the message scares the customer, that one is an easy fix....

go to:

includes/languages/english/modules/payment/square_webPay.php

and change:

// from:

define('MODULE_PAYMENT_SQ_WEBPAY_TEXT_MISCONFIGURATION', 'We have a problem on our end.  So Sorry! Please report this error to the Store Owner: SQ-MISSING-TOKEN');

// to:
define('MODULE_PAYMENT_SQ_WEBPAY_TEXT_MISCONFIGURATION', 'Hi, please remember to select square PRIOR to entering your credit card data.  Thanks again!'); 

feel free to change the text to whatever you think is appropriate.

best.

[Valencia]

vic,
again, without bring able to reproduce the problem, it is hard for me to fix it...

i do not agree that the pre-selection of the radio problem addresses the problem, but i have been wrong before.

if you think the message scares the customer, that one is an easy fix....

go to:

includes/languages/english/modules/payment/square_webPay.php

and change:

// from:

define('MODULE_PAYMENT_SQ_WEBPAY_TEXT_MISCONFIGURATION', 'We have a problem on our end.  So Sorry! Please report this error to the Store Owner: SQ-MISSING-TOKEN');

// to:
define('MODULE_PAYMENT_SQ_WEBPAY_TEXT_MISCONFIGURATION', 'Hi, please remember to select square PRIOR to entering your credit card data.  Thanks again!'); 

feel free to change the text to whatever you think is appropriate.

best.

Thank,s Carl

That will help restore confidence. I shall be modifying it tomorrow.

By the way I have just found out that turning off the OPC module allows Webpay to work without having to select the radio button first.
Just tried it now on my test cart, and everything works perfectly. And my test cart is just a duplicate of my live site in a different directory.

Vic

[Nick1973]

vic,
again, without bring able to reproduce the problem, it is hard for me to fix it...

i do not agree that the pre-selection of the radio problem addresses the problem, but i have been wrong before.

if you think the message scares the customer, that one is an easy fix....

go to:

includes/languages/english/modules/payment/square_webPay.php

and change:

// from:

define('MODULE_PAYMENT_SQ_WEBPAY_TEXT_MISCONFIGURATION', 'We have a problem on our end.  So Sorry! Please report this error to the Store Owner: SQ-MISSING-TOKEN');

// to:
define('MODULE_PAYMENT_SQ_WEBPAY_TEXT_MISCONFIGURATION', 'Hi, please remember to select square PRIOR to entering your credit card data.  Thanks again!'); 

feel free to change the text to whatever you think is appropriate.

best.

It isn't so much the pre-selection, as it does actually pre-select the minute you start typing in the credit card number.

If the customer clicks the radio button, and then enters their card details, the payment is taken absolutely fine.

If they start typing their card details and DON'T select the radio button, and the radio button pre-selects automatically, and then they try to 'confirm order' after they have entered their credit/debit card details, it is then that the error occurs.

Trust me, I have lost orders through this, and I know I have, so I know that it is the issue.

It's easy to replicate if you try it.

I don't think changing the text will make any difference in all honesty. Customers don't always read what is in front of them, and just expect it to work. We are talking people not so computer literate as ourselves here. There is a difference.

It works on the standard checkout, so really it should be the same on OPC.

[carlwhat]

...
Trust me, I have lost orders through this, and I know I have, so I know that it is the issue.

It's easy to replicate if you try it.

nick,
try and play along. i have tried it. numerous times. on your site and on vic's site. did you read the above post:

https://tinyurl.com/2probynf

did you watch the video, i posted:

https://www.dropbox.com/s/i3zc3t5diu...20PM.webm?dl=0

i have a suggestion for you. why don't you do a screencast similar to what i did, showing the exact sequence where an order goes through using your keystrokes. and then one where it does not.

trust me, there is nothing more that i want to do than to solve this problem. but unless i can replicate it, i can not solve it.

finally with regards to this comment:

It works on the standard checkout, so really it should be the same on OPC.

the only thing i can say is you really have no idea what is going on in OPC and the amount of javascript code that plugin does.

[Nick1973]

nick,
try and play along. i have tried it. numerous times. on your site and on vic's site. did you read the above post:

https://tinyurl.com/2probynf

did you watch the video, i posted:

https://www.dropbox.com/s/i3zc3t5diu...20PM.webm?dl=0

i have a suggestion for you. why don't you do a screencast similar to what i did, showing the exact sequence where an order goes through using your keystrokes. and then one where it does not.

trust me, there is nothing more that i want to do than to solve this problem. but unless i can replicate it, i can not solve it.

finally with regards to this comment:

It works on the standard checkout, so really it should be the same on OPC.

the only thing i can say is you really have no idea what is going on in OPC and the amount of javascript code that plugin does.

carlwhat, I am playing along and this is why I am also reporting the issue :-)

Ok Screencast - will do one then so you can see the issue. I guess from our points of view we could be reading things differently from one another after all so not an issue.

'the only thing i can say is you really have no idea what is going on in OPC and the amount of javascript code that plugin does' - I do know the amount of Javascript that is used by OPC, so I am fully aware it will be a minefield to work with.

Like I said before carlwhat, I am extremely grateful for your hard work on this, and I think Vic is from what I read as well. There are probably others that think the same.

[Nick1973]

nick,
try and play along. i have tried it. numerous times. on your site and on vic's site. did you read the above post:

https://tinyurl.com/2probynf

did you watch the video, i posted:

https://www.dropbox.com/s/i3zc3t5diu...20PM.webm?dl=0

i have a suggestion for you. why don't you do a screencast similar to what i did, showing the exact sequence where an order goes through using your keystrokes. and then one where it does not.

trust me, there is nothing more that i want to do than to solve this problem. but unless i can replicate it, i can not solve it.

finally with regards to this comment:

It works on the standard checkout, so really it should be the same on OPC.

the only thing i can say is you really have no idea what is going on in OPC and the amount of javascript code that plugin does.

Ok I have had a look at your screencast videos.

Firstly, I understand why the Paypal method would fail, so that is fine because the customer has selected the wrong payment method and then tried to enter details into the square fields. You would expect that to fail!

That is this video:
https://www.dropbox.com/s/6mc9y5gvf3...20PM.webm?dl=0

-----------------------------------------------

Now, this video actually highlights the problem:
https://www.dropbox.com/s/i3zc3t5diu...20PM.webm?dl=0

So, a suggestion. To stop this from happening, are you able to force the customer to select the radio button before they can enter their details?

You could disable the SQUARE text entry fields, or even hide them until customers click on the SQUARE radio button. And if customers click the Paypal radio button, the text fields on the square element either remain disabled or hidden from view.

At the side of the SQUARE radio button in BOLD text, or even BOLD RED TEXT, you could have some text saying 'If you wish to pay by credit or debit card, please select this payment method. NOTE: You will be able to enter your payment details once this radio button is checked' - then once the radio button is clicked, the text fields either get enabled OR if hidden, they appear on screen.

At the side of the PAYPAL radio button you could have some text saying 'If you wish to pay by PAYPAL, please select this payment method' - then the SQUARE text fields either remain disabled or hidden from view and the customer can pay by paypal without a problem.

And if the customer happens to try and click confirm order, before they have selected either, it throws up a message something like 'You forgot to select a payment method, please try again'.

This is just an idea by the way! I am trying to help with a suggestion!