<?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 Authorize.net Gateway Errors without Message in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Gateway-Errors-without-Message/m-p/68760#M41913</link>
    <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Two of my sites are having this issue. Authorize.net support is saying it's a Magento problem. I haven't patched or changed any code this week. Anyone out there seeing this in the wild?&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;UPDATE 1&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;A users on the M1 support forum posted a temporary fix. I applied the change and it worked.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;UPDATE 2&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;My host hinted that Authorize.net reverted the change. I substituted the multiple char delimiter and it is back to working as normal. Authorize.net's response has been atrocious, I'm going to be digging into bolt's checkout.&lt;/P&gt;</description>
    <pubDate>Fri, 16 Aug 2019 06:59:28 GMT</pubDate>
    <dc:creator>satna2</dc:creator>
    <dc:date>2019-08-16T06:59:28Z</dc:date>
    <item>
      <title>Authorize.net Gateway Errors without Message</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Gateway-Errors-without-Message/m-p/68760#M41913</link>
      <description>&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;Two of my sites are having this issue. Authorize.net support is saying it's a Magento problem. I haven't patched or changed any code this week. Anyone out there seeing this in the wild?&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;UPDATE 1&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;A users on the M1 support forum posted a temporary fix. I applied the change and it worked.&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;UPDATE 2&lt;/P&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;My host hinted that Authorize.net reverted the change. I substituted the multiple char delimiter and it is back to working as normal. Authorize.net's response has been atrocious, I'm going to be digging into bolt's checkout.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Aug 2019 06:59:28 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Authorize-net-Gateway-Errors-without-Message/m-p/68760#M41913</guid>
      <dc:creator>satna2</dc:creator>
      <dc:date>2019-08-16T06:59:28Z</dc:date>
    </item>
  </channel>
</rss>

