#thescoutrocker - PM + Cust

1 messages · Page 1 of 1 (latest)

wanton kelp
#

Hi 👋

#

Do you have the request ID?

stable warren
#

Hi, sure

#

req_WBYmgU1xWdK7ks

wanton kelp
#

Thanks

#

Have you done this more recently?

Also we do not recommend this approach to attach a Payment Method to Customer. Setup Intents are the recommend process.

#

I'm seeing a failed cvc check for this card associated with the request to attach it.

stable warren
#

No, that's the latest

#

Ok but in that case the decline_code should be incorrect_cvc right?

wanton kelp
#

It can depend on what the bank responds with but I do agree that is kind of confusing

stable warren
#

Ok, let me explore the SetupIntents API, the problem with that is that we have the cards management process apart from the payment process, how we can use the SI to only create the PM without create any charge or payment?

wanton kelp
#

That is exactly what SetupIntents are for.

#

The "intent" is to "set up" a payment method with a customer for future use

#

No charges at that time

stable warren
#

Okok, let me explore it then

#

I thought that was a preconfigured payment intent

wanton kelp
#

You can use the Payment Sheet with either a Payment Intent (collect funds now) or a Setup Intent(save PM for future use)

stable warren
#

Great, and whats the main difference with the PM API?

wanton kelp
#

Creating a PM directly, especially with tokenization, doesn't trigger the validation steps so you miss the chance to bring the user back to fix any incorrect info

#

Using SetupIntents goes through both validation of the data as well as checks for any additional authentication

#

In general it results in PMs with a higher rate of successful charges

#

And less steps, API calls on the developer side