#silvpol-Terminal-location
undone belfry
lethal arrow
thanks
when creating ConnectionToken we are specifying Custom Account ID as per docs
RequestOptions.builder().setStripeAccount(<ACC_ID>).build()
Could we use our platform acc id instead but still make payments for given connect account
heady crane
@undone belfry I'll take that one
lethal arrow
i.e. override in PaymentIntent later?
heady crane
@lethal arrow if you use Custom accounts you should not be doing this. You should have all charges happen on the platform
https://stripe.com/docs/connect/destination-charges that's the right flow of funds
lethal arrow
this is for Terminal though
ashen mango
You can see the Terminal specific API calls here: https://stripe.com/docs/terminal/payments/connect#destination
lethal arrow
card present
heady crane
it's the same thing for Terminal, all through platform no change
lethal arrow
when I follow docs I specify custom acc id
and that causes issues for us
we have no use for locations and no interface for it
we need to use SDK 2.0 due to app and reader choice
so now stuck with locations
ashen mango
Yes, you need to use Locations with the 2.0. SDK
lethal arrow
locations are only working if created per account, locations at platform level not working
in this setup
ashen mango
If you're using Custom Connect, you should be creating Locations on the platform
And registering Readers on the platform
lethal arrow
that doesn't work though
locations in platform don't work for reader if custpm acc id specief in connection token
ashen mango
Your connection token shouldn't be Account ID specific.
That should happen on the platform as well
lethal arrow
but Stripe connect docs for terminal say to specify it
ashen mango
Which docs?
lethal arrow
ConnectionTokenCreateParams params =
ConnectionTokenCreateParams.builder()
.setLocation("{{LOCATION_ID}}"
)
.build();
RequestOptions requestOptions =
RequestOptions.builder()
.setStripeAccount("{{CONNECTED_ACCOUNT_ID}}"
)
.build();
ConnectionToken connectionToken = ConnectionToken.create(params, requestOptions);
ashen mango
That's for direct charges, which is what's used to collect payments with Standard Connect. But you're collecting payments with Custom Connect, right?
lethal arrow
yes, I think I now see what you mean
so all we really need is this?
ConnectionTokenCreateParams params =
ConnectionTokenCreateParams.builder()
.setLocation("{{LOCATION_ID}}"
)
.build();
ConnectionToken connectionToken = ConnectionToken.create(params);
ashen mango
Yep!
ashen mango
Yes, it'll work with that feature too
ashen mango
Everything is going to happen on the platform, and you'll Stripe where to put the flow of funds by specifying the Account in the PaymentIntent using the transfer_data[destination] parameter