#skammerens-datter_api

1 messages · Page 1 of 1 (latest)

bronze bladeBOT
#

👋 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/1257320340741427254

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

dry ivyBOT
boreal briar
#

Can you clarify your question? Not sure I understand. Are you trying to bill the connect account a subscription fee?

gilded perch
#

Yes exactly

#

besides them being connected accounts and thus charging their customers and receiving the payout, they are also going to be paying a monthly subscription. Instead of creating two seperate objects with identical information, we would like to simply reuse the connected account. I was reassured that would be possible. The main benefit, rather than just fetching the data and creating a new billing customer with the data from the connected account, would be that they share the same object in the stripe dashboard...

boreal briar
#

What type of connect account is this?

#

I was reassured that would be possible
Where exactly?

gilded perch
#

I spoke with support via email I think the previous month, I don't mean as in a promise, rather that it would be possible

boreal briar
#

As far as I know you can just create charges that bill a connect account (not subscriptions)

#

The right way to do this would be to create a customer on your platform account that you can bill via subscriptions

gilded perch
#

okay, just for clarification this is one of our connected account's id: acct_1OyZCCGf4P13Sche

#

or this one: acct_1OwJld2fJRIlx8Kc

#

i would assume they're identical in setup, since everything happens programatically

boreal briar
#

But those are 1-time charges not subscriptions

#

If you need to use Stripe Subscriptions, then you'll need to set up a Customer on your platform to bill

gilded perch
#

Okay, that is not an issue, I am merely trying to understand if possible to reuse the information from their connected account in some way to "tie" the customer and connected account together in some way?

boreal briar
#

if possible to reuse the information from their connected account in some way
what information?

#

You'll need to recollect payment method details if that's what you mean

#

You can't copy over a payment method

gilded perch
#

Name, email, address, business information, legal documents neccessary for Stripe, and the sorts

#

I understand that, also they as a connected account haven't provided a payment method, they just supply an IBAN for payouts

boreal briar
#

You can re-use the name, email address, and billing address

#

But there's no legal documents, etc required for a customer

#

They're not account holders

gilded perch
boreal briar
#

yeah exactly

gilded perch
#

so from that, would it be possible to do what I am inquiring?

boreal briar
#

yes that's the same as what I suggested above

gilded perch
boreal briar
#

No not a dumb question at all

#

Yes you can build a subscription like in the above link

#

The customer won't be linked to the connect account though in any way

#

It's just a way for your platform to bill them

gilded perch
#

Okay, so from my current use case I have an EMS SaaS, and my customer sends an invoice for a wedding to their customer with a prepayment. The connected account; my customer, gets the payout, which is the prepayment of the wedding. This is all working as it should. The next step is to introduce a subscription, so that we make money from our connected accounts besides the platform_fee. We want to create a settings page where they can manage their subscription, and we can charge them monthly a fee of using our EMS SaaS, whether they invoice or not. The main concern for us, is that we store the connected account id, e.g. acct_1OwJld2fJRIlx8Kc, and we are interested in knowing if we can use that id for checking the subscription status or if we would have to create a new database column to store the customer id, besides just the connected account id. Do we need to separate the two, or can our customer (being both the "connected account"" that receives payouts, and the "customer" paying the subscription fee to us) be tied to the same id, or would each customer have a connected account id and a customer id, for payouts and subscription respectively?

boreal briar
#

Yeah I recommend storing the account id to customer id mapping in your database

gilded perch
#

Okay, thank you for your time. We'll crack on 😄