• Authorize.net just sent out an e-mail (see copy below) about some changes to Supported Characters. Is this plugin being updated with the new Authorize.net security improvement?

    Also found this for reference: https://community.developer.authorize.net/t5/News-and-Announcements/Changes-to-Supported-Characters-on-January-10-2019/td-p/65435

    Dear Authorize.Net Merchant:

    As part of ongoing security improvements, we’re making changes on January 10, 2019 that may affect your gateway account. After January 10, certain characters will be replaced with spaces if sent to the gateway.

    Authorize.Net is changing how it handles some character data included in transactions submitted to our systems. Starting January 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

  • The topic ‘Security Improvements’ is closed to new replies.