#Derek Pankaew

1 messages · Page 1 of 1 (latest)

brisk pollenBOT
balmy panther
#

SetupIntents create PaymentMethods under the hood, and have the additional benefit of allowing you to correctly set up the PaymentMethod to allow for recurring/future charges

#

So for example, if you were to collect card information through a SetupIntent we can also run 3DS to authenticate that payment method for future usage and give it a higher chance of successful payment in the future

slim sentinel
#

I see, got it. Does SetupIntent require the use of the Payment Element, as opposed to collecting card info on our own front end? (It's not possible to configure SetupIntent to use our own card collection mechanism correct?)

balmy panther
#

If you're using your own card collection mechanism are you working with raw card numbers and sending those to us to create paymentmethods?

slim sentinel
#

Yes

#

I think the PaymentMethods API allows that, but I can't tell if SetupIntents allows that

#

I'm still trying to understand the pros and cons of doing that

balmy panther
slim sentinel
#

Oh ... I see, I didn't realize that. I thought PCI compliance only matters if we're storing the information

#

Got it ... in that case, we'll probably go ahead and use SetupIntents with the Payment Element

balmy panther
#

👍 Yeah unless you have a really good reason I wouldn't mess with PCI compliance