#Perry

1 messages · Page 1 of 1 (latest)

grizzled ospreyBOT
deep thicket
#

no, you would not use createToken any more

#

can i still use createToken API as i need this token response at my end?
you have to redesign the backend and overall approach so that instead of recieving a Token from the frontend and charging it, you create and return a Payment/Setup Intent from the backend to the frontend.

warm olive
#

Okay and why i should not be using Token? are they going to be deprecated in future?

deep thicket
#

it's been deprecated/not recommended for several years

warm olive
#

and the setupintent.paymentmethod ID that i will receive from confirmCardSetup can be used by third party client for future charges to customer right?

deep thicket
#

what is a "third party client" in this context?

warm olive
#

means thrid party platform who will save these details for future charges

#

it's not us who will charge the customer but this 3rd party secure platform will charge once validation is done

#

anyways, my main question is
this paymentmethod ID can be used to charge the end customer right?

deep thicket
#

hmm then it really depends who they are and what APIs they use and how they work

warm olive
#

okay, great
I will NOT be using payment intents as i mentioned this another platform will charge the user, so they were going to use Token but as you mentioned that tokens will be deprecated, hence i will pass them payment method ID

grizzled ospreyBOT
deep thicket
#

well you need to check with that platform/third party then

#

maybe they only have legacy code that supports Tokens, who knows. So you should ask them how your payment integration with them is supposed to work and for help designing it

warm olive
#

yes i have asked and they came back with response that tokens are required at their end for payment integration

#

and ensuring it's set for future usage

timber badger
#

Hey, taking over here. Let me know if there's any follow-up Qs I can answer!

warm olive
#

hello

#

yes, so if you can access tha above chat, i have mentioned the 3rd party client of ours need tokens for charging customer in future

timber badger
warm olive
#

but i got to know that tokens will be deprecated?

timber badger
#

yes tokens are deprecated, you should be using the new PaymentIntent/Method APIs

warm olive
#

okay, so the setupIntent.payment_method payment method ID that i will get from confirmCardSetup can be used for future payments right?

deep thicket
#

no need to repeat yourself

warm olive
#

mean if i pass this Payment method ID to this 3rd party platform, they should be able to charge the customer

deep thicket
deep thicket
warm olive
#

okay, so we are suing peoplevine as our end platform, peoplevine is the 3rd party platform whic will charge

deep thicket
#

ultimately if they are not and they require tokens and you require to work with them, then you need to keep creating/using Tokens

warm olive
#

okay

deep thicket
#

'deprecated' to us means we don't document the approach and we discourage it and we might restrict it for new users and we reach out to users to get them to migrate, but ultimately we wouldn't arbitrarily disable the API itself without notice since we are aware of plugins/platform like this

warm olive
#

okay now i understand, i thought deprecated means they will be removed forever
but if they are still in use then let me have a word with peoplevine team.
if they still need tokens then i will use tokens, but if payment methods ID are way to go then accordingly we need to agree upon 🙂

#

How long do you think these tokens will survive in Stripe environment?

#

hello team

deep thicket
#

that's not a question we can answer

warm olive
#

okay no worries