#greatesteu_api
lost havenBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1252720048158675005
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
shy galleon
Hello
When you say a temp user is created, is that something you're creating on your app? I'm not sure I fully grasp how you're collecting payment method details and associating them prior to creating the subscription
Can you elaborate on what your current API calls sequence looks like?
vapid moth
Yes, sorry- only limited to 600 characters in the description so we may have some back n forth for additional details.
The current flow is as follows:
1.) User enters product page and selects products
2.) Checkout process is started
2a.) User gets created temporarily within the app (because subscriptions can't be attributed to guest users according to the Stripe plugin)
2b.) Products get created within Stripe
2c.) Stripe Gateway is loaded
2d.) User enters payment method within the Stripe Gateway
3.) Subscription is created within Stripe
Once the subscription is created it associates the stripe user via the app user's email by default. So anytime the user were to attempt a guest login on that email, the payment information would automatically be there- My goal is to avoid this, but I can't find anything within the docs to make this possible.
shy galleon
Oh you're using a third-party plugin?
Unfortunately, we won't know anything about that. This server is only for questions related to Stripe's first party APIs/SDKs
vapid moth
Well it's an official Stripe plugin, but I can push via API as well
The plugin itself was developed by you guys lol
shy galleon
A different team at Stripe maintains stripe owned plugins. My team on discord isn't familiar with how they were built and how they function 🙂
I'd recommend writing in via our support team, they can put you in touch with the right folks for this
https://support.stripe.com/?contact=true