#hendi-legacy-card
terse dust
torpid veldt
Hi 👋
All payment tokens created with the /v1/tokens API are single use tokens unless attached to a Customer object before they are charged.
ornate spindle
I believe we now get them through a beta product using elements?
Manually entering cards in other words
torpid veldt
I'm sorry but I would need much more specifics here. Any payment method is a single use payment method unless configured for re-use.
How are you creating these payment methods? What API calls are being made?
ornate spindle
OK, understand about payment methods
So for the tokens API, that did not have the concept of a future use setup, right? So the token you get from that, you can either use for a one-tine payment, or add it to a customer, and then use the token from the customer for future payments?
ornate spindle
ok, so if I have tokens in my db that start with tok_, those cannot be used for subsequent purchases?
torpid veldt
If they have been used.
ornate spindle
and I might as well delete them?
torpid veldt
Unless you need to hold onto them for a specific reason (e.g. referential integrity, reconcilliation, etc.)
ornate spindle
no, we have loc al copies of customer "wallets", but from what I understood from you, once a token is saved to a customer, the token becomes a card_ ?
I think we had a bug, saving the wrong token, we should have saved the card_ token we would have gotten back from the customer endpoint after saving the token to the customer, right?
hollow fjord
correct the tok_123 is like a temp alias to card details and you use it to turn those card details into either a one-time charge or a saved Card object for future re-use, in which case you store the card_123