#heka6
steel hazel
vital night
Hey there, when threads go inactive for a bit then they get closed. If you can summarize your use-case then I'd be happy to help.
plush hazel
hi
basically we are working with connect accounts, but also need to be able to bill servcies on the platform
so we need:
- to save customer and payment method on both platform and connect account
- process direct charge on connect account
- be able to bill subscriptions later on on platform for customers who subscribed
Note that customers subscribe to subscription during a purchase. The issue / fear I have, is that when doing destination charges we were specifying that the card could be used later off_session. Now that we want to do direct charges, I fear the subscriptions would trigger some extra 3DS on billing days while customers actually agreed to the subscription on_session.
that's why I sent the image above including the Setup Intent as suggested by toby
in order to adapt our previous destination charge + subscription flow to the direct charge constraint
we now have
vital night
Yep the above looks fine but you should just use setup_future_usage: off_session here as that can encompass both on session and off session (see: https://stripe.com/docs/api/payment_intents/create#create_payment_intent-setup_future_usage) since it sounds like it is ambiguous.
plush hazel
sure
but would that help for subscription billing?
because the payment intent is on the connect acount
vital night
Yes you want a PM to be set up for off_session if you are going to use Subscriptions
plush hazel
not on the platform where we bill the subscriptions
vital night
A SetupIntent sets a PM up for off_session by default unless you specify usage: on_session
vital night
Are you ever creating the Subscription first here?
Like you don't want to use a SetupIntent and then immediately create the Subscription
plush hazel
what do you mean by first?
vital night
You should just use the Subscription to set up the PM in that case
vital night
Yep
When you confirm a PaymentIntent associated with an Invoice from a Subscription creation that will set up a PM for off_session
plush hazel
what we want to avoid is 2 3DS in a row. because the customer has the products in their cart + a subscription. products are billed on the connect account, subscription will be 7 days later if they stay on as members. and this will be billed by the platform
vital night
Will the Connected Account ever be in a different country than your platform?
vital night
Gotcha
Okay so yeah the initial idea of SetupIntent on platform and then clone to Connected Account and create PaymentIntent there is fine
You can either create the SetupIntent separate or create a Subscription with a trial which will generate a SetupIntent as well
Up to you really
Overall, 3DS should only be request once
As we will carry over the exemption when you clone
But it is always possible that it is requested again for the PaymentIntent
You will want to be ready to handle that, but should be very rare.
plush hazel
ok thanks a lot
vital night
👍
plush hazel
🤯 our use case is a headache. I loved destination charges, but some merchants complain about not seeing proper payments attached to customers in their dashboards
so the only way we found was to do direct charges
but we now have these subscription related concerns
if you have an alternative for the connect dashboard to show payments attached to customer despite destination charges, I take it