bilal-legacy-apis | Stripe Developers | Page 1

rare vaultBOT Jun 16, 2023, 5:24 PM

#

fierce light Jun 16, 2023, 5:29 PM

#

bilal-legacy-apis

#

@agile scarab those are legacy APIs deprecated back in 2018. They are incompatible with a lot of flows such as 3DS, Mandate collection, redirect for other payment method types, etc.

#

So really you should not use those APIs in a new integration

agile scarab Jun 16, 2023, 5:30 PM

#

But for saving credit card detail i still have to use Stripe::Customer.create right ?

fierce light Jun 16, 2023, 5:31 PM

#

Yes just don't pass the source id or use the Create Charge API

agile scarab Jun 16, 2023, 5:35 PM

#

So how can I migrate all the existing customers to SetupIntent Api ?

fierce light Jun 16, 2023, 5:36 PM

#

You don't need to migrate anything, those will continue to work. You would evolve your integration to use SetupIntents or PaymentIntents for new Customers/new payments

agile scarab Jun 16, 2023, 5:42 PM

#

Got it, So as per documentation SetupIntent is only for storing payment method details, for that we have to integrate paymentElement ? or something else ?

fierce light Jun 16, 2023, 5:46 PM

#

SetupIntent is to collect payment method details without accepting a payment immediately
PaymentIntent is to accept a payment immediately and you can collect payment method details at the same time and even save those automatically after the successful payment.

Elements is our UI library of components to collect payment method details. There are many different Elements. The most recent one is PaymentElement which is what we recommend and it works with both PaymentIntent and SetupIntents

agile scarab Jun 16, 2023, 5:50 PM

#

Got in, Thank you 🙂

#bilal-legacy-apis