The Authorize.Net Developer Blog

Posts from Authorize.Net employees, community members and experts about integrating with the Authorize.Net Payment Gateway: sample code, tutorials, and problem-solving techniques, just to name a few.

Important Update Required for Users of EMV® Card Readers

by Administrator Administrator on ‎05-04-2018 01:20 PM (12,805 Views)

If you or one of your merchants is using the Authorize.Net Anywhere Commerce Walker C2X and/or the BBPOS Chipper™ 2X, via the Authorize.Net In-Person SDKs, you must update the EMV card reader to remove the expired 1152-bit key.

 

The 1152-bit key recently expired and it must be removed from the EMV card reader within six months. If no update occurs, and a chip card reader with an expired key requests authorization, the transaction will be declined. The 1152-bit key must be removed from EMV card readers no later than July 1, 2018.

 

Recommended Action

  • Update your In-Person SDK iOS, Android and Windows integration with the Firmware/Configuration Over-the-Air (OTA) remote update feature.

or

  • Utilize the In-Person SDKs sample applications in Net’s GitHub repositories.

 

Additional Option

 

Additional Resources

Visa: https://technologypartner.visa.com/download.aspx?id=34

 

EMV is a registered trademark or trademark of EMVCo LLC in the United States and other countries.

Comments
by craigomez
on ‎06-03-2018 03:47 PM

hello ,

thankyou for the heads up!

ill update my card!

BEST REGARDS

craig

by Campos369
on ‎06-25-2018 02:46 AM

Yes, for the foreseeable future, credit and debit cards will be issued with a chip on the front of the card and the familiar magnetic stripe on the back of the card so that chip cards can be backwards compatible with existing non-EMV capable devices. However, merchants may be liable for any counterfeit fraud if they don’t support chip transactions.