#doppio_api
1 messages Β· Page 1 of 1 (latest)
π Welcome to your new thread!
β²οΈ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
β±οΈ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
π This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1438282578116477138
π Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there
Feel free to drop the screenshot but pretty sure that is Dashboard-only and can't be done via the API.
You are better off setting metadata on the Reader
And then you can check that metadata
This is the popup
Oh I see, you literally need to activate Terminal as a product
Yeah you can't do that for your user -- they have to log in and do that.
This is the only thing separating me from viewing the Terminal resources on the connected account, as far as i understood "merchant_tags" is like a feature flag that says which features are enabled for a user
Hmm yeah I'm still not really sure what you are referring to for merchant_tags... that isn't a proprety on the Reader object: https://docs.stripe.com/api/terminal/readers/object?api-version=2025-10-29.preview&rds=1
Of note... we aren't intimately familiar with the Dashboard as we just focus on the API.
That's what i was afraid of. That connected account does not have dashboard access - intentionally. What could be a strategy so we - as a platform - still have visibility on this? I am able to create Terminal resources and everything via API, even if the user doesn't "activate" Terminal via the dashboard
merchant_tags seems to be an API endpoint strictly related to the dashboard. Full endpoint is https://dashboard.stripe.com/ajax/legacy_graphql/merchant_tags if that can help
Right but what are you actually setting? Can you screenshot what you are doing to hit that endpoint?
Pressing the "Inizia" button in the screenshot
I assume you are doing this on your own account and then want to do it on your Connected Accounts, no?
Noticed here i didn't reply to your "Hi", sorry for that, was busiy censoring the screenshot π , hi to you too!
lol all good
The screenshot i posted is while clicking the button while impersonating the connected account
Going to the Terminal product from the sidebar
Okay, and what are you really trying to do?
Like let's say that error didn't occur
What are you trying to do in the Connected Account's Dashboard?
Viewing the Terminal dashboard on the connected account to see connected Readers, created Locations on the connected account etc
Oh you just want to view their Readers and stuff, you aren't actually trying to take an action
Just to be clear, this dashboard
Yes exactly, stuff i can already see from the API, just to have a visual access that would be much more convenient while implementing Terminal
The issue is just that i can't pass that activation popup
Gotcha yeah when working with Connect it is intended that you would mostly use the API here.
I don't think there is any way past the popup currently without your user logging in and activating Terminal. Best I can do right now is to put in a feature request to see if we can bypass this in the future if it is the platform attempting to view the Connected Account's Terminal page.
What's really confusing me is that i can see basically everything else on the connected accounts like payments, Radar etc, it's just Terminal that seems to be passing that popup
Yeah Terminal has a specific acceptance required to use the product.
Clear, the thing that's weird is that even if the user does not "explicitly accept" the use of Terminal i can still bind readers, order them and stuff
So it just seems to be a dashboard visualization issue
Right now you as the platform are controlling things and you have accepted that. The popup is intended for if the Connected Account user wants to use Terminal directly (without your platform facilitating).
That said, overall I agree this isn't the cleanest state here
It feels weird that this would be blocking you
Yes it's a bit weird that i can do basically everything via API and not seeing anything via the dashboard π
Is there a possibility to maybe report this and see if this can be looked into?
Yeah I can submit a ticket internally but can't give you any sort of guarantee for timeline here.
That still would be something good i think, it seems to be a bit inconsistent as it is right now
Is there a way to maybe be in the loop of the ticket and be pinged if this get fixed or at least looked into?
You can write into our Support team via https://support.stripe.com/contact/login if you want to be kept up to date.
I've already contacted support regarding this matter, done 2 phone calls and it seems that they still could not understand the issue. I felt like trying to ask on discord just for a second opinion and it seems like you understood what the issue is
Maybe can i refer to the discord conversation on the support ticket or something like that?
One min
Okay actually I can have a case created for you so that the ticket can be linked. Then our Support team will keep you updated based on the ticket.
Hello @visual imp, we have sent you a direct message, please check it at https://discord.com/channels/@me/1438287440526704680
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.