Square’s Postcode Requirement for Payments SDK in WooCommerce Checkout

Ive used square for years for both POS and the checkout payment option on woocommerce and recently out of the blue the postcode verification suddenly activated on our website and caused a loss of hundreds of dollars a day! I immediately emailed square and they passed the responsibility back to woo, woo looked into it and finally came back confirming it was to do with squares requirements. I passed this all back onto square whilst receiving 5+ phone-calls a day from customers advising they couldn't checkout due to this sudden payment requirement (imagine how many didnt bother calling). These orders wouldn't show up in failed orders either so there was no way to track how much money I've actually lost from this. After days of square not responding to the multiple emails i removed it as a payment option and am now considering shifting away from square all together as its left a really bad experience in my mind about the lack of accountability and support.

286 Views
Message 1 of 2
Report
1 Solution
Square Community Moderator

Solution

Hi @Bloomsssss25!

I'm really sorry to hear how frustrating this has been - this definitely isn’t the experience we aim to provide. I’ve shared your feedback directly with the relevant team leads so it can be taken into account.

This issue has come up from other Sellers before, and I agree it’s a tricky one. It falls outside the scope of what Square Support can assist with, as it relates to our Payments SDK and Developer tools. These types of questions are best handled by the Square Developer team, as Support doesn't have access to the tools or expertise needed for SDK and API-related queries.

From what I’ve seen on the Square Developer Forums, the Web Payments SDK typically requires a postcode to proceed with payment, and whether it’s mandatory can depend on the card type being used and the issuing country. That said, I’d still recommend reaching out to Square Developer Support directly to get a definitive answer for your setup. You can submit your question here.

If you don’t hear back in the next few days, feel free to give me a shout - I’ll do my best to help move things along for you.

Laurie
Community Moderator, Australia, Square
Sign in and click Mark as Best Answer if my reply answers your question.

View Solution >

248 Views
Message 2 of 2
Report
1 REPLY 1
Square Community Moderator

Solution

Hi @Bloomsssss25!

I'm really sorry to hear how frustrating this has been - this definitely isn’t the experience we aim to provide. I’ve shared your feedback directly with the relevant team leads so it can be taken into account.

This issue has come up from other Sellers before, and I agree it’s a tricky one. It falls outside the scope of what Square Support can assist with, as it relates to our Payments SDK and Developer tools. These types of questions are best handled by the Square Developer team, as Support doesn't have access to the tools or expertise needed for SDK and API-related queries.

From what I’ve seen on the Square Developer Forums, the Web Payments SDK typically requires a postcode to proceed with payment, and whether it’s mandatory can depend on the card type being used and the issuing country. That said, I’d still recommend reaching out to Square Developer Support directly to get a definitive answer for your setup. You can submit your question here.

If you don’t hear back in the next few days, feel free to give me a shout - I’ll do my best to help move things along for you.

Laurie
Community Moderator, Australia, Square
Sign in and click Mark as Best Answer if my reply answers your question.
249 Views
Message 2 of 2
Report