#Riiver
fiery zodiac
would it be possible to pre generate a bunch of tokens and assign them at a later time?
Hello! This is technically possible, but discouraged. This is both an older API that we no longer recommend people build with and we don't have a publicly-defined expiration on these Tokens.
silk arch
Could you clarify on publicly-defined expiration? As in there is no expiration or there is one but it is not exposed through the api
fiery zodiac
We don't publicly document an expiration for these Tokens, we only recommend you don't store them.
Can you tell me more about your use case? I might be able to make a better alternative recommendation.
silk arch
There is one credit card we would like to associate to multiple accounts on user creation but we dont want to store the credit card anywhere
we would like to generate the card token and keep them in a pool for assignment
fiery zodiac
Tokens can only be used once, so that's not viable regardless of how long they last.
Are you using Connect?
silk arch
true true but i think the current idea is to create many tokens using the same credit card
fiery zodiac
That is really not recommended. 😅 Yes or no on using Connect? If you're using Connect I have a solution for you.
fiery zodiac
With Connect you can clone payment information from your platform account to multiple connected accounts: https://stripe.com/docs/connect/cloning-customers-across-accounts
silk arch
interesting, we will look into it
fiery zodiac
If you're building something new we strongly recommend you don't use Tokens/Charges and use Payment Methods and Payment Intents instead, BTW.