Durante nossa análise de dados de pagamentos n?o aprovados, notamos um comportamento onde compras onde o 3D Secure foi requisitado, e o usuário estava realizando a compra através do smartphone, o iframe para valida??o do código torna-se inoperante, impossibilitando o usuário de colocar o código pois n?o fica visível o campo.
O iframe aparece, mas fica totalmente fora de propor??o, n?o sendo possível dar zoom out ou ajustar a tela para encontrar o campo.
Em compras através do computador, e tiveram a requisi??o de um código 3D Secure, as compras foram realizadas. Como a tela é maior, o iframe funciona sem problemas.
Realizamos o teste em ambiente de homologa??o para ter a certeza do problema. Para testar, vá até uma view mobile ou teste direto do celular, mas precisa usar o cart?o de teste que terá o challenge com sucesso.
Mastercard (fluxo de challenge de sucesso do 3D Secure), você encontra aqui: https://www.mercadopago.com.br/developers/pt/docs/checkout-api/how-tos/integrate-3ds
Aparentemente, o iframe n?o é otimizado para mobile. E estamos abrindo este ticket para que vocês possam testar e arrumar esse iframe na vers?o mobile quando o checkout faz uma requisi??o de código 3D Secure.
——-
English version:
During our analysis of declined payment data, we observed a behavior where, when 3D Secure is requested for purchases made via smartphone, the iframe for code validation becomes inoperable. This prevents the user from entering the code because the input field is not visible.
The iframe appears but is completely out of proportion, making it impossible to zoom out or adjust the screen to find the field.
For purchases made on a computer, where a 3D Secure code is also requested, transactions are successfully completed. Since the screen is larger, the iframe functions without issues.
We conducted a test in a staging environment to confirm the problem. To test, please access a mobile view or use a mobile device directly, but make sure to use the test card that will trigger a successful challenge.
You can find the Mastercard test card (for successful 3D Secure challenge flow) here: https://www.mercadopago.com.br/developers/pt/docs/checkout-api/how-tos/integrate-3ds
Apparently, the iframe is not optimized for mobile, and we are opening this ticket so you can test this iframe in mobile view and fix it when the checkout requests a 3D Secure code.
Thanks
]]>If I set Contingency for 3D Secure = 3D secured when required, what happens is someone from outside EU, or whose card processor does not require SCA, makes a payment? Will they be able to pay, or rejected?
I’m asking because since I’ve switched to Woocommerce and set the above settings, sales dropped a lot. I wonder now if legit customers are rejected or not.
Thank you.
]]>I have a pretty simple forminator form with stripe payment element in the form, everything appears to be set up correctly but I have a strange behaviour – when users submit and make a payment they initially get a message above the form in the style of an error that says:
“This payment require 3D secure authentication! Please follow the instructions”
Screenshot link (only active for 3 days from this submission):
After a few seconds the form automatically reloads/resends or does some action as the message disappears and the grey loading bar reappears and the payment processes successfully.
]]>Here is the response from Stripe….
Hi Mark,
Thanks for taking the time to receive my call today. It's always a pleasure.
As promised, I will be sending you a guide in order to prevent incomplete payments from happening in the future.
Ideally, you need to seek assistance from a developer or your plugin Woocommerce and follow these steps:
Create a payment method using:
https://stripe.com/docs/api/payment_methods/create.
Once you have the payment method ID, please proceed to updating the PaymentIntent using https://stripe.com/docs/api/payment_intents/update.
You’ll need to simply add the payment_method parameter and include the payment method ID which can be found via the Logs (The id that starts with “pm_” under the Response body of the Create a PaymentMethod object you’ve passed.)
After you update the PaymentIntent, it’ll transition to requires_confirmation. You’ll then need to confirm the PaymentIntent by using: https://stripe.com/docs/api/payment_intents/confirm.
Upon confirmation, the PaymentIntent will attempt to initiate a payment.
After confirmation, if a PaymentIntent has a requires_action status, inspect the PaymentIntent’s next_action. If it’s redirect_to_url, that means 3D Secure is required.
To redirect the customer to the 3DS authentication page, pass a return_url to the PaymentIntent when confirming on the server, https://stripe.com/docs/api/payment_intents/confirm#confirm_payment_intent-return_url or on the client, https://stripe.com/docs/js/payment_intents/confirm_card_payment.
Hope that gets you back on track. In the meantime, please let me know If you have any other questions or comments regarding Stripe and I’ll be more than glad to answer.
Have a great day,
Errolprint: https://jmp.sh/wrXXX8bZ
]]>I found out that when someone is trying to pay with Visa or Mastercard and the 3D secure check is raised by Stripe, then the payment fails with error message “Something went wrong”.
I located the problem in file “/app/Modules/PaymentMethods/Stripe/StripeInlineHandler.php” and at line 416, as Argument 1 of “update” method should be passed as an array, and not as an integer.
Please fix it before any future update as it will break again my payment form.
Thanks
]]>Any help in troubleshooting this issue would be greatly appreciated.
]]>I’m using cards that I know 3d secure is enabled, but never is showing the verification step.
I’m in test environment with test stripe credentials using 4000002760003184 card for example, popup is working fine.
How can I force the 3DS verification?
]]>in our website we are using the WooCommerce Stripe Payment Gateway integration for payments.
Usually everything works correctly but lately some orders fail and remain “pending payment” from our backend.
By checking the stripe dashboard, the orders are unsuccessful due to the unsuccessful attempt of 3d Secure.
Speaking with stripe customer service they told us exactly:
“The WooCommerce plugin uses Sources, which have become obsolete for credit card payments. The Sources cannot handle payments with cards that have 3D Secure 2.
From October 2022 all major card circuits have stopped supporting 3D Secure 1. With cards that have 3D Secure 1 there should not be any problem, while cards with 3D Secure 2 will have problems for payments that don’t fall within the exceptions.”
Is it true that the plugin does not support 2d secure 2? Because we are losing a lot of orders due to this issue.
]]>