tchernaev

Yes, I managed to create the the file and place it mu-plugins folder. The I tried again but this did not solve the problem.

1. This is regular order of a physical product.
2. No custom code using Stripe plugin filters
3. Card and Apple pay
4. Guest customer / the customer tried to pay multiple times
5. We are using CheckoutWC

Hi again,

I get another error from the Payment Plugin I cannot understand. I can confirm this is after the update to the last available version.

This image is from a Hotjar video. The customer tries to pay with a card. The customer initiated 4 payment attempts. The log shows that the payment started and ends with a status of incomplete.

okay, great. I am also interested in your Premium support subscription. I will write an email to you from https://paymentplugins.com/ so you can send me more details. Thanks for your cooperation!

I absolutely agree with that. I had another open topic regarding this issue as I am coming from another payment plugin for stripe where these intents were not created.

Okay, basically is this Payment form (beta) safe to use. I mean beta means they might be some bugs, I would rather change to something not beta. Would you recommend going back to the other payment form?

I am using CheckoutWC.

I also noticed that Payment intents are no longer created once a visitor adds a product to cart. They are no longer created in the updated version.

This is captured by Hotjar. I have experienced lower conversion rates since moving to Cloudflare, so now I am investigating errors through Hotjar.

This has happened before the update, because I did the update just 30 min ago.

I have a full video of the interaction of the client. The client contacted us and then I checked his session. He eventually paid after a second try, but this error is something I would like to know more about.

The payment was with card.

I had another error:

Is this caused by Stripe or by your plugin?

• This reply was modified 2 years ago by tchernaev.

Okay, I have updated the plugin. Do you think this would solve the problem?

This is the last answer from Stripe support:

Thanks for reaching out to Stripe support. It was a pleasure interacting with you today. I understand you requested assistance with a request error shown in your account logs and I am glad I was able to assist you. 

As we discussed during our conversation, the payment pi_3M4QTsDgb9BnSsnz3PMditUF was not process because the user is trying to complete the payment with the Link payment method, the request body is set to this: 

"payment_method_types": [
        "card",
        "link"

However, this payment shows: 

 "directory_server_name": "cartes_bancaires"

In order to accept Link payments with Cartes Bancaires, the request and the integration needs to add this option as well. As you are using a third party integration with the "Payment Plugins for Stripe WooCommerce" platform, you can reach out to them to clarify this issue.

Stripe account ID: acct_1DbqKRDgb9BnSsnz
Payment ID: pi_3M4QTsDgb9BnSsnz3PMditUF

Stripe is showing the customer tried to pay with LINK. After the try, the payment was declined showing this message as an error.

@mrclayton thank you. I will stay with the beta and I will await an update without payment intents. Thanks!

• This reply was modified 2 years ago by tchernaev.

@mrclayton the only problem is that LINK feature will not work with the Stripe Inline form, so in order to increase the conversation rate it is better to stay with the beta, right?

@mrclayton and would it be possible that in my case since I am using WC checkout, that they have equal design for this form? Or the design comes from your plugin? Sorry for the many questions, I think this topic will be helpful to many people with the same issue.