<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Changes to Supported Characters - Jan 22, 2019 in News and Announcements</title>
    <link>https://community.developer.cybersource.com/t5/News-and-Announcements/Changes-to-Supported-Characters-Jan-22-2019/m-p/65435#M218</link>
    <description>&lt;DIV&gt;&lt;SPAN&gt;Update 2 - 1/18/2019&amp;nbsp; Changes are now live in sandbox and will go live in production on Tuesday, January 22, 2019.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Update - 1/11/2019 This change postponed.&amp;nbsp; New date TBD.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Dear Authorize.Net Merchant:&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;As part of ongoing security improvements, we're making changes on &lt;/SPAN&gt;&lt;STRONG&gt;January 10, 2019 &lt;/STRONG&gt;&lt;SPAN&gt;that may affect your gateway account. After January 10, certain characters will be replaced with spaces if sent to the gateway.&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Authorize.Net is changing how it handles some character data included in transactions submitted to our systems. Starting &lt;/SPAN&gt;&lt;STRONG&gt;January 10, 2019&lt;/STRONG&gt;&lt;SPAN&gt;, 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.&amp;nbsp;This includes URL and HTML encoding of the ‘&amp;lt;’ and ‘&amp;gt;’ characters, and non-printable Unicode characters.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Invalid Character Inputs&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;TABLE width="0"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;&lt;STRONG&gt;Char Representation&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;&lt;STRONG&gt;ASCII Value(s)&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;&amp;gt;&amp;nbsp;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;62&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;&amp;lt;&amp;nbsp;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;60&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;Non-printable characters&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;0 – 31&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;SPAN&gt;For example, if you submit a transaction to Authorize.Net with the Description field populated with &lt;/SPAN&gt;&lt;STRONG&gt;“Chocolate Chip Cookie [&amp;lt;medium&amp;gt;]”&lt;/STRONG&gt;&lt;SPAN&gt;, the Description data we will send to the back-end processor and save in our databases will be &lt;/SPAN&gt;&lt;STRONG&gt;“Chocolate Chip Cookie [ medium ]”&lt;/STRONG&gt;&lt;SPAN&gt;. Note the removed ‘&amp;lt;’ and ‘&amp;gt;’ characters.&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;What Steps Should You Take?&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;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 from Authorize.Net. &lt;/SPAN&gt;&lt;STRONG&gt;If your systems rely on these characters being sent back, then you must remove this dependency before January 10, 2019.&amp;nbsp;&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Additional information resources&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;If you have any questions, please contact Customer Support at 877.447.3938 or go to the &lt;/SPAN&gt;&lt;A href="https://support.authorize.net" target="_blank" data-targettype="webpage"&gt;Authorize.Net Support Center&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Fri, 18 Jan 2019 17:56:44 GMT</pubDate>
    <dc:creator>RichardH</dc:creator>
    <dc:date>2019-01-18T17:56:44Z</dc:date>
    <item>
      <title>Changes to Supported Characters - Jan 22, 2019</title>
      <link>https://community.developer.cybersource.com/t5/News-and-Announcements/Changes-to-Supported-Characters-Jan-22-2019/m-p/65435#M218</link>
      <description>&lt;DIV&gt;&lt;SPAN&gt;Update 2 - 1/18/2019&amp;nbsp; Changes are now live in sandbox and will go live in production on Tuesday, January 22, 2019.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Update - 1/11/2019 This change postponed.&amp;nbsp; New date TBD.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Dear Authorize.Net Merchant:&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;As part of ongoing security improvements, we're making changes on &lt;/SPAN&gt;&lt;STRONG&gt;January 10, 2019 &lt;/STRONG&gt;&lt;SPAN&gt;that may affect your gateway account. After January 10, certain characters will be replaced with spaces if sent to the gateway.&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;Authorize.Net is changing how it handles some character data included in transactions submitted to our systems. Starting &lt;/SPAN&gt;&lt;STRONG&gt;January 10, 2019&lt;/STRONG&gt;&lt;SPAN&gt;, 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.&amp;nbsp;This includes URL and HTML encoding of the ‘&amp;lt;’ and ‘&amp;gt;’ characters, and non-printable Unicode characters.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Invalid Character Inputs&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;
&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;TABLE width="0"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;&lt;STRONG&gt;Char Representation&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;&lt;STRONG&gt;ASCII Value(s)&lt;/STRONG&gt;&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;&amp;gt;&amp;nbsp;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;62&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;&amp;lt;&amp;nbsp;&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;60&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD width="227"&gt;
&lt;P&gt;Non-printable characters&lt;/P&gt;
&lt;/TD&gt;
&lt;TD width="90"&gt;
&lt;P&gt;0 – 31&lt;/P&gt;
&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;DIV&gt;&lt;SPAN&gt;For example, if you submit a transaction to Authorize.Net with the Description field populated with &lt;/SPAN&gt;&lt;STRONG&gt;“Chocolate Chip Cookie [&amp;lt;medium&amp;gt;]”&lt;/STRONG&gt;&lt;SPAN&gt;, the Description data we will send to the back-end processor and save in our databases will be &lt;/SPAN&gt;&lt;STRONG&gt;“Chocolate Chip Cookie [ medium ]”&lt;/STRONG&gt;&lt;SPAN&gt;. Note the removed ‘&amp;lt;’ and ‘&amp;gt;’ characters.&amp;nbsp;&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;What Steps Should You Take?&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;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 from Authorize.Net. &lt;/SPAN&gt;&lt;STRONG&gt;If your systems rely on these characters being sent back, then you must remove this dependency before January 10, 2019.&amp;nbsp;&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;STRONG&gt;Additional information resources&lt;/STRONG&gt;&lt;/DIV&gt;
&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV&gt;&lt;SPAN&gt;If you have any questions, please contact Customer Support at 877.447.3938 or go to the &lt;/SPAN&gt;&lt;A href="https://support.authorize.net" target="_blank" data-targettype="webpage"&gt;Authorize.Net Support Center&lt;/A&gt;&lt;SPAN&gt;.&lt;/SPAN&gt;&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 18 Jan 2019 17:56:44 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/News-and-Announcements/Changes-to-Supported-Characters-Jan-22-2019/m-p/65435#M218</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2019-01-18T17:56:44Z</dc:date>
    </item>
  </channel>
</rss>

