I'm very familiar with authorize.net CNP accounts and their apis. However I'm working on a new web app that needs to handle Card Present transactions, and have very little experience on this side. I've done a lot of searching for answers to my questions and my next step is to ask them here.
1) Our web app is mainly used at a sales desk through a web browser on a desktop computer, specifically for paying Invoices generated through our web app. Does reading track data from a card swipe into our opened browser app and sending that to the auth.net API fullfill Card Present requirements?
2) If the answer to #1 is no, how would I go about integrating the data from a Card Present swipe transaction with the Invoice data of our Web App?
3) Is there a sandbox for Card Present accounts, and how do I go about getting one?
Most Authorize.Net accounts will support either Card Not Present (CNP) or Card Present (CP) transactions.
For accepting in-person payments, we suggest using our in-person SDK which is available for mobile devices and Windows.
Sandbox accounts also support in-person payments using the SDK, although you're need to obtain a special device to test EMV transactions in the sandbox. Check the SDK documentation for details.
So I've checked out the in-person SDK and I guess the only way that would work for our web app is if we built a mobile version of it so our users could use it with a mobile device. However, I'm looking for the same functionality through a web browser on a desktop. That's where I'm having the disconnect. It is even possible?
Can VPOS integrate with my web app? How would I associate the data in the VPOS with the Invoices in my web app?
That's essentially the answer I'm trying to get to. How do I take Card Present data and put it into my web app? That's all I'm trying to figure out.
Also, is there a test or example version of the VPOS that I can play with? Having access to play with it may answer some more of my questions about VPOS.
Inorder to connect and get the reader data for CP transaction from Web Browser you need to create a browser extension which can interact with underlying native application.
You can make use of Chrome's Native messaging technique to interact with a native application.
You can create a native app which leverages Inperson Windows SDK support for quick chip transaction.
Browser can then send a message/command to extension and the extension can then take this message forward to the underlying app using Native messaging technique and vice versa.
So basically you need to have a browser extension which will be communication channel between the browser and underlying native application to process CP transactions with devices.
Whoa hold on there. Your questions and comments raise some flags. I suggest reading this for background:
Great thank you, this is a lot of the info I was looking for.
Knowing all this now, do you have a suggestion on how I can accomplish what I'm trying to do without needing to get my app PA-DSS certified?
Basically I need two key things
1) Credit card swipe
2) The ability to get the resulting transaction data into my app, as immediate as possible.