topic Re: Card present vs not present for SaaS system in Integration and Testing

Card present vs not present for SaaS system

TwinPeaks — Fri, 16 Aug 2024 22:19:30 GMT

Hello,

The company I work for has a web based ERP system (written in PHP). We are currently linked with auth.net. We store the CC details in our software, then, to process the CC, we send to auth.net invoice details (invoice #, amount, details) and customer details (customer name, CC#, etc).

Currently, all charges are 'card not present.' We want to be able to process the as 'card present,' but I could not find how in the API. Can someone please link it for me? If you need more info, please let me know and I can speak with our developers (they do not speak English). Thank you.

Re: Card present vs not present for SaaS system

BashDang1 — Sun, 18 Aug 2024 15:50:35 GMT

To process credit card transactions as "card present" using the Authorize.Net API, you'll need to make some changes compared to how you currently process "card not present" transactions. "Card present" transactions typically involve in-person payments where the card is physically present, often requiring the use of additional hardware such as a card reader.

Here’s a general guide to help you get started:

1. Use the "Card Present" API

Authorize.Net offers a specific API for "Card Present" transactions. This is different from the standard "Card Not Present" API and is designed for use with point-of-sale (POS) systems.

API Documentation: You can find the relevant API documentation for "Card Present" transactions here (look for the "Card Present" section).

2. Transaction Key and Signature Key

For card present transactions, you’ll typically need a Transaction Key and Signature Key. These are required to authenticate your API requests.

3. Required Data

In "Card Present" transactions, additional data might be required:

Track Data: If you're using a magnetic stripe card reader, you'll need to pass track data.
EMV Data: If you're using a chip card, EMV data will be required.
Device Information: Information about the hardware device used for the transaction.

4. Testing and Certification

Authorize.Net may require that your system undergo certification to ensure compliance with their security standards for card present transactions.

5. Switching from "Card Not Present" to "Card Present"

Update your API calls to reflect the "Card Present" mode.
Adjust the data being sent to include details like track data or EMV data, depending on the card reader you are using.

6. Consultation with Developers

Since your developers may not speak English, consider having a translator or documentation in their language. They will need to implement the necessary changes in your system to handle the specific requirements for card present transactions.

7. Contact Authorize.Net Support

If you’re having trouble finding specific information or need additional assistance, contacting Authorize.Net support directly might be the most effective route. They can provide detailed guidance and any additional documentation you might need.

Re: Card present vs not present for SaaS system

TwinPeaks — Tue, 20 Aug 2024 05:21:25 GMT

@BashDang1The hyperlink doesn't work to the API. Can you link it again please. Thank you.

I know card present is for a situation with a physical terminal, however, I know other platforms can set all transactions to card present. Is that possible with auth.net without having the physical card present?

Re: Card present vs not present for SaaS system

TwinPeaks — Fri, 23 Aug 2024 00:15:34 GMT

Hi @BashDang1 , can you please provide the hyperlink. It doesn't work. Thank you.

Re: Card present vs not present for SaaS system

sharrul — Wed, 04 Sep 2024 04:21:07 GMT

Hello dear where is the hyperlink. I think it is not working