batangaTroy-paymentmethods | Stripe Developers | Page 1

thick solar Sep 17, 2021, 11:45 AM

#

@ruby bluff sure, what's the question? Cards and PaymentMethods are mostly the same concept but Cards are deprecated and you should never use them

ruby bluff Sep 17, 2021, 11:46 AM

#

ok. that's answers the question. I was looking for best practice. Good. I implemented PaymentMethod and then found the Card API and thought "um, what?"

#

thank you

thick solar Sep 17, 2021, 11:48 AM

#

it's a legacy API. Basically we had the Card API from the beginning as Stripe only did credit card payments, then we realised we needed a more generic representation of a 'payment instrument' when we added more payment methods, so we created Sources... and then we realised Sources had problems, so PaymentMethods are now that generic payment instrument class and we're fully committed to it

#

we made it backwards compatible as well(https://stripe.com/docs/payments/payment-methods/transitioning#compatibility)

ruby bluff Sep 17, 2021, 11:50 AM

#

sounds good. one related question, I (think I) noticed that when using the Test Environment and the test cards that the payment_method->id was always the same regardless of the card I used - is that expected because it's the Test Env?

thick solar Sep 17, 2021, 12:03 PM

#

it should be different I would think

#

the pm_xxx should be different for each object you create even if the card number/other details are the same

#

hard to say without looking at some examples!

#batangaTroy-paymentmethods