3X Web Desenvolvimento Digital

@marcosgn testei a última versão e continua desta forma, no retorno do pix é inserido em um novo pedido.

@marcosgn tudo bem se eu entrar em contato com você pelo git pra gente trocar contato?

Sim, obrigado pela resposta rápida, estou usando:

Pix Automático com Pagarme para WooCommerce Versão. 2.0.2
WooCommerce Versão 6.7.0
Pagar.me módulo para Woocommerce Versão 2.0.8

Os pedidos duplicados ocorrem exclusivamente quando o pagamento é via pix.

Hello @nicw

I’ll be running some tests later on today, i don’t believe it’s a compatibility problem, since the checkout does work with all supported brands and I’ve been using this same theme and plugins for a while without problem.

As i said in a previous message, I believe it’s a usability problem, since the card form allows for an unsupported brand to be typed in, but returns no error, for it’s passing valid card data to validation (number + cvc + expirantion) to Stripe.

I’ll look further into this matter and will post my findings soon.

Regarding the lack of an error: if there is an error generated, it will be added to the checkout, unless there is a conflict with an existing plugin, or possibly the theme. To test whether this is the case, you should try disabling all plugins except WooCommerce and Stripe, and test checkout while using the Storefront Theme.

I fear all tests will work regardless and won’t trigger this same problem with test data. I’m hoping for a customer to try an unsupported card again and ask for support for me to check his console for JS erros too.

Anyway I’ll post my test logs later. Thanks for your help.

Hello @dougaitken,

Thank your for carefully reading this thread.

The core of your query sounds like how handling of an unsupported card brand should show the customer, do I have that correct?

Yes you are correct, it needs an error to inform customers about this, preventing them from proceeding with checkout, or at least presenting an error.

I’m also trying to inform about this problem, since it must been affecting other users as well, as in:
https://ww.wp.xz.cn/support/topic/stripe-not-loading-in-strange-conditions/
And many others who are not yet aware.

Can you clarify how you are losing money? Do you mean lost revenue due to the transaction not being successful?

A few customers reported this checkout behavior and gave up from buying on our store. Our products range from R$ 500 to R$ 3900.

Hello @apmwebdev. Actually there’s are none, the plugin does not process the payment at all.

I’ve read your code for a while, i see there’s a helper funcion called get_supported_card_brands() inside class-wc-stripe-helper.php:326, but i cannot find any other call to this function beyond get_icon(), i’m not sure if this was supposed to wait for API response from Stripe to check for supported brands.

I would say you should validate the card brand before calling API for (i’m guessing) createSource().

I’ve checked Stripe Docs and i’m making a wild guess here, i see there’s support for a few as in the array bellow:

var brandClass = {
	'visa': 'stripe-visa-brand',
	'mastercard': 'stripe-mastercard-brand',
	'amex': 'stripe-amex-brand',
	'discover': 'stripe-discover-brand',
	'diners': 'stripe-diners-brand',
	'jcb': 'stripe-jcb-brand',
	'unknown': 'stripe-credit-card-brand'
};

When a certain unsupported brand is typed, an ‘unknown’ card is sent to validation inside the card object on “brand” string, then stripe’s validates this card (cc number + CVC + expire date) thus not returning an ‘card_error’ type error, and this may be causing this weird behavior.

What do you think?

• This reply was modified 4 years, 9 months ago by 3X Web Desenvolvimento Digital. Reason: formatting code