#ingridwong
1 messages ยท Page 1 of 1 (latest)
Hi ๐
For question 2: Yes this is possible. It will create the Financial Connect on the Connect Account.
For question 1: I'll need to dig a bit more
For question 2: Will it create the Financial Connection Account on the connected account if the Customer object we pass in is on the platform account? What we've found experimenting with Checkout is that, if we pass in a Customer in the platform account AND the stripe_account header for connected account, the Checkout Session and the subsequent PaymentMethod objects are all created in the platform account. So we're essentially just using the stripe_account: CONNECTED_ACCOUNT_ID header to apply branding on the Checkout Session. Is this accurate?
Can you share a request ID for one of these Checkout Sessions?
Here's how you can find a request ID: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Oh, this is not using the Stripe Header. It's using on_behalf_of. This will use the branding of the Connect Account but still create all the records on the Platform.
oh! we went through different iterations and I got confused. Sorry about that
so am I able to also pass in the on_behalf_of param when creating the FinancialConnection Session?
No, that's not an available parameter: https://stripe.com/docs/api/financial_connections/sessions/create
I see. But if I need to charge the PaymentMethods from my platform account, is there a way to clone them?
Basically I want the connected account's branding, but still charge these payment methods and have the funds flow into the platform's account balance
๐ stepping in as Snufkin needs to step away
Hi! No worries
Okay so sounds like currently you are creating Checkout Sessions on your Connected Accounts
So that you get their branding
And you are collecting ACH Debit accounts to do this
And you want to be able to check their balance?
yes
Also just to clarify, we're creating Checkout Sessions on our platform account, but just using on_behalf_of to apply their branding
Ah okay. You had said Stripe Account Header before which would insinuate a Direct Charge (not OBO)
Yeah I got things wrong, our current implementation is just using on_behalf_of and not the Stripe Account header
Okay so currently are you passing payment_method_options.us_bank_account.financial_connections.permissions when you create your Checkout Sessions? https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_method_options-us_bank_account-financial_connections-permissions
If you want to be able to check balances, then yes.
Okay, and that's because by passing in that param into the Stripe::Checkout::Sessions.create request, once the end user completes the authentication flow, will that create a PaymentMethod object AND a FinancialConnectionsAccount object? So I can use the latter object to retrieve its balance?
Yes that is my understanding. I actually haven't tested this flow specifically with Checkout before
I plan on doing so in just a minute since I want to know as well what this looks like
I'm testing this out right now!
Do I need to opt into the private beta before I can test this though?
Great, testing now
Sounds good, let me know!
I'm not seeing any financial connections account attached to this customer
is there anywhere else that I should be looking?
Can you provide me that Customer ID?
cus_MavMXT1SfU9GBy
Okay yeah I do see a financial connections account. So try retrieving that PaymentMethod ID
Oh perfect, I am able to see it in the PaymentMethod object as part of the payment_method.attached payload
Nice
Thank you very much for your help!