#rpoulose-setup-intents-pm
1 messages · Page 1 of 1 (latest)
pm_1Kt77iEIzwO0cI9aXoTFoNRY - this is on a test environment
Is there a reason why you're creating a PM and Setup Intent separately and then attaching it to a customer?
What are you actually trying to achieve?
The PM is created by our front end using Stripe client libraries (we don't want to pass any details like CVV to our backend). Once the PM is created by front-end we do certain checks on the backend service (like card type, duplicate fingerprint etc.) and only then do we attach the PM to the customer
Is the intention to use the card for future payments?
There's a better way to do this: https://stripe.com/docs/payments/save-and-reuse
(you shouldn't really use the attach endpoint as it can trigger a 3DS/auth check with no means to facilitate it)
So we do use the SetupIntent and confirm it by a call from the UI. Here is an example req_aE10AhLMhbJPV3. Wouldn't the 3DS/auth check happen when the SetupIntent is confirmed?
it would yes