#csk22_api

1 messages · Page 1 of 1 (latest)

brisk viperBOT
#

👋 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/1281629562190430261

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

marsh root
#

Hello

#

Yes threads are closed after a period of inactivity

#

The expectation is that this is a live chat

#

Now as stated in the other thread, what you want is not possible.

#

It is required that all objects live under the same account

honest barn
#

hello

#

sorry about that

marsh root
#

It sounds like what you want to be doing here is just using your platform account and then you can transfer funds to your different Connected Accounts

honest barn
#

I wasn't aware that was the expectation, I've been on a Teams call - my bad

marsh root
#

All good

#

Just know that threads will close if you go afk and you'll need to start a new one

honest barn
#

all good, I'll pay more attention 🙂

#

so we already have an Android app and an iOS app that have BBPOS WisePad 3 and TTP / TTPOI. On those we dynamically generate a connection token based on the connected account and generate a location if they don't already have one. With the S700 apps on devices implementation, the device is manually registered to a location in the dashboard. I do this in the 'manage deployment groups' tab and in there I am unable to see any locations from the connected account, only the the locations created on the platform account for the connected accounts. If I choose one of these and then generate a connection token using the connected account's ID, the app fails to connect to the reader. I raised this via support and they said:

"Our internal team has taken a look into this with req_Qfwy72FuBRdtL1 provided.

The app discover request is made using account acct_1FCsKZEzGMAqDSOH. The reader with serial STR70Z1C410000267, tmr_FspcRAH3b2CooQ, is registered to acct_1EtC8PIoZDVxPDhe.

Please note that the reader must be registered to the same account that the app is using. "

#

when I did some testing I tried deleting the connected account's ID from the account header and it connects successfully but payment fails. It does the same if I enter the platform account ID in the account header when generating the connection token. I have no idea why it will not find the reader if I use the connected account ID in the header

marsh root
#

Because the Reader doesn't exist on the Connected Account

#

You have two options -- you do everything on the platform or everything on each Connected Account

#

Just like with the WisePad and TTP integrations

#

Same idea

honest barn
#

okay so this location

marsh root
#

Yep that exists on your platform. So you would create Charges on your platform as well here

#

Let's pause for a second though

#

Tell me more about what is different here from your previous Terminal integration?

honest barn
#

in our existing iOS and Android apps we automatically generate the connection token via our back end API based on the connected account ID and take our application fee using direct charges. With this app it is installed through the dashboard and the S700 is manually registered to a location on the dashboard. I assume that I need to publish the app on our platform account because all of the connected accounts are connected on there. When I go to the manage deployment groups tab, I see 'GiveTap (platform account)' and then a list of connected account locations underneath. Logically I thought I select one of those for the connected account

marsh root
#

Okay one sec

honest barn
#

it's not very clear, it just says 'GiveTap Test' but I think that's a location for my connected account. However, when I select this location the deploy group shows 'acct_1EtC8PIoZDVxPDhe' (platform account ID) under the 'Account' header. If I install this app on the devkit and try and connect using my connected account ID (acct_1FCsKZEzGMAqDSOH), it fails to connect. Your support team kept telling me that it's failing because the header doesn't match the location that it's registered to but I'm completely at a loss

vast hedge
honest barn
#

please could you expand on that a bit more. My connected account is only linked to one platform account and it's the one my app is deployed to. It was connected via Oauth using the standard Stripe integration

vast hedge
honest barn
#

so we may be getting to the crux of the issue

#

in my deploy group I have 'GiveTap (platform account)'. beneath it area locations that our back end API has created for each of our connected accounts. Our iOS and Android apps will connect using these locations, but if I select one of these for the S700 it labels them with our platform account ID and fails to find them

vast hedge
#

eg, in my test account:

controls.png
honest barn
#

okay, let me check

vast hedge
honest barn
#

but the UI doesn't allow me to select locations that are created directly on the connected account

#

I've created creating one directly on the connected account and then searched for it on the platform account and cannot see it in the UI

vast hedge
#

I've created creating one directly on the connected account
how did you do that?

#

It might be necessary to create it via your platform, using connect headers

honest barn
#

so I guess I need to enable platform controls, though I'm not entirely sure how to do that. I thought it would just be managed via the Oauth connection process which is part of our sign up flow. We use the default Stripe setup

honest barn
vast hedge
vast hedge
honest barn
honest barn
brisk viperBOT
vast hedge
#

I'd also suggest creating a test connected account via the api that gives you application controller, and repeating your tests using that to see if it changes the outcome

#

But in terms of expected Dashboard behaviour for device apps for these connected accounts, this is something I'd suggest working with your terminal apps experts on via support: https://support.stripe.com/contact

Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

honest barn
#

is there a way to retrospectively enable platform controls? As I say we have around 400 or so connected accounts and I can't go through the process of getting them to unlink/relink

#

I feel like it's a relatively new feature and came out after we built the integration

vast hedge
#

I believe you have a contact you're working with directly at Stripe, and I would recommend you speak to them about this and options for the existing connected accounts.