#chris.phandal-connect auth
high perch
You'd use the Stripe-Account header as documented in https://stripe.com/docs/connect/authentication
somber finch
You'd use the Stripe-Account header as documented in https://stripe.com/docs/con...
Hi thanks for the super quick reply, so by specifying the stripe-account header in the create location, will that work during the get request ??
i only want to show the locations created by their own connected acocunt ?
high perch
Correct. The Stripe-Account header makes the request as the connected account instead of the platform.
somber finch
ok apologies for my confusion here:
when we create the location, it is saving back to the platform account
high perch
Right, and if you use Stripe-Account on both the create and retrieve calls, it'll all take place on the connected account.
somber finch
aah ok, so we won't be able to view the locations themselves in the express dashboard only for platform account will see the addresses ?
sorry for the incompetence here :(, the documentation for locations only referred to standard and custom accounts, nothing about express
high perch
You may be looking for https://stripe.com/docs/terminal/payments/connect -- the difference is really Direct vs. Destination charges
somber finch
this is what i am struggling with: https://stripe.com/docs/terminal/creating-locations#creating-a-location-with-standard-connect
high perch
You want the Custom account version. Does that call not work with an Express account?
somber finch
no 😩 , the create api works and creates it onto the platform account but the get request returns blank
i suppose we could just specify the 'metadata' => [
'connected_account' => '{{CONNECTED_ACCOUNT_ID}}',
]
then create in app filter to only return locations where this is connected account is populated onto ?
high perch
Did you pass Stripe-Account with the same account id when creating the Location?