<?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 Re: accented characters in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/accented-characters/m-p/16556#M9331</link>
    <description>&lt;P&gt;No, the Authorize.Net system cannot currently handle Unicode characters.&amp;nbsp; You most likely wouldn't get an error submitting them, but they will most likely not be the same when they are returned.&amp;nbsp; We do accept accented characters, but they must be submitted in an extended western encoding.&lt;/P&gt;</description>
    <pubDate>Fri, 26 Aug 2011 22:34:43 GMT</pubDate>
    <dc:creator>Trevor</dc:creator>
    <dc:date>2011-08-26T22:34:43Z</dc:date>
    <item>
      <title>accented characters</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/accented-characters/m-p/16070#M9098</link>
      <description>&lt;P&gt;We have an increasingly global customer base. As such, more people from spansih and french speaking countries are submitting transactions (which very often have accented characters in names, addresses, cities, etc...). Authorize.net&amp;nbsp; chokes on these accented characters and throws an error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We use AIM, programming in vb.net, our website is asp.net.&lt;/P&gt;&lt;P&gt;We've searched all your documentation and previous posts. We see one discussion on this, but not much detail was discussed.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have analyzed the suggested code that authorize.net provides and we are using for the checkout process. The problem in handling accented characters looks to clearly be in the encoding for the streamwriter function. Current suggested code by authorize.net is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;FONT face="Consolas"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;myWriter = New StreamWriter(objRequest.GetRequestStream())&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="Consolas"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="Consolas"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face="Consolas"&gt;&lt;SPAN style="background-color: #ffffff;"&gt;It seems to us that we could easliy fix this problem so that accented characters would work by changing the encoding to unicode. So, simply replacing the above code with this insread:﻿&lt;BR /&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;myWriter = New StreamWriter(objRequest.GetRequestStream(),&lt;/SPAN&gt;&lt;SPAN style="font-family: Consolas,Courier,monospace; font-size: 13px; white-space: pre;"&gt;System.Text.Encoding.Unicode&lt;/SPAN&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;My question though, is whether the authorize.net platform will accept unicode encoding, or whether this will cause all sorts of problems? Would appreciate your thoughts/comments/insight.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN style="font-family: Consolas; background-color: #ffffff;"&gt;Thanks!&lt;BR /&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&lt;SPAN&gt;﻿&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 12 Aug 2011 15:02:07 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/accented-characters/m-p/16070#M9098</guid>
      <dc:creator>enewmark</dc:creator>
      <dc:date>2011-08-12T15:02:07Z</dc:date>
    </item>
    <item>
      <title>Re: accented characters</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/accented-characters/m-p/16556#M9331</link>
      <description>&lt;P&gt;No, the Authorize.Net system cannot currently handle Unicode characters.&amp;nbsp; You most likely wouldn't get an error submitting them, but they will most likely not be the same when they are returned.&amp;nbsp; We do accept accented characters, but they must be submitted in an extended western encoding.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2011 22:34:43 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/accented-characters/m-p/16556#M9331</guid>
      <dc:creator>Trevor</dc:creator>
      <dc:date>2011-08-26T22:34:43Z</dc:date>
    </item>
  </channel>
</rss>

