No, you can create a customer token and that token will forever refer to the credit card details the user entered. The only way you could consider that they "expire" is if the card as-entered expires, or if the user cancels that card. But even in this case your token still works, it just points to data that isn't valid anymore.
Unless celery does anything else on top of this (auto notifies customers if the cc expires in the interim, provides them a way to update details without you needing to do anything) then I don't see any compelling reason to use it.
Comments
No, you can create a customer token and that token will forever refer to the credit card details the user entered. The only way you could consider that they "expire" is if the card as-entered expires, or if the user cancels that card. But even in this case your token still works, it just points to data that isn't valid anymore.
Unless celery does anything else on top of this (auto notifies customers if the cc expires in the interim, provides them a way to update details without you needing to do anything) then I don't see any compelling reason to use it.