gandulf78

Hi. Thank you Herman for looking into it.
I notice I have to set Webpagetest from California EC2 Chrome to see the issue (my server is in France). My targeted audience is in the US.
I have a short film strip to illustrate:

Transiently another menu is displayed then replaced by my menu.
I confirm that I am using W3 Total Cache plugin.

• This reply was modified 3 years, 3 months ago by gandulf78.
• This reply was modified 3 years, 3 months ago by gandulf78.
• This reply was modified 3 years, 3 months ago by gandulf78.
• This reply was modified 3 years, 3 months ago by gandulf78.
• This reply was modified 3 years, 3 months ago by gandulf78.
• This reply was modified 3 years, 3 months ago by gandulf78.

Hi Herman.
Thank you for your quick answer.
Regarding the cache, would you have any clue of the exception in the caching rules to handle it properly?
Regarding the sidebar, could you please tell me where to find the documentation for implementing it ?
Thank you ??
Kind regards.
Laurent

Sure. It is: https://withlovefromfrance.fr
I have tested with recaptcha v2 (with the plugin) and the badge is showing up. I just went back to recaptcha v3 to show you.

• This reply was modified 3 years, 5 months ago by gandulf78.

Same here. I tried V3, V2 invisible and V2 with button. Cannot make it working…
It is working with Catch Bank so I believe the issue is with the plugin, not with my reCAPTCHA account/settings.

So I thought about that. I can see two options to improve the behavior of the “Payment Request gateway”.

1) The first would be to have exactly the same behavior for each Google Pay, Microsoft Pay etc as the standard Apple Pay:
o Pay with Google Pay (for ex) and on the right the Google Pay mini logo
Instead of the standard “Payment Request gateway” with the browser logos which may be confusing for the customer. I am not sure every customer understands why to click on this button and why the browser logos are there. If “Google Pay” (for example) is directly displayed, it is completely straight forward.

2) The second would be to have the Pay button on top of the “payment methods” (first choice) with an OR for the credit card (second choice). It would also need to move my Woocommerce checkbox “I have read and agree to the website terms and conditions” over the payment methods area.

Thanks for your help.

• This reply was modified 3 years, 6 months ago by gandulf78.

I see. Thank you but actually it is not what I am looking for since i need my customer to enter details and accept the terms & conditions.
What I would like is to have the button just over the credit card details in my paiement methods box with an “OR” instead of the radio buttons.
It would be great.
Thank you for your continuous support, it is very appreciated.

That’s good news, thank you. Sorry, I feel stupid but i cannot find it.
I searched in the documentation too and didn’t find either.
Where is it ?
Does it apply to all the Pay buttons?
Thanks.

What other display options are you referring to?

Actually, I would love to have also the possibility to have a OR choice (like in https://stripe-payments-demo.appspot.com) instead of the radio buttons. Would be seamless for the customer.

• This reply was modified 3 years, 6 months ago by gandulf78.

Thank you. It is working perfectly.

Sorry for the confusion. I had to switch to this alternative plugin because WooCommerce Stripe doesn’t offer the capability to chose on which page to display the “Apple Pay” (or Google Pay) buttons. It is either on every page or nowhere.
I absolutely need for the customer to accept the terms and conditions and to fill some data before to pay.
Have a good one.

Actually I am referring to the image for ??browser payment?? in the documentation of the plug-in there below ??The text that appears on the checkout page for the gateway.??:
https://docs.paymentplugins.com/wc-stripe/config/#/stripe_payment_request
Thanks

• This reply was modified 3 years, 6 months ago by gandulf78.

Finally, I’ve used the clean up tools in WC and it is working!

BTW, I don’t know if it is related also i also noticed the following error in the Stripe logs :
POST /v1/payment_methods
parameter_missing – type
Missing required param: type.

{
“key”: “pk_test_*********************************************************************************************qubhXs”,
“type”: <required>
}

{
  "error": {
    "code": "parameter_missing",
    "doc_url": "https://stripe.com/docs/error-codes/parameter-missing",
    "message": "Missing required param: type.",
    "param": "type",
    "type": "invalid_request_error"
  }
}

That’s kind of puzzling. It was working fine with the Stripe extension from WC so i am still suspecting an issue with your plugin.
I directly reached out the Stripe support and they said:
“Upon checking with the technical team, “The client_secret provided does not match the client_secret associated with the PaymentIntent”
means that something other than the client secret is being passed to ConfirmCardPayment. If you were creating the charges yourself, you could log out the client secret before you call ccp to verify that its the same as the one on the payment intent.”
I don’t know what to do with that.

• This reply was modified 3 years, 7 months ago by gandulf78.
• This reply was modified 3 years, 7 months ago by gandulf78.
• This reply was modified 3 years, 7 months ago by gandulf78.

Thanks for your help.
I see on the stripe dashboard some events “payment_intent.requires_action” with an associated webhook attempt tagged failed “400 (Bad Request)”
I hope it helps
Kind regards.