Hello, Authorize.net sent out this notification this week. Do we know if this will impact the Authorize.net plugin? DearAuthorize.NetMerchant: As part of ongoing security improvements, we're making changes onJanuary 10, 2019that may affect your gateway account. After January 10, certain characters will be replaced with spaces if sent to the gateway. Authorize.Netis changing how it handles some character data included in transactions submitted to our systems. StartingJanuary 10, 2019, transactions that contain any of the characters listed in the table below will be replaced with a space (‘ ‘) before saving the transactions in our systems and/or passing the transaction data to the back-end payment processor. If you later query our systems for data on these impacted transactions, we will send back the edited content. This includes URL and HTML encoding of the ‘<’ and ‘>’ characters, and non-printable Unicode characters. Invalid Character Inputs For example, if you submit a transaction toAuthorize.Netwith the Description field populated with“Chocolate Chip Cookie [<medium>]”, the Description data we will send to the back-end processor and save in our databases will be“Chocolate Chip Cookie [ medium ]”. Note the removed ‘<’ and ‘>’ characters. What Steps Should You Take? No change is required if your systems do not send any of the above characters in transaction data and rely on them in the response fromAuthorize.Net.If your systems rely on these characters being sent back, then you must remove this dependency before January 10, 2019. Additional information resources If you have any questions about this email, please contact Customer Support at 877.447.3938 or go to theAuthorize.Net Support Center. Thank you for your attention to this matter and for being anAuthorize.Netmerchant.
Do not worry about it. These changes do not affect aMember integration with authorize.net. Happy New Year!