- portraitkanrishaAsked on February 17, 2018 at 03:49 AM
I would like to know if the Postal Code requirement could be disactivated on the Square Payment Widget. This field is indeed only necessary for businesses running in the US, Canada and the UK. (https://docs.connect.squareup.com/payments/sqpaymentform/sqpaymentform-setup) (see below step 7)
As always, thank you very much in advance for your help !
- JotForm SupportJim_RAnswered on February 17, 2018 at 06:48 AM
We can put this up as a feature request but we'd like to know your thoughts first on why you need to the POSTAL CODE to be removed from the SQUARE payment field.
I understand that this is optional and is only required for merchants based in the United States, Canada, and United Kingdom. Seeing that your forms are in Japanese and your last login geolocation was in Japan, I can only assume that your customer and user base would be in Japan alone, is that correct?
Kindly get back to us with more info so we can relay them to our developers for review.
- portraitkanrishaAnswered on February 17, 2018 at 07:02 AM
As you mentioned, this would be used for a Japanese company operating in Japan. Besides, this form will be used to sell products only to people living on the territory.
The reason why I would like to have this field removed is that you are usually never asked this kind of information over here when making a payment, which could actually confuse the customer.
In my case, they are already required to enter their postcode earlier in the form so asking it a second time makes it redundant on top of that.
I assume just removing the field would be simpler rather than making a function that allows to channel a previously entered postcode field into the square payment one..
Thank you very much for your quick feedback !!
- JotForm SupportJim_RAnswered on February 17, 2018 at 07:40 AM
Thanks for the detailed reply. I elevated your thread as a feature request. Please keep in mind that there's no assurance whether this will be implemented. It will highly depend on the viability of the feature, the amount of similar requests we get, along with the workload of our Developers.
We can't give you any timeframe but we'll keep you apprised on this same thread when there's an update.