EVM credit card October deadline
On October 1, in the US, card present credit card transactions wherein the card has an embedded chip will shift credit card fraud liability from the banks and credit card providers to the merchant if the merchant does not process the card via the EVM technology. Liability can also go to the application developer.
My clients process payments through my web application face to face using a simple card swiper. Transactions are processed through authorize.net. However, authorize.net has not yet updated it's API for processing EVM cards. I have one client freaking out about the upcoming liability change, but there is not anything I can do until Authorize.net gets it's act together. Of course it will take me time and expense to revise my code to support the new cards.I will have to purchase a few EVM card readers for testing.
Is anyone else dealing with the same thing now?
I will be able to pass the expense of the code upgrade to my clients, but what annoys me is that authorize.net isn't ready, but I'm the one who take the heat from my clients for it.
