#luka-finderle_best-practices

1 messages · Page 1 of 1 (latest)

next troutBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1349351230446501918

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

wise void
#

I guess the Stripe concepts would remain the same as to whether it was for a friend or not – you'd create a Customer that maps to the individual who'll pay and how you map that to a 'friend' in your system would be an implementation details

wooden epoch
#

What happens if I pay for a subscription for a friend and they already have an active subscription? Will their already active subscription be canceled or will it be added to their existing one?

wise void
#

Nope, a Customer in Stripe can have multiple active subscriptions

wooden epoch
#

So it's actually best if we don't show anything inside the app, but let the user go into Stripe and manage their subscriptions there?

wise void
#

Sure, makes sense I guess. You can manage that however you want, but there's no conceptual limit to 1x Customer (cus_xxx) havuing multiple active Subscriptions (sub_xxx)

wooden epoch
#

Ok, thats great. Thanks a lot!
You can close this ticket

wise void
#

No problem, glad I could help!

wooden epoch
#

Just one more question. In this case when I pay a subscription to a friend, can my friend see in his dashboard that I have payed the subscription to him?

wise void
#

I'm confused now, which Dashboard are we referring to?

wooden epoch
#

Does every user have an active dashboard or some kind of a account details in Stripe to see all the history and other options about his subscriptions?

wise void
wooden epoch
#

Ok, but can that mentioned friend see somehow in Stripe that I have payed a subcription to him?

wise void
#

Not really no, you'd need your own UI to convey that

wooden epoch
#

Can you just clarify to me is it even necesery to create a stripe a account to pay a subscription?

wise void
#

No, not at all

#

I only mentioned that because you said 'active dashboard', so wanted to clarify we weren't talking about an account when you said 'user'

#

(e.g. some kind of Connect setup)

wooden epoch
wise void
#

I don't know what you're asking me

#

The portal (the link you sent me) displays relevant subscriptions and other configured info for the Customer in question. The URL is generated for a specific Customer object (cus_xxx) so all the info there is scoped to one customer

wooden epoch
#

So let's first confirm if the following is possible.

A user comes into our app and we open Stripe for them to pay for their subscription. After they pay for their subscription and come back into the app and after a few days they want to see when their next subscription charge will be. When they get to this screen, will they see that?

wise void
#

Yes

wooden epoch
#

Ok, great. So somehow the Stripe window will show data exactly related to that user.

I'm asking how can Stripe now to which user to map the data if the user isn't created in the Stripe database?

wise void
#

It can't. You must give us a cus_xxx ID (customer) when you create the subscription, and that's who it is associated to. Whether that sub is for a 'friend' or themselves, we are agnostic to that

wooden epoch
#

So it would actually be best if we show the user all the subscriptions he has in the application (something like history) and then when he clicks on the subscription to take him to the stripe and the stripe then shows him everything related to that cus_xxx ID we sent?

wise void
#

You don't need to leverage the portal (the link you sent). It's just a prebuilt UI to allow customers to manage their subscriptions within your application/business. You can build all that yourself via the API and get the more granular control and UI you likely need, just comes with more overhead for you. It's about trade-offs

wise void
wooden epoch
#

I didn't think we should create our own portal, but we need to somehow show the user all the subscriptions they have in their application because as far as I understand, one cus_xxx ID is equal to one subscription?

wise void
wooden epoch
#

So we can arrange the logic so that when a user clicks on a subscription, for example cus_XX1 ID, we open a portal with data from only that subscription, and if they click on a subscription, for example cus_XX2 ID, we open one from the other. Did I understand correctly?

#

Or will I always send you the same cus_XXX ID for the same user and you will show all subscriptions in the portal?

#

Thanks for having nerves for me 😄

wise void
#

I don't know enough about your business concept (friends, etc) but how you map that in Stripe is important. Does the 'friend' need to be a Stripe customer if they're not paying for anything? If not, then that seems like a detail that is irrelevant to Stripe and is only important to your application

wise void
next troutBOT
wooden epoch
#

Thanks

#

We can close this ticket