Square verification failure on Mastercard

Hi @djellsworth,

Thank you for reaching out and providing detailed information about the issue you’re experiencing. The error you’re seeing is coming from Square’s API, which suggests that the issue might be related to the specific card or the card’s issuing bank. However, to rule out any issues on our end, let’s try a few troubleshooting steps:

1. Enable Logging: Go to WooCommerce > Settings > Payments > Square > Manage, and enable ‘Debug Log.’ Try processing the card again and check the log entries in WooCommerce > Status > Logs. This might give us more information about the error.
2. Check API Keys: Ensure that your Square API keys are correctly entered and up-to-date. You can find this under WooCommerce > Settings > Payments > Square.
3. Test in Sandbox Mode: Switch to Sandbox mode in the Square settings and try a test transaction. Does the error still occur?

Please share the results of these steps, and remember not to share any sensitive information from the logs publicly.

Looking forward to your response.

-Logging enabled. Please see attached.

-Check API keys. I do not see these API keys listed anywhere on the screen (see screenshot attached. I can go to my square developer dashboard and the production environment shows I am using the Square API version 2020-04-22 (49 versions behind). I don’t know if that is related to this plugin or another project I started in the past. I don’t recall ever selecting anything here when using the square plugin.

-Doesn’t work in Sandbox either (the same card number).

Looking forward to your response. We have a couple customers now having the same problem, but other credit cart orders still come through just fine.

Thanks.

Square log: https://drive.google.com/file/d/16KryoThDwkclXCnUpxtR7As6ejp39B-U/view?usp=drive_link

System report: https://drive.google.com/file/d/1l-hN1a-po9gW1i7K9vu40uJWu3Ghj6Pp/view?usp=drive_link

Square settings (no API keys viewed): https://drive.google.com/file/d/1PXf_aaPINjI4ZWeUv45COqdDCsQGv0I_/view?usp=drive_link

Hey, @djellsworth!

I tried checking the information you shared, but it is private. Please note we are not allowed to review it if it is private.

Can you please share it somewhere we can check it? You can share it on https://github.com/, https://quickforget.com/, or somewhere similar ??

Also, you mentioned only some users are facing this issue. Do you know if they are using the same type of credit card (visa, american express, master, etc)?

On the first message you mentioned a government card, are all customers who are having this issue using this type of card?

Looking forward to your reply.

Have a wonderful day!

I have enable the links to be viewable, always forget that part lol.
Currently it is just one card that throws the 400 error on the Post “https://connect.squareup.com/v2/analytics/verifications”
We get emails from customers that the processing spinner just spins (nothing happens) but later the order goes through. This particular one causes this error every time. It will not process.

This is the message in the browser console:

XHRPOST
https://connect.squareup.com/v2/analytics/verifications
[HTTP/2 400 99ms]

POST
https://connect.squareup.com/v2/analytics/verifications
Status
400
VersionHTTP/2
Transferred1.22 kB (224 B size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem

access-control-allow-credentials
    true
access-control-allow-headers
    Origin, Content-Type, Authorization, X-Requested-With, _connect_js_csrf, X-JS-ID, X-CSRF-Token, Square-Version, X-Allow-Cookies, X-Block-Cookies
access-control-allow-methods
    GET, POST, PUT, DELETE, OPTIONS
access-control-allow-origin
    https://connect.squareup.com
cf-cache-status
    DYNAMIC
cf-ray
    867fd039d91ea6f7-PHX
content-encoding
    gzip
content-length
    178
content-type
    application/json
date
    Thu, 21 Mar 2024 17:55:31 GMT
server
    cloudflare
strict-transport-security
    max-age=631152000; includeSubDomains; preload
vary
    Origin, Accept-Encoding
x-block-upstream-cluster
    payapi-analytics--production
x-content-type-options
    nosniff
x-download-options
    noopen
x-envoy-decorator-operation
    /v2/analytics/verifications
X-Firefox-Spdy
    h2
x-frame-options
    SAMEORIGIN
x-permitted-cross-domain-policies
    none
x-speleo-traceid
    CDN-40fec778-eb4b-45e3-b216-a2f03055b598
x-sq-dc
    aws
x-sq-region
    us-west-2
x-xss-protection
    1; mode=block

Accept
    */*
Accept-Encoding
    gzip, deflate, br
Accept-Language
    en-US,en;q=0.5
Connection
    keep-alive
Content-Length
    6472
Content-Type
    application/json
Cookie
    _savt=ba3867f8-3607-4f70-8723-db0c8870c2ea; __cf_bm=iciB8PlXFodoTuNuGqAOWBsp3bKJ7fAEs3fegwaXl.0-1711043714-1.0.1.1-xwj2xsmvPvH8f4AooeyN0JAnsNa4GomC_bXzTW6dLx40haHEP2OxrP4WOlBwTjmMUwOEFWLBgb9H5rGECtL0NA
DNT
    1
Host
    connect.squareup.com
Origin
    https://connect.squareup.com
Referer
    https://connect.squareup.com/payments/data/frame.html?referer=https%3A%2F%2Fwww.speechcorner.com%2Fsc-checkout-page%2Forder-pay%2F36629%2F%3Fpay_for_order%3Dtrue%26key%3Dwc_order_reS2PFp8IscmS
Sec-Fetch-Dest
    empty
Sec-Fetch-Mode
    cors
Sec-Fetch-Site
    same-origin
TE
    trailers
User-Agent
    Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:124.0) Gecko/20100101 Firefox/124.0

This is odd, @djellsworth.

In order to investigate further, please contact us at Woo.com > My Account > Support. You may need to create an account before you can access that page.

Please include a link to this forum thread, so that we can keep track of what’s already been done.

We will be able to help you further there.

We’re experiencing the same issue and all our developers and Square is scratching their heads. Square has told us that there is no issue from Square and we need to follow up with the plugin developer. Exact same logs and exact same versions. tried with 8.6.1 and 4.5.1 and 8.7.0

Hi @dgogia,

Thank you for contacting WooCommerce support. I understand you are facing the same issue. Since all websites are built differently and run in different environments. Therefore, as per our Support Policy, I will suggest you create a new topic so we can assist you separately.

I appreciate your understanding. ??

Hi @djellsworth, since we’re already in touch with you via a ticket, I’ll go ahead and close this thread for now.