Square Payment Module for Zen Cart [Support Thread]

[carlwhat]

It appears we have a combination of three things here. The item may have been in stock but is now out. The item may have been on special but there is no record now.

The current listing was generated by using edit orders and mentioning special. Not sure what versions of any of those things but will need to check further before pointing another finger.

Someone PLEASE check. Is today full-moon Friday the 13th?

TBC

you see, now you are sending us on wild goose chases. in looking briefly at the square module, v '1.5', api '3.20200528.1', it just takes the order total, converts the currency if necessary, and then authorizes...

if this did not work properly, i'm sure we would see a lot of other problems.

now, someone goes into edit_orders and makes some sort of adjustment. who knows what. we are now not comparing apples to oranges.

last time i checked, edit orders is pretty good about logging what it does in the order comments.

stock status? any item at that price point for the difference? again, square looks to take the order total and authorize for that amount. stock status seems like a red herring to me...

what this looks like to me, is a problem with procedures at the store, and not a problem with the square code, or the ZC code. edit orders, i acknowledge is a necessary evil for most stores; what it did to these orders should basically be there and be easy to reproduce.

but posting about square when the order has already been edited seems... i'm not sure for an appropriate term...

best.

[dbltoe]

Thank you for your kind remarks.

One can only use the information that one forces out of the client. Once I gained access, I can see that it may be several things which I will NOT bother you with here.

Since Square has done umpteen API changes since this site was setup, I broached the subject as best I could.

Your concerns are noted.

[DrByte]

Since Square has done umpteen API changes since this site was setup, I broached the subject as best I could.

Things like this have nothing to do with the Square API version.
In fact typically only major infrastructure changes have anything to do with the API version.
Usually as long as the Square API is same as the module's API, there's no point fixating on the API version (because using a newer API version will make it mismatch and thus is more likely to cause new problems rather than fix anything). Only exception is if Square has officially stopped responding to that API version ... in which case nothing will be working at all and it would be very obvious (eg: there wouldn't be small anomalies with a couple transactions).

[dbltoe]

And, from the customer

I updated the API and processed a payment. It was correct. I will wait and see what happens in the next Square payment.


Thanks

[Congerman]

I use Square payment module vs1.5. I have just had the below from square. Is there an update to the module coming soon?

We want to remind you that there are a few required steps you need to complete by 1st May 2021 to enable Strong Customer Authentication (SCA) for online payments, as required by the PSD2 (Payment Services Directive 2). If you do not take these steps, you risk facing bank declined payments after 1st May.

[johnjlarge]

I use Square payment module vs1.5. I have just had the below from square. Is there an update to the module coming soon?

We want to remind you that there are a few required steps you need to complete by 1st May 2021 to enable Strong Customer Authentication (SCA) for online payments, as required by the PSD2 (Payment Services Directive 2). If you do not take these steps, you risk facing bank declined payments after 1st May.

I've just received this email too. Would be good to clarify if SCA is already implemented in the square payment module.


We want to remind you that there are a few required steps you need to complete by 1st May 2021 to enable Strong Customer Authentication (SCA) for online payments, as required by the PSD2 (Payment Services Directive 2). If you do not take these steps, you risk facing bank declined payments after 1st May.

What do you need to do?
- Businesses and Partners that use Square’s developer products must update their applications to minimise the occurrence of declined payments. This includes those using the Square Payment Form and Connect V2 APIs. To achieve compliance, you are required to update your Square Payment Form integration following this guide.
- Businesses using Square Online, Square Online Checkout, and Square Invoices do not need to make any changes as the products have been updated to meet SCA requirements and invoke 3DS2 when necessary.

[WayneStephens]

Just adding my name to the list, I received the same email and would also like to know.

[ianhg]

I've just received this email too. Would be good to clarify if SCA is already implemented in the square payment module.


We want to remind you that there are a few required steps you need to complete by 1st May 2021 to enable Strong Customer Authentication (SCA) for online payments, as required by the PSD2 (Payment Services Directive 2). If you do not take these steps, you risk facing bank declined payments after 1st May.

What do you need to do?
- Businesses and Partners that use Square’s developer products must update their applications to minimise the occurrence of declined payments. This includes those using the Square Payment Form and Connect V2 APIs. To achieve compliance, you are required to update your Square Payment Form integration following this guide.
- Businesses using Square Online, Square Online Checkout, and Square Invoices do not need to make any changes as the products have been updated to meet SCA requirements and invoke 3DS2 when necessary.

Same had this email is the current plugin OK to use?