#will_api

1 messages · Page 1 of 1 (latest)

limber sailBOT
#

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

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

sudden pike
#

I'll elaborate a bit - my site is built in bubble and users can subscribe on it to plans.
The parter site will be able to send me those user's info with their API, and they use stripe to collect payment.
I want the payment they collect to be sent to me (that's probably easy with connnect) but I also want to make sure that once a user pays them I'm able to set up the recurring payment on my backend

thin ibex
#

Hi there,
just to clarify, are they (the partner site) collecting the payment? And are they doing that for you and on their own account and you only should get a share?

sudden pike
#

They're gonna collect
1 - Payment on my behalf
2 - Payment for their services
Ideally both payments should be combined in one transaction

#

So I'd get a share of that transaction, but also be able to set up a recurring payment in my stripe account with the info collected by the partner

#

I'll give an example - they're a car dealership, I'm a warranty. they collect the fees for the booking and sign the user up to my warrenty, collect the first payment, I'm collecting recurring warranty revenue after that and handle the user in my system

limber sailBOT
gritty ravine
#

Hey! Taking over from my colleague here, give me some time to catch up

sudden pike
#

all good, thanks

limber sailBOT
gritty ravine
#

Actually could i clarify, for your use case, why did you consider the use of stripe connect?

sudden pike
#

That's what they suggested, I'm not married to using it

#

if there's a better way

gritty ravine
#

Hey, sorry for the wait!

sudden pike
#

let me see, one sec

#

so they can set me up as a connected account, and every time a user purchases, they create that user as a customer in the connected account, will subscriptions I have in my account show up in the subscriptions of the collected account or do they have to create the subscription?

#

and then when a user pays they'll show up in my account with a subscription ID?

gritty ravine
#

Apologies, I think i wasnt very clear

#

Do give me some time as i craft a reply

#
  1. You (the warranty provider) will be the Platform account
  2. The car dealership will be the Connected account
  3. Create a payment method for the Customer on the Platform account (the warranty provider): https://docs.stripe.com/connect/direct-charges-multiple-accounts#create-customer
  4. Clone the payment method to the connected account (the car dealership) to create a direct charge: https://docs.stripe.com/connect/direct-charges-multiple-accounts#clone-and-create-direct-charges
  5. During the first transaction, the direct charge would land into the connected account (the car dealership), and you will receive an application_fee for the warranty that you provide.
  6. During the first transaction, also set up a recurring Subscription for the warranty service that you provide
sudden pike
#

ok let me read up on this

#

Let me sure I track

  1. User is on dealership website, proceeds to payment
  2. Dealership website sends api to my website, I create a customer, clone it and post to the dealership's connected account.
  3. the dealership starts a checkout session (?)
  4. I can use the credit card collected in the session to set up a subscription on my backend?
gritty ravine
#

before i answer the questions above, could i confirm a few things:

  • The Customer will transact over the Car dealership's website
  • The branding that the Customer will see is the car dealership? And nothing about you guys (the warranty provider)
#

Apologies, Stripe connect is quite a big product on it's own and there are multiple considerations when it comes to it's setup

sudden pike
#

yes to both

gritty ravine
#

And the transactions that will take place will be:

  • One time transaction for the Car
  • Recurring transactions for warranty (e.g. a yearly warranty)
sudden pike
#

exactly

gritty ravine
#

Each charge type has different use cases

sudden pike
#

Yeah I understood the direct charge aspect

#

I just want to confirm - if I create a customer, clone it to their connected account - and they charge that customer, I'll be able to create a subscription for that user in my account without collecting their payment information again?

gritty ravine
#

yup, that would be the case

#

Could i check, in your use case, would you be the warranty provider for multiple car dealerships? or just this one?

sudden pike
#

got it, thanks, that makes my life easier
So they could theoretically not even charge the user at all on my behalf, I could charge them with just the cc info if they collect it on my behalf?

#

For now just one, but there will be more in the futurw

gritty ravine
#

So they could theoretically not even charge the user at all on my behalf, I could charge them with just the cc info if they collect it on my behalf?
what do you mean by theoretically not even charge the user on your behalf?

#

Do you mean that you can create a charge with the credit card PaymentMethod, with an amount that lands in the connected account (car dealership)?

sudden pike
#

I mean, they can charge the user whatever amount they want (regardless of my price), then that customer will have a paymentmethod connecte to their user, and I'll be able to charge + susbsribe to plan on my backend

#

makes sense?

#

Wait, wouldn't it have to be the other way arround? I'd be the connected account?
That way the dealership can create a paymentmethod and clone it to my connected account

gritty ravine
# sudden pike Wait, wouldn't it have to be the other way arround? I'd be the connected account...

The problem with this would be

Creating a charge with the cloned PaymentMethod consumes it, because it’s not attached to a customer. However, consuming the clone doesn’t affect the original PaymentMethod saved on your platform. You can’t reuse the consumed clone, but you can clone the platform PaymentMethod again and use the new clone for another charge.
https://docs.stripe.com/connect/direct-charges-multiple-accounts#create-confirm-payment-intent

#

So if you are the connected account, you can only consume the cloned payment method once