#wolfi-elements-subscriptions
1 messages · Page 1 of 1 (latest)
Current Setup:
Our users currently subscribe using the Stripe Payment Element.
We want to ensure that the entire process, from subscription to updating payment methods, happens on our platform without redirecting users to the Stripe dashboard.
Objective:
We aim to provide a seamless experience for our users to update their payment method in a secure and compliant manner. Specifically, we want to:
Allow users to select and confirm a new payment method via our portal.
Update the default payment method for their subscription based on their selection.
Ensure that the updated payment method is used for subsequent subscription renewals.
Thanks for your response while we've successfully integrated the Stripe Payment Element for initial subscriptions, we're struggling to find a clear flow in the documentation for allowing our subscribers to update their payment method via our custom portal.
Could you provide guidance or point us to resources that detail how to implement this while ensuring security and compliance?
We won't really have a specific resource for that specific use-case. But you want to look at https://stripe.com/docs/payments/save-and-reuse which is how you can collect payment method details for future payments.
Thank you for pointing us to the "save and reuse" documentation.
We've already integrated the process of storing the payment method ID for our subscribers after checkout with elements.
However, our challenge lies in allowing subscribers to create a new payment method and then replacing the existing one for future payments.
Could you guide us on how to:
-
Allow subscribers to add a new payment method via our portal?
-
Replace the existing stored payment method ID with the new one, ensuring it's used for subsequent subscription renewals?
that's exactly what I just did! I linked you to the clear doc on how to collect a new payment method from your customer. This is the guide you would use to collect a new one right? That's the first step
oh, sorry for the misunderstood. we are checking now the flow and if the flow can be integrated with the Stripe Elements instead of checkout to ensure a consistent user experience on our portal.
Sure, on that doc there's a clear split at the top to decide what integration to use
https://stripe.com/docs/payments/save-and-reuse?platform=web&ui=elements is the exact link for web + PaymentElement
And so doing this will let you collect payment method details for future payments. And then the next step is to make that new PaymentMethod "the default". There are many ways to do this and it depends how you integrate today.
You can set the default payment method globally on the Customer object inside invoice_settings or directly on each Subscription. See https://stripe.com/docs/billing/subscriptions/payment-methods-setting#payment-method-priority
Thank you, @oblique bramble , for your guidance and the resources you've provided. We'll use the information as a starting point for our implementation. We appreciate the clarity you've brought to our concerns.
If we encounter any challenges or have further questions during the implementation, we'll reach out. In that case can we still use this thread?
Thanks again for your prompt and helpful support!