#bachir-terminal-ttp
lime meadow
blazing stone
👋 happy to help
narrow kayak
hey
blazing stone
what integration are you using?
would you mind pointing out which guide from our docs are you following?
blazing stone
this is a guide of using Terminal with Connect https://stripe.com/docs/terminal/features/connect
narrow kayak
Ok so I just re-use the same location from my platform account, and register each connected account's reader to it using a different display name ?
Actually I just remember I tried to follow this documentation but I couldnt get ahold of the REGISTRATION_CODE of my local reader to be able to register the reader against Stripe in this step https://stripe.com/docs/terminal/features/connect#destination-locations
const reader = await stripe.terminal.readers.create({
registration_code: "{{READER_REGISTRATION_CODE}}",
label: "Alice's Reader",
location: '{{LOCATION_ID}}',
});
gaunt kettle
Hi there 👋 stepping in as my teammate needed to step away. What type of reader are you using for your flow?
gaunt kettle
Gotcha, the reader connection process varies based on the type of reader that is being used. I would suggest reviewing this guide for using Tap to Pay:
https://stripe.com/docs/terminal/payments/connect-reader?reader-type=tap-to-pay-on-iphone
narrow kayak
Indeed ! I know this documentation by heart tbh, but the issue here is that I want to display a different merchant name based on the connected account using the tap to pay. For that, you need to set the display_name on the location when creating it. Which I manage to do. Now, I want to fetch this location (created on the connected account, with its own display_name) from Stripe, but if I just call "listLocations" it lists the locations of my platform account, not the connected one. Hence all connected accounts have the same display_name : the one from my platform location. That's the issue I brought first, and hence I asked if it's possible to pass "StripeAccount" ID in the listLocations request to fetch the connected account's locations.
Now, as tarzan said, I should use documentation from the connected accounts #1068521682983194624 message, but as I stated here, #1068521682983194624 message, I can't with tap to pay on iPhone reader as I don't have a registration code, or at least don't know how to retrieve it. So I was asking if with tap to pay on iPhone, there is a way to retrieve this registration code so I can register the reader with the location with its own display_name
gaunt kettle
No, because Tap to Pay doesn't generate a registration code, the concept of a registration code is unique to our internet-enabled reader (WisePOS E).
narrow kayak
Alright ! so how can I retrieve the locations of the connected account using StripeTerminal iOS SDK (2.16.1) ?
Terminal.shared.listLocations does not accept the StripeAccount option that usually is used for connect API, so I'm stuck only retrieving locations of my platform account.
gaunt kettle
bachir-terminal-ttp
It sounds like you're working with a Direct Charges flow since you're talking about setting up objects directly on the Connected Accounts, so I believe the approach you're looking for is to create your Connection Tokens using the StripeAccount parameter so those tokens are generated to grant access to the Connected Account:
https://stripe.com/docs/terminal/features/connect#direct-connection-tokens
narrow kayak
We actually use Destination Charges for our Connected accounts
I guess I just maybe take a step back and re-phrase my issue : How do I display a different merchant name on the tap to pay on iPhone screen for each of my connected account (custom, using destination charges, iOS app) ?
nvm I think I found a solution : passing merchantDisplayName to LocalMobileConnectionConfiguration
It seems for this case, it's not controllable from the Location object, but this will do
gaunt kettle
The only field from the API side that I think might influence this flow, is the on_behalf_of parameter on the associated Payment Intent:
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-on_behalf_of
Typically that field causes the Connected Account's details to be shown, rather than the Platform's, on features like Invoices.
narrow kayak
Indeed I use the onBehalfOf field, but it seems that it is not enough.
If I have a feedback on this, I think it should be more explicit that this documentation does not apply for tap to pay, and offer a way around if you think tap to pay on iPhone will become more and more an industry standard for accepting in-person payments. https://stripe.com/docs/terminal/features/connect
In any case, thanks for your help, have a great day 👋
gaunt kettle
Thank you for that feedback, hope you have a great day as well!