#rpoulose-setup-intents-pm

1 messages · Page 1 of 1 (latest)

jolly gull
#

Hey, can you share an object ID of the PM or Setup Intent?

old bay
#

pm_1Kt77iEIzwO0cI9aXoTFoNRY - this is on a test environment

jolly gull
#

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?

old bay
#

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

jolly gull
#

Is the intention to use the card for future payments?

old bay
#

yes

#

and we do set the 'set for future usage' on the setup intent.

jolly gull
#

(you shouldn't really use the attach endpoint as it can trigger a 3DS/auth check with no means to facilitate it)

old bay
#

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?

steady needle
#

it would yes

old bay
#

ok.

#

Thanks for confirming that.

#

About my original question, if there was no postal code supplied in the PaymentMethod, is there a way to force the postal code of the customer when doing the address_postal_code_check?