Level3 Data

  • Resolved Salty Pete

    (@peterwills)


    4 years, 9 months ago

    I was getting the exact same Level3 data error as @tonyd256 and @zalexzperez, namely that the plugin was sending “Level 3” data to Stripe for each transaction, triggering 400 Errors, followed immediately by a second transaction when the plugin succeeded with no Level3 data.
    https://www.ads-software.com/support/topic/received-unknown-parameter-level3/

    Following recommendations, I contacted Stripe support and asked them to activate a secret gated feature on my account. After a while they relented and admitted that Level 3 existed and they’d look in to turning it on. Now I’ve got level3 working. Yay. I now get more level3 errors because of a handling fee I add at checkout looking weird according to the level3 spec. I reverted to 4.3.1 of the plugin which looks like the last one before Level3 was added, and all is well for now, except I’m using an out-of-date plugin
    https://github.com/woocommerce/woocommerce-gateway-stripe/releases/tag/4.3.1

    Questions:
    1) Does this mean that by default, out of the box, this plugin spams errors unless you succeed in convincing Stripe to activate a secret feature? Or is there likely something unusual about my setup?
    2) Wouldn’t it be better to make this an option?

    Many thanks. I consider WooCommerce to be generally pretty amazing.
    — Peter

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    Hey there!

    This Github thread goes into some significant details on the technical implementation and also touches on why we’re doing this https://github.com/woocommerce/woocommerce-gateway-stripe/pull/1130

    1) Does this mean that by default, out of the box, this plugin spams errors unless you succeed in convincing Stripe to activate a secret feature? Or is there likely something unusual about my setup?

    No. From our discussions with Stripe, this feature (using level 3 data) should be a part of the vast majority of US based Stripe accounts. Our implementation of this sends once with Level 3, then should not send level 3 again if it fails (because it knows it can’t accept it). In your case because of the mismatch in totals because of the fee, you will see more errors than we would expect for sure. So all that to say, no you should not have to have Stripe enable stuff to have level 3 work.

    2) Wouldn’t it be better to make this an option?

    No, level 3 data is industry standard at this point, and it is something that a lot of merchants use (and card processing networks). There should not be a reason to have logging on in production, so the vast majority of people will never notice even if they were getting errors.

    Hopefully that helps! Have a great one!

    Thread Starter Salty Pete

    (@peterwills)

    Thanks @slash1andy, highly informative! I appreciate your time, link, and info.

    We’re in Canada, so that may account for some of this.

    Just to be unambiguous: prior to Stripe activating the gated feature on our account, we saw “Received unknown parameter: level3” errors on most transactions. The plugin didn’t learn level3 wasn’t available and insisted on sending it every time, triggering an error. This was unrelated to the level3 totals mismatch.

    I noticed the 400 errors from the API logs on the Stripe dashboard.

    Plugin Support dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hey @peterwills

    Can I ask if we can help more with this or was your reply to AW clarifying this for anyone else searching for this same scenario?

    If we’ve sorted this for you, please do mark this thread as Resolved.

    Thanks!

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

    – Joey

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Level3 Data’ is closed to new replies.