#CHIΞFMCCONNΞLL.ΞTH

1 messages · Page 1 of 1 (latest)

unborn bloomBOT
balmy rock
#

Hello! You're correct that Subscriptions require a Customer. Can you tell me which type of connected account you're using (Standard, Express, or Custom)?

azure quartz
#

standard account

#

but am i also correct in saying.. .if the sub is created in the dashboard, then i could either copy or pull the link with api and then use it on a subscription page like tier1 click here tier 2 click here etc

balmy rock
#

For Standard Accounts you should be using direct charges, which means the Subscription and the Customer should both exist on the connected account. You can create the Subscription and Customer on the connected account using a connect request: https://stripe.com/docs/connect/authentication

#

Not sure I understand your last question, can you provide more details?

azure quartz
#

sure. so when the subscription is created you can just take the subscription link that and send it to someone or connect it to a button that would then take them to stripe to complete the subscription (fill out the data and either log in or create an account if they dont already have one). this makes sense.. because in the dashboard you can also change the pricing and schedule and update it... and it will generate a link for any of these instances

#

like this

#

i see where you can integrate as well into your own page (ideally what we would like to do) but it is using ruby and some other stuff. we already do straight purchasing through api with fixed pricing. but just trying to figure out the easiest way in integrate subscriptions into our site without already having customer information (so if someone comes to the site for the first time they could also subscribe)

balmy rock
#

you can just take the subscription link that and send it to someone or connect it to a button that would then take them to stripe to complete the subscription
Not clear on this part; the screenshot shows you creating a Subscription from the Dashboard, yes, but where is the link coming from?

azure quartz
#

sorry your right.. it was in products

#

in products you can make reoccurring payments .. maybe this is the point of confusion for me

balmy rock
#

Am I correct in assuming that you as the platform want to take an application fee?

azure quartz
#

we as the platform would like to enable our authors/artists to be able to set up subscriptions for their products/services

balmy rock
#

If they're using Standard accounts they have the full Stripe Dashboard and can do all of that without being connected to or involving your platform.

#

Can you explain how your platform is involved? If you want to take fees?

azure quartz
#

we take fees for owning the platform where all of our artists can showcase and sell their items (digital downloads), we have all of that set up for individual one time purchases already and the apis are all set up for that. we were thinking we could also set up a dashboard of sorts where our artists can also set up their subscriptions through us and we could also provide a dashboard for them to see their active subscriptions, change them, update them, etc

#

and yes we would also take a fee for each subscription as well.

balmy rock
#

Okay, gotcha. So you're going to need to write code for this, you can't do it just from the Dashboard.

azure quartz
#

right. and thats where I thought I could do it through the api post method but each one requires a customer_id

balmy rock
#

If you want to use Stripe Checkout I think you're going to want to create Checkout Sessions for each unique order.

#

Payment Links are designed for when you want to sell the same thing to many different people over and over again, but it seems like you have a situation where you want to sell different things to each person each time.

azure quartz
#

yes the first case we have handled. you can checkout on our site and buy any of the live projects now through stripe checkout.

Indeed we want to set up subscriptions for our artists so they can have a sort of subscription feel like this

balmy rock
#

Okay. It sounds like you want to wire those buttons up to code that creates a Checkout Session for the option(s) selected.

azure quartz
#

yes, i think you are right. sounds like a checkout session would be what we need. would it create a new subscription for each checkout session?

#

if you set the mode to subscription it seems like it would just create a new one each time

balmy rock
#

Yes, that's correct.

azure quartz
#

crap. that is a lot of subscription.. so I guess it is safe to assume that each subscription is directly tied to a customer, rather than a subscription that serves multiple customers

#

hence why when trying to do an API call it requires a customer_id

balmy rock
#

Yes.

#

It wouldn't work to have a single Subscription for multiple Customers.

azure quartz
#

ok, that sounds good. now i understand a little more. i think there were some assumptions from my team and that led to wanting to use strip in a way it is not designed.

#

I appreciate your help in talking me through this

balmy rock
#

Always happy to help!

#

But yeah, the idea is that you create a Subscription to represent the recurring payments for a single Customer. The Subscription manages those recurring payments for that one person.