Electronic Credit Card Processing - Interact 7
- Heidi Adams
- Alex Ohde
Overview
The Electronic Credit Card feature (ECC) allows Interact to work with a credit/debit card terminal. The ECC software and hardware are offered as a kit. It will include the software and the hardware. The hardware must be purchased through AWS.
AWS has partnered with two (2) processing companies, Heartland and ValPay. Heartland offers a solution that works with our unattended kiosks. Each company is able to provide a single point of contact for the hardware, processor, and merchant services. AWS will not be able to provide support for other processors.
The only information passed from Interact to the terminal is total ticket charge and ticket number. The reader performs all operations related to reading the chip or mag stripe then contacting the credit/debit card processor directly via the internet.
When the merchant has successfully processed the credit/debit card transaction through the terminal, a limited amount of information related to the charge will be returned to Interact and stored in the database, some of this information is required to be printed on a ticket. Because the credit/debit card number and other personal information are never stored in the Interact database, Interact will never need to be PCI DSS compliant (Payment Card Industry Data Security Standard). Scale operators and scale computers are isolated from this requirement.
How it works
A hardware device is used to read the credit/debit card. Interact is programmed to work with the UIC Bezel 8, PAX A35, and a number of Adyen models. Once the software is installed and the Device Port configured, it is ready to go.
Printed Tickets
Specific information is required to be printed on tickets. Keywords for each hardware device are available and can be found on the Electronic Credit Card Processing - Printed Ticket Requirements page.
Convenience Fee
The ECC feature can be configured to apply a processing convenience fee when transactions are paid for with a credit/debit card. It can also be configured to apply a tax to the fee.
To learn more, go to the Electronic Credit Card - Convenience Fee Setup page.
Troubleshooting Errors
- Electronic Credit Card - Verifone Reader Error Messages
- Electronic Credit Card - UIC Bezel 8 Reader Error Messages
- Electronic Credit Card - PAX Reader Error Messages
Error Logging
Interact creates a daily log file. It includes all activity related to Interact including electronic credit card logging. It is stored in the C:\Users\userlogin\AppData\Roaming\AWS\Interact\Logs
Under normal conditions, the log will contain the last communication related to the Success or Deny of a credit/debit card. It contains all of the data returned from the reader. The data may be necessary to troubleshoot communication issues between the reader and the processor.
PAX A35 Reader
- Electronic Credit Card Processing - PAX A35 Hardware Setup
- Electronic Credit Card - PAX Reader Transaction Processing
- Electronic Credit Card - PAX Reader Error Messages
- /wiki/spaces/I6/pages/2819325953
- Voiding Credit Card Transactions Processed with Heartland
UIC Bezel 8
- Electronic Credit Card Processing - UIC Bezel 8 Hardware Setup
- Electronic Credit Card - UIC Bezel 8 Transaction Processing
- Electronic Credit Card - UIC Bezel 8 Reader Error Messages
- /wiki/spaces/I6/pages/2819325953
- Voiding Credit Card Transactions Processed with Heartland
Verifone
- Electronic Credit Card Processing - Verifone Hardware Setup
- Electronic Credit Card - Verifone Reader Transaction Processing
- Electronic Credit Card - Verifone Reader Error Messages
- Voiding Credit Card Transactions Processed with ValPay
- Electronic Credit Card Processing - Valpay Portal Tutorial
Software Options
- Electronic Credit Card - Convenience Fee Setup
- Electronic Credit Card Processing - Printed Ticket Requirements
- Weigh Options - Default Cash Payment Type