#shahzaib-haider_docs
outer narwhalBOT
👋 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/1397132197521260624
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
torpid glacier
You can reconnect to a known reader automatically by your integration, have you had the chance to check this ?
https://docs.stripe.com/terminal/payments/connect-reader?terminal-sdk-platform=android&reader-type=internet#automatic-reconnection
deep cave
But what about connection token generation, will I have to create new token everything I want to connect with reader or I can use previously generated token until it expires (In my terminal I have many connected account, when user select a account I have to connect reader to that account)
torpid glacier
No, you don't need to generate a connection token for a known device (that already has been connected to)
deep cave
In my terminal I have many connected account, when user select new connected account I have to disconnect from old connected account and connect to new connected account, So, in that case I can't used already reedem token ?
torpid glacier
Ah Multiple connected account (users) that use the same Terminal App 🤔 ?
deep cave
Yes, that is the problem in our app we have an organization which can have many connected account as payment categories, when donating in terminal app user can chose which payment category(connected account) he want to donate to. So, in that scenario, for switching reader for that connected account is taking alot seconds as it has to disconnect, register a reader with connected account, discover reader, and connect to reader.
We want to somehow optimize that process, so delay can be minimize
outer narwhalBOT
torpid glacier
when donating in terminal app user can chose which payment category(connected account) he want to donate to
But in this case, you should make destination charges and not Direct Charges
With Destination charges, you don't need to disconnect the Connected Account and reconnect at each payment/donation
deep cave
But currently our model is working with direct charges, is there a way for optimization for direct charges
queen rivet
👋 taking over for my colleague. Let me catch up.
deep cave
Ok
queen rivet
you can connect the same reader to multiple connect accounts
like what is the use case anyway?
is the store where the terminal will be would sell products given to you by multiple merchants?
deep cave
like what is the use case anyway?
Usecase is we have an organization(an entity which receive donations/payments) which can have many connected account as payment categories, when donating in terminal app user can chose which payment category(connected account) he want to donate to
deep cave
is the store where the terminal will be would sell products given to you by mult...
Like imagine a non-profit organization collecting donation, but have payment categories like "Children Eduction Fund" and "Free Food For Needy" both have seperate connected account.
User can choose to donate to which he want, and money should go to that connected account for managing purposes.
queen rivet
I really don't think you can register a terminal to multiple accounts. Why not just use multiple terminals
each one is connected to its own Connected accounts
I know it's a hack but I don't see any other simple way to overcome this limitation
even with https://docs.stripe.com/terminal/features/connect#direct-platform:~:text=Contact us if,a single platform. I don't think it's possible but you can try and at least you'll get a direct answer from the terminal team
deep cave
We can't basically we have kiosk app, that we run on organization location, payment categories is chosen by user at run time, so, having different terminal or we can say card reader in our sense will be useless
queen rivet
I agree. please visit the link I sent you and click on Contact us.
explain your use-case and see if that beta can offer you what you're expecting
in all cases, you would get a validation on whether this is possible or not with our SDK
actually it does. based on the docs
This allows a single reader managed by the platform to process payments for multiple different connected accounts. The connected account is responsible for the cost of Stripe fees, refunds, and chargebacks.
this is a 100% what you're looking for
deep cave
Can you guide me on that
queen rivet
you need to click on contact us in the link I shared above
deep cave
I don't see contact us button
queen rivet
and send an email to the Stripe Terminal beta team to gain access to this feature
Platform owns readers
deep cave
Ok, Now I can see