BAD_REQUEST: Invalid verification_token

  • Resolved Derek Wilcox

    (@themassapothecary)


    1 year, 6 months ago

    I just had a customer try to put an order through and first it went to failed status with a transaction limit error but then he tried to place the order several more times and each time it threw this error –

    BAD_REQUEST: Invalid verification_token

    I have debug on and have the log as well.

    [0] => Square\Models\Error Object
    (
    [category:Square\Models\Error:private] => INVALID_REQUEST_ERROR
    [code:Square\Models\Error:private] => BAD_REQUEST
    [detail:Square\Models\Error:private] => Invalid verification_token: verf:CBESEFqgotfcA-XxDCUWRNJlCHg
    [field:Square\Models\Error:private] => verification_token
    )

    )

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hi @themassapothecary

    Thanks for reaching out!

    I am sorry to hear that one of your customers is unable to complete the payment process due to the error message above.

    Based on the error message you provided, it seems like there might be an issue with the verification token used during the payment process. The BAD_REQUEST: Invalid verification_token error indicates that the token being used is either incorrect or expired.

    Please double-check your Square API settings under WooCommerce > Settings > Payments > Square, and ensure that the API keys and other settings are correctly configured. If you’re unsure, you can cross-check the API keys with the ones available in your Square Developer Dashboard (https://developer.squareup.com/apps).

    You can also try to replicate the same order they were trying to purchase via Square Sandbox Mode and see if you are able to reproduce the same error above?

    Please give it a try and let us know it goes!

    Hi,

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – we’ll be here if and/or when you are ready to continue.

    Best.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘BAD_REQUEST: Invalid verification_token’ is closed to new replies.