Can I send along the Stripe-Account header transparently for all API calls, including for my own account as well, @stripe, or do I need to implement a separate flow for direct customers versus connected account customers?
-
-
Replying to @dHeremans
Great question, David. If you're looking at your own account, you will be unable to use Stripe-Account for these API calls since this is intended for Connected accounts. You'd need to look at implementing a separate flow for this.
1 reply 0 retweets 0 likes -
Replying to @stripe
which is a pity to be honest - wouldn't it make sense if you could make that just more transparent and generic to your users? Now we have to make two implementations even though we only need one on our end ;-)
1 reply 0 retweets 0 likes -
Replying to @dHeremans @stripe
As in - we have multi tenant system in place, and basically I want the same flow whether we have a user pay our invoices, or an invoice of one of our tenants :)
1 reply 0 retweets 0 likes -
Replying to @dHeremans
Sorry to disappoint, but we greatly appreciate your feedback around this. We'll continue to take a look at your feedback.
1 reply 0 retweets 1 like -
Replying to @stripe
Not an issue. Rome wasn’t built in a day. Am I right that thebonly difference for these flows is the additional header and all the rest can work transparently?
1 reply 0 retweets 0 likes
Good question—not necessarily. When you're using your own account, you're not passing 'Stripe-Account', in turn also not passing 'application_fee' or 'transfer_data'.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.