#pcpw
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- pcpw, 3 days ago, 11 messages
- pcpw-node-retries, 3 days ago, 7 messages
Hi, let me help you with this.
- This needs to be
off_session: false, it will fail if customer action is required, e.g. 3DS. - You look at the
status: "requires_action". - You need to use
handleNextAction(): https://stripe.com/docs/js/payment_intents/handle_next_action
Having said that, I hope you know what you're doing, as normally if the PM is set up correctly it shouldn't trigger customer actions. Usually in that case you would ask the customer to provide a different payment method.
I’ll be using an existing PM saved on an existing customer. If the customer successfully authenticated using 3DS when they first added the PM, does that mean all subsequent payments in the future will not trigger 3DS?
3DS is triggered by the bank, so we don't control it. Normally it shouldn't. But the bank might just decide to ask for 3DS for no apparent reason. This usually means something is wrong and it's worth asking the customer for another PM.
So if that happens do I still invoke handleNextAction and have the customer go through 3DS or should I treat it as a payment failure and ask the customer for a different card