#corytea
1 messages · Page 1 of 1 (latest)
To double check, are you getting actual declines or is the payment intent going in to a requires_action status? requires_action is not an error and is actually expected as part of any flow when 3DS is required
checking
I get this, so a failed invoice, and then seperate required verification
Ah, that is expected. That invoice.payment_failed event happens whenever an invoice payment does not immediately succeed. So it is counterintuitive but that event is expected when the payment simply required 3DS to go on and later succeeds
Ok cause i have code to remove all other cards attached
via webhookk when a user adds a card
but in this case they are ending up with 2 cards in their accountr
I see i had that code in payment_intent.succeeded
maybe i should have it in payment_method.attached
Can you send me the ID of a customer that you are seeing that behavior on?
For an already saved card, Stripe won't create another payment method just because the card went through 3DS
sure cus_PXs6LBN9ub4Ckb
Are you directing your users to Stripe's hosted invoice page for these payments? Or is this your own custom page?
From what I can see, the second time the user re-entered their full card info. So it wasn't 3DS that created the new PM, it was that new card info was entered (even if it was for a card that was already saved)
cuystom
Gotcha, and is your custom form just the card element? Or do you have UI where the user can select a previously saved payment method?
Basically, for your own custom page with Elements, you will need to provide your own list of saved payment methods, if the customer chooses a payment method from that list, you can confirm the payment intent with the ID of the saved payment method to reuse it.
It is still possible to have duplicate payment methods if the user inputs their card data again instead of clicking on the saved PM, but there are ways to check for duplicates and remove them if that is what you want to do.
ok 5thx