cancel
Showing results for 
Search instead for 
Did you mean: 

Question regarding Authorize.net In-Person SDK for Windows

Hi everyone,

I have a question regarding Authorize.net's in-person SDK for Windows. Here is my use case:

- We are an online concert ticketing platform (think TicketMaster or Eventbrite)

- We currently have a web application (for online ticket sales), and a native iOS / Android mobile application (for in-person ticket sales).

- We are currently integrated with Authorize.net which allows for "card not present" transactions, but we currently don't have a solution in place to process "in-person" transactions through Authorize.net (which is why I'm reaching out here).

Additional notes:

- We explored integrating one of Authorize.net's card readers with our native iOS / Android mobile application to solve for this. The readers can be found here: https://partner.posportal.com/authorizenet/auth/. However we discovered that these readers only work with Authorize.net's mPOS & vPOS applications (we can't integrate them with our own native iOS / Android mobile application). So that doesn't help us very much if our clients are required to use both our mobile app and Authorize.net's mPOS / vPOS app in order to process in-person payments (we need a fully integrated solution).

- Exploring Authorize.net's in-person SDK here: https://developer.authorize.net/api/reference/features/in-person.html, the article says "The iOS and Android versions of the In-Person SDK are deprecated" which checks out. However there's another line of text that says "The Windows SDK is still fully supported," which is what I'm curious about.

Questions:

1. Would the Authorize.net in-person SDK for Windows be a possible solution for our use case here?

2. If so, would this only apply to native Windows applications (which we currently don't have) or could this be used with our web application running on a Windows device?

Thank you!

PromoTix
New Member
2 REPLIES 2

 

Integrating Authorize.net's In Person SDK for Windows into a web application to process in-person EMV transactions poses several challenges. The SDK is designed for native Windows applications in C#, making direct integration into a browser based environment difficult due to architectural differences and browser sandboxing, which prevents direct hardware access like card readers. A possible workaround is developing a native Windows middleware app to handle SDK interactions and communicate with the web app, though this adds complexity. Alternatively, switching to a payment processor that offers in person payment support via web friendly SDKs or APIs may be a more streamlined and scalable solution.

Justin_lima
New Member

Thank you Justin, that is the answer I was expecting but I wanted to be fully sure.

PromoTix
New Member

Type a product name