#savlundi
1 messages · Page 1 of 1 (latest)
Hello 👋
With card readers, do you mean terminal?
yes, exactly. We were originally told the BBPOS WisePos E readers are the only compatible ones with our application, but it seems like overkill for what we are doing
its not a storefront or something like that
and when they cost what they do, its a big expense
It depends on what features you're trying to build.
We have a comparison between the reader types and what ways they can be integrated to apps on this page
https://stripe.com/docs/terminal/payments/setup-reader#reader
https://stripe.com/docs/terminal/payments/setup-reader#sdk
is there a way i might be able to connect with someone and show them what our application does and get guidance?
TBH i am not the developer, I am product and have been digging into this for quite some time trying to figure out what is suitable before we lead our development team down that path
You might be able to talk to our support team via
https://support.stripe.com/?contact=true
From technical aspect the options mostly come down to;
What platform is your integration built on?
WisePOS E and S700 support all our SDKs (Web, Mobile, Server Driven)
Blutooth Readers are only supported by mobile SDKs
it is a web based application, there is currently not a mobile version if that helps
Gotcha. WisePOS E and S700 are the only two readers that support our web (JavaScript Based OR Server Driven) SDKs
got it, okay so we will need one of those devices if there is no mobile app
Correct
if we build out a mobile app at some point, we could integrate the other devices tho?
You can use bluetooth readers w/ mobile SDKs, yes but those still won't work with web based app.
WisePOS E can be used with web and mobile both. So if you do build a mobile app in future, you won't need to order new readers to support that integration
got it, okay. and as far as stripe connect goes, are we able to provide our clients with readers or would they have to purcahse their own readers? That is something we would want to be able to do for them since it is event management software
You can place an order and send it to them.
We also have a Hardware Order API in the works which would let you order readers using the API
https://stripe.com/docs/terminal/fleet/placing-orders#use-the-hardware-orders-api
so there is no way for us to, say, buy 10 readers, that we use for all events and give them to a client without it being ordered from an account for that specific event?
Not sure I follow.
You can order it as a platform and send it to them. They don't have to order it from their account.
Got it, like i could hand them any WisePOS reader and they would be able to connect it to their account?
Theoretically, yes.
From a technical aspect, the connection process depends on how you build your connect integration and what type of charges you create
https://stripe.com/docs/terminal/features/connect
Our thought process was on the admin side of the application, we have a terminal management page where all of our terminals are listed.
From there we would be able to assign the terminal to an event, and the owner of the connect account would be able to link 1 or more terminals to their account to be used during that event. It would also pull in the event location giving the terminal a geographical location stamp for when its being used.
Once an event is over, we would unlink the terminal from the event and then follow the same process for other events.
Right but the reader needs to be registered to the account that would act as a Merchant of Record for the payments.
So the registration would depend on what kind of charges your application ends up creating
(Direct or destination)
what is the difference between the two? Direct meaning to our parent account or destination meaning the connected account?
I'd recommend reading through our connect docs as they go very deep on the difference and more
https://stripe.com/docs/connect/charges