Need recommendation

[Stramels]

We are new to CC processing and Authorized.Net.  We have a client who asked us to write an application that will be used on a Kiosk type unit with a touchscreen, magnetic card reader, No keyboard or mouse.  It is a Winforms app written in VB.NET 2010.  The user will selected the items they would like to pay for with their Debit/CC, swipe their card and the application will need to go charge the card.  There is no place for a signature to be captured.

I have a couple questions:

1. Since the user has the card in hand, we signed up for a Card Present test account.  Is this correct account type?
2. Which API would be the best solution for our situation?
3. In a post on this Community Site, I was a bit confused by one post where the people said SSL was needed but others said SSL was not needed for desktop (non-web) applications.  Will we be required to use SSL to communicate with Authorize.Net?
4. When the correct API is chosen, we will look at the sample code.  Does anyone know if there is sample code that show how to process a card from a desktop (non-web) application?

Thanks, in advance, for your assistance!

[RaynorC1emen7 · Accepted solution]

1. Yes, Card Present test acount.

2.A version of AIM http://developer.authorize.net/api/cardpresent/

3.SSL not need on the client since it is a windows app. Yes you will use HTTPS to communicate with authorize.net, it the only way.

4.A website app and desktop is about the same, so download the AIM sample code and copy/paste the code and edit it to cardpresent spec.