#MaggyD-checkout-subscription
1 messages · Page 1 of 1 (latest)
Hi there 👋 out of curiosity, can you help me understand the business use case for that scenario? If you don't save a payment method when creating a subscription then the renewals will fail without additional work.
That's a bummer because, well, we track stripe customer_ids as a field for users in our database, however, we are an email only application, we do not ask users to create a password to use our service
Therefor, someone can make a fraudulent charge by just having access to someones email, exposing the last 4 digits of the card
I am guessing I may need to do some email verification then... which is fine, I wanted to get around that, we can't do passwords unfortunately, so I could secure the information via an email
Gotcha, when you create a Subscription through Checkout, steps are taken to prepare that payment method for future off-session payments in an attempt to set up the best customer experience possible. So not saving the info would prevent that from working correctly, and without a saved payment method on file then the subscription's renewals will fail until a payment method is provided. If you don't want that info stored in Stripe, then you can build subscription logic on your end and just process payments through Stripe as one-time payments.
Ok, thank you for your time