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.
