#nina_api
hollow micaBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1296923473322709092
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
safe rivet
Hi, are you asking if you can use the the old sources ids when you create the PaymentIntent? Or, something else?
final yacht
hi, currently we are using the token objects to tokenize the bank account information before we store it to use for withdrawals later...noticed in the migration to payment Intents doc its noted:
The Payment Methods API replaces the existing Tokens and Sources APIs as the recommended way for integrations to collect and store payment information
It’s not specific about whether or not the Tokens API is or will be deprecated if it’s being used outside of the Sources API
safe rivet
You can still use those and the are backward compatible for cards: https://docs.stripe.com/payments/payment-methods/transitioning#compatibility
You can keep using those old objects but you won't be able to create new ones. Instead, you'd use PaymentMethods.
final yacht
thanks @safe rivet , so just to confirm stripe.tokens.create will be deprecated and instead we should be using the paymentMethods?
to create new objects I mean
safe rivet
Yes, that is correct.