CB error handling behaviour

  • Resolved ataypamart

    (@ataypamart)


    3 years, 2 months ago

    Hi,

    Let me start by saying that I enjoy very much the plugin you provide. I only have two issues with it, the first being that there are no translations to French (the target site of the website we are building) and the second is that I encounter a slightly uncertain (random?) behaviour on stripe error.

    To replicate (this is on the website below, but i do no see anything specific we do that would explain this) simply use the CC provided by stripe for test 4000002760003184 which triggers 3D auth all the time. Then fail the fake authentication.

    Error gets reported nicely as “The provided payment method failed authentication. Provide a new payment method to attempt this payment again.”. So far so good. However, it seems to me that the form is now in a strange state.

    If you now try with the basic test card “42424242424…” you get the authentication 3D again (?) which is kind of really unexepcted.

    In a distinct test, with a new order (new “payment intent” i suppose), I get a slightly random behaviour, again with the “Force 3D” card 4000002760003184. After failing the authentication twice (manually) I get a new error message: “The Payment expected a payment method with different properties than what was provided.” Then switching back to 4242424242 Is get “The Payment expected a payment method with different properties than what was provided.”.

    Shouldn’t the payment intent be reset on failure of the credit card check? It seems that there is something that remains across calls to stripe and that provides a certain level of randomness.

    Am i doing something wrong? I am trying to test combinations that are slighlty outside the happy path to see if I invest the time in translating the plugin 🙂

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Sravan Bhaskaravajjula

    (@bhshravankumar)

    3 years, 2 months ago

    Hello @ataypamart,

    1. Please use the Loco Translate plugin to translate, please note the payment form fields are loaded by the Stripe and could not be converted through our plugin.
    2. I tried to replicate the issue on my test website but could not able to replicate it, please share a screen recording of the same for further investigation.

      Best,
    Plugin Support Aamir

    (@aamiribsf)

    3 years, 1 month ago

    Hello @ataypamart,

    It’s been a while since we haven’t heard from you so we are marking this thread as resolved.

    If you faced any other issues while using our product, feel free to start a new thread.

    Best regards,

    Thread Starter ataypamart

    (@ataypamart)

    3 years, 1 month ago

    Sorry @aamiribsf i did not get your reply until now. Bit of a missed opportunity since then I switched to using another plugin (which is translated to french, so less work for me). The strange behaviour bit was easy to replicate from what I remember and this was almost deterministically strange if you see what i mean. Maybe this was just a stripe API fluke I don’t know. Sorry for the absence of reply, this was very impolite of me.

    Plugin Support Sravan Bhaskaravajjula

    (@bhshravankumar)

    3 years, 1 month ago

    Hello @ataypamart,

    Thanks for the update.

    Let us know if we could be of any further assistance. 

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

The topic ‘CB error handling behaviour’ is closed to new replies.