I'd like to know the following: can't you already do this with Stripe? They seem to use stripe as their backend, so how is this different than me doing this with stripe on my own (i.e. collect charge tokens, charge later)? Or do stripe's tokens expire after a short period of time, I haven't looked into that yet.
I genuinely want to know because I'm potentially interested.
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.
You could do it yourself, but there's a lot of people who don't have the technical knowledge to do so. This is my understanding from speaking with independent makers and builders (e.g., Kickstarter grads) over the past year. Payments is only one part of commerce. Our mission is to package everything together (order management, analytics, a commerce API, etc).
Comments
I'd like to know the following: can't you already do this with Stripe? They seem to use stripe as their backend, so how is this different than me doing this with stripe on my own (i.e. collect charge tokens, charge later)? Or do stripe's tokens expire after a short period of time, I haven't looked into that yet.
I genuinely want to know because I'm potentially interested.
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.
You could do it yourself, but there's a lot of people who don't have the technical knowledge to do so. This is my understanding from speaking with independent makers and builders (e.g., Kickstarter grads) over the past year. Payments is only one part of commerce. Our mission is to package everything together (order management, analytics, a commerce API, etc).