In order to support card present transactions, the system needs to support a local pci dss compliant stripe reader. From what I understand, it needs to read the cvv1 number which is only encoded on the mag stripe. These transactions are less expensive to process as there is a lower rate of chargebacks since the customer actually had to present the card.
Basically, I think that there would need to be support for some encrypted link between the local system and the payment gateway on the server.
A related issue might be providing clean interfaces for a local (touch and/or bar code scanning) ui.
I gotcha. Ultimately this is a contrib issue in much the same way as the UberPOS was for Ubercart... some way to link a terminal to the checkout page or some other admin page. I'm not sure just dumping that data into checkout is what you'd want anyways.
Comments
Wouldn't that just require
Wouldn't that just require the CSR typing in the CC number on the payment terminal for the order? Not sure what else Commerce itself can do here...
A "card present" transaction has to be swiped.
In order to support card present transactions, the system needs to support a local pci dss compliant stripe reader. From what I understand, it needs to read the cvv1 number which is only encoded on the mag stripe. These transactions are less expensive to process as there is a lower rate of chargebacks since the customer actually had to present the card.
Basically, I think that there would need to be support for some encrypted link between the local system and the payment gateway on the server.
A related issue might be providing clean interfaces for a local (touch and/or bar code scanning) ui.
I gotcha. Ultimately this is
I gotcha. Ultimately this is a contrib issue in much the same way as the UberPOS was for Ubercart... some way to link a terminal to the checkout page or some other admin page. I'm not sure just dumping that data into checkout is what you'd want anyways.