#batler-payment-integration
upbeat meteor
Looking in to this
Taking a step back, is there a reason you are working on this specific API call? That is a legacy call that most users starting with integrations today would not need to use
plain knoll
I've got two different people telling me that the other is older.
I'm new to Stripe and want to use the newest though I'm not sure how to determine who is right and who is wrong 😐
I'm not allowed to use existing libraries or frameworks on projects so all the code has to be done direct. So if you could please direct me to the newest API version I'd appreciate that.
upbeat meteor
That which one is older? We do have other older APIs, namely Sources. The current way to do this now is by using a PaymentIntent or SetupIntent which will create a PaymentMethod object (this wraps a card object like the one that you are trying to create). We have this intro doc for the most common modern flow https://stripe.com/docs/payments/accept-a-payment
plain knoll
I read that tokens are single-use only and that to save a card that I have to instead create a source.
upbeat meteor
Yeah, tokens and sources are the legacy integration path. We still support them but intents and payment methods are much more feature rich and easier to use
plain knoll
So... terminology wise, is there now a distinction between single-use "tokens" and multiple-use "sources"? Knowing the latest terminology will help me through the documentation a lot more.
upbeat meteor
Yes they are completely different objects. Tokens are for collecting information and sources represent an actual source of funds that can be charged
Though again, we heavily reccommend against using either if you are starting out now
plain knoll
I don't care about tokens and sources...what SHOULD I care about?
upbeat meteor
I would reccommend going through our starter doc and looking at the API objects that it works with. https://stripe.com/docs/payments/accept-a-payment?platform=web&ui=elements
cyan crystalBOT