Square Payment Module for Zen Cart [Support Thread]

Log Mode:
Log on Failures and Email on Failures

Shouldn't I receive an email when checkouts fail?
Shouldn't the email be visible in Email Archive? Similar to ALERT: when admin changes are made?

Have just reopened my shop after 9 weeks. updated square and have seen my first payment so all good. While testing the site I thought it would be nice to hide the credit card details until that method was selected. Made some javascript that does the job but cannot find where the credit card radio button is located so that I can add an onclick/change to the button to display the fields. Any pointers as to where I would add the onclick/change?

Thanks in anticipation.

brittainmark:

Have just reopened my shop after 9 weeks. updated square and have seen my first payment so all good. While testing the site I thought it would be nice to hide the credit card details until that method was selected. Made some javascript that does the job but cannot find where the credit card radio button is located so that I can add an onclick/change to the button to display the fields. Any pointers as to where I would add the onclick/change?

Thanks in anticipation.

i would look here:

https://github.com/zencart/zencart/blob/22424cedd39d8b4b8496438507f8a897881e0644/includes/templates/template_default/templates/tpl_checkout_payment_default.php#L125-L140

includes/templates/template_default/templates/tpl_checkout_payment_default.php

i think that is what you are asking. and i'll assume you know about the whole template override thing.

best.

Thanks. That was exactly what I was looking for. And yes I do know about the template override thing. But good to check. All done.

Zen Cart 1.5.6c
PHP Version: 7.3.18
Database Engine: MySQL 5.5.5-10.3.23-MariaDB
Square Payments 1.1

I have been getting a number of square payment failure messages with the code "GENERIC_DECLINE". I am getting some payments through as well. Was wondering If this is an intermittent site issue or User error.

Any Advice welcome

GENERIC_DECLINE is the square equivalent of "oops!"

"An unexpected error occurred" is certainly not a lot of help.

First, make sure your API is dated 04-22-2020.

Then, if the module's Log Mode is not set to notify you of errors, select at least log on failures.

Next, try dropping the PHP back a notch just to make sure your 7.3 is not just outside the current range of 1.5.6c

Just in case, check server logs for the times these failures occurred. With everyone using the internet at home, you may have some dropped connections.

Keep in mind, that some of these transactions might be someone just testing to see if a hacked card will work.

Thanks for that.
I have seen cvv failures which could be people testing cards.
The last lot were the same person at 03:00 so I would not expect internet to be busy. Prior to that it took someone 2 attempts but the order was successful on the second attempt.
I have logging on as suggested and I am using the latest version of Square api.

As for Php are you suggesting I go down to 7.2?
I have not had any php errors using zen cart. I did have to change a few arrays to make sure they were defined for counts so not even getting warnings.
Happy to try 7.2.

Is there any logging i can turn on with Square outside of zen cart?

Thanks again

Someone else might have other suggestions but, that's all I've got in my bag of tricks.

Being such a vague error, it may be best to just move on. We've only had one GENERIC_DECLINE reported by our square-using customers.

Thanks Anyway. I'll keep an eye.

dbltoe:

... First, make sure your API is dated 04-22-2020...

As v1.1 says 'Integrated using SquareConnect PHP SDK 3.20200325.0' is it safe/advisable to always be using the latest API?

Generally best to use the API version that the module was built for. That said, the module transmits its API version with its transaction requests, so it should auto-negotiate with Square for the right one to use on each communication attempt.

None of our clients with square have had problems with the current api. Several have had problems that were cured by updating.

Would be interested to hear other experiences along these lines.
We have been using the Square module (still using 0.97) since January 2020, and it is indeed very convenient because of its seamless integration into the checkout page, unlike, say, Paypal.

There is a major shortcoming though: At least in Japan there is the following restriction, notice of which we received from their support staff after several INVALID_CARD transaction failures.

Online use via the E-Commerce API only permits transactions for 3 credit card types: VISA, MasterCard, American Express.

The following additional 3 card types can only be used physically, via the Square Reader (card reader): JCB, Diner's Club, Discover Card.

So the use of the module is sadly quite limited for online transactions. I am still waiting for confirmation as to whether this is a regional restriction for Japan, or a world-wide Square restriction. It is confusing since in one's Square account one needs to make a special application for JCB use approval, which we made and received the OK for, but there is no mention that one cannot actually use JCB and related cards with the E-Commerce API.

gernot:

Would be interested to hear other experiences along these lines.
We have been using the Square module (still using 0.97) since January 2020, and it is indeed very convenient because of its seamless integration into the checkout page, unlike, say, Paypal.

There is a major shortcoming though: At least in Japan there is the following restriction, notice of which we received from their support staff after several INVALID_CARD transaction failures.

Online use via the E-Commerce API only permits transactions for 3 credit card types: VISA, MasterCard, American Express.

The following additional 3 card types can only be used physically, via the Square Reader (card reader): JCB, Diner's Club, Discover Card.

So the use of the module is sadly quite limited for online transactions. I am still waiting for confirmation as to whether this is a regional restriction for Japan, or a world-wide Square restriction. It is confusing since in one's Square account one needs to make a special application for JCB use approval, which we made and received the OK for, but there is no mention that one cannot actually use JCB and related cards with the E-Commerce API.

What are your settings for configuration->credit cards?

Hi mc123455678
I have the following:

Credit Card Enable Status - VISA 1
Credit Card Enable Status - MasterCard 1 Info
Credit Card Enable Status - AmericanExpress 1 Info
Credit Card Enable Status - Diners Club 1 Info
Credit Card Enable Status - Discover Card 1 Info
Credit Card Enable Status - JCB 1 Info
Credit Card Enable Status - AUSTRALIAN BANKCARD 0 Info
Credit Card Enable Status - SOLO 0 Info
Credit Card Enable Status - Debit 0 Info
Credit Card Enable Status - Maestro 0 Info
Credit Card Enabled - Show on Payment 2 Info

Square confirmed that this restriction in the E-Commerce API is for Japan, specifically when creating a Square account in Japan. And that it might be elsewhere too.
Therefore the only cards capable of being used with the web input method (typing in the card information) are VISA, MasterCard, and American Express.

They say that use of JCB, Diner's Club, and Discover Card can be accomplished using the invoice method, which I understand is quite a bit more expensive to use.
English:

1. https://squareup.com/help/us/en/article/5137-send-square-invoices-online
   Fee seems to be 2.9% + 30c
   for Card on File 3.5% + 15c
2. https://squareup.com/help/us/en/article/5138-pay-invoices-with-square

Japanese (different conditions):

1. https://squareup.com/help/jp/ja/article/5137-send-square-invoices-online
   Fee seems to be 3.25% (JCB 3.95%)
   for Card on File 3.75% (JCB 3.95% [same as standard fee])
2. https://squareup.com/help/jp/ja/article/5138-pay-invoices-with-square
   Has a note at the top stating that support for JCB, Diner's Club, Discover Card depends on the shop (presumably whether the application has been approved).

So Square clearly operates differently in different regions/countries.

mc12345678:

What are your settings for configuration->credit cards?

This made me wonder. Having only ever used Square and PayPal EC to process credit cards, I've never looked at that configuration page - even after all these years.

Delving into the code I believe that only Authorize.net & PayPal Website Payments Pro use the checks set on that page and that they have no bearing on how Square processes payments.

simon1066:

This made me wonder. Having only ever used Square and PayPal EC to process credit cards, I've never looked at that configuration page - even after all these years.

Delving into the code I believe that only Authorize.net & PayPal Website Payments Pro use the checks set on that page and that they have no bearing on how Square processes payments.
The cc_validation logic that uses those settings is not used by the Square module because Square does all the card-validation itself, offsite, not in ZC.

gernot:

So Square clearly operates differently in different regions/countries.Yes: this is based on regulatory approvals that are granted by local banking rules.
Every card-processing service needs to get approvals, which takes time.

**Version 0.97 - with the newest Square API versions paired - is working well on 1.55f *AND ***1.56c PHP 7.x for anyone waiting for the kinks to get out of the newer Square 1.x versions.

Obviously there will be features missing and problems in the future so... support us and we'll support you :)

twitchtoo:

... waiting for the kinks to get out of the newer Square 1.x versions.

Other than trying to use an old API, none of our customers have had any kinks. Care to elaborate as to the kinks you are finding?