Due to the new PCI / DSS rules, we are removing the ability for our desktop app to use the Card Present / AIM method. We have converted our application to use the SIM interface.
SIM works well, but there is 1 problem. It does not support swiped transactions. If I tell our customers that they cannot use their card swipes, they will scream. They have good reasons:
1. Swiped transactions are faster and more accurate
2. A non-swiped (card not present) transaction is charged about ½ percent more for the merchant discount rate.
What we are looking for is a way to pass information back and forth - like in the SIM interface. The only difference is that with the swiped transaction, there would be a field on the Authorize.net for that could accept a card swipe.
It would work like this:
1. The initial form gets submitted with the fingerprint in a post (same as now). However, there would be another variable that indicated that a card swipe will be used.
2. Authorize.net will send the information back to display the payment gateway hosted payment form
3. The merchant would swipe the card and click submit.
4. Authorize.net returns the receipt (same as it does now).
The transactions would be faster, more accurate and PCI compliant. And, there is not much programming to be done.
This is a matter of some importance. We have several hundred merchants as customers. This issue is enough to force us to use another payment gateway.
Is there any way that we can stay with Authorize.net?
Thanks in advance.
Bruce