#ingrid-directcharges-clone

1 messages · Page 1 of 1 (latest)

calm glen
#

There are many ways to do this. Are your customers going to re-use those payment methods?

faint nova
#

Yes! We're thinking of using Stripe Checkout with mode: 'setup' to store the Payment Method on the Customer and re-use it

calm glen
#

So that customer will only ever pay that specific connected account? And you're using Standard accounts?

faint nova
#

Yes, with the caveat that we might eventually need to switch to Separate Charges and Transfers. But I've been told by Product to leave out this possibility and just assume the customer will only pay to that specific connected account.
I do want to ask how hard it will be to transition from Direct Charges to Separate Transfers

#

And yes, we're setting the connected accounts as Standard

calm glen
#

if you use Standard accounts you should never use anything other than Direct Charges

#

So mostly yes, just create the Checkout Session on that connected account in that case, no need to go through the platform

faint nova
#

Okay that makes sense.

#

I do want to follow up on the transition though: say we're on Standard + Direct Charges, but eventually want to switch to Separate Transfers. Does that mean we'll need to create new connected Accounts of *Custom/Express * type first for all our Standard connected accounts?

calm glen
#

yep

#

and re-collect all the information/details to verify their account

faint nova
#

Got it thank you!

faint nova
#

Sorry quick question on the Checkout Session create step:
So instead of using setup_intent_data.on_behalf_of param, I should just pass in the account id of the connected account:

Stripe::Checkout::Session.create({mode: 'setup',},
{stripe_account: '{{CONNECTED_ACCOUNT_ID}}'
)

This will apply the connected account's branding I assume?

#

What's the difference between the 2 approaches then?

vestal quail
#

on_behalf_of will create Destination charges (as opposed to Direct charges). Those are similar to Separate Charges & Transfers, except that you cannot use on_behalf_of to facilitate multi-party payments and the whole charge flow takes place almost instantaneously.

And yes, if you're using direct charges, it will apply the standard account's branding to Checkout

faint nova
#

Got it! So I should never use on_behalf_of for Direct Charges, and instead, should just pass in the additional header for stripe_account in any request?

#

Also, correct me if I'm wrong, but if I'm using Stripe Checkout Session with mode: setup, this will not create a charge (destination charge or not). So does it really matter if I pass in setup_intent_data.on_behalf_of or the stripe_account header?

vestal quail
vestal quail