<?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: Need Encrypt KEY for MSR in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Encrypt-KEY-for-MSR/m-p/50658#M26076</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18344"&gt;@upsaferuss&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In order to use an encrypted reader with Authorize.Net, we must generate the key and it must be injected into the device by the manufacturer or an authorized agent. &amp;nbsp;Some devices allow remote injection, but most currently require physical access to inject the key. &amp;nbsp;Authorize.Net does not perform key injection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A list of devices which currently support the Authorize.Net key are listed at&amp;nbsp;&lt;A href="http://authorizenet.posportal.com/" target="_blank"&gt;http://authorizenet.posportal.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you don't see the specific make/model of the device you want to use, please post this using our &lt;A href="https://community.developer.cybersource.com/t5/Ideas/idb-p/ideas" target="_blank"&gt;Ideas forum&lt;/A&gt;. This will allow others add their vote for support as well.&lt;BR /&gt;&lt;BR /&gt;Richard&lt;/P&gt;</description>
    <pubDate>Thu, 14 May 2015 17:18:31 GMT</pubDate>
    <dc:creator>RichardH</dc:creator>
    <dc:date>2015-05-14T17:18:31Z</dc:date>
    <item>
      <title>Need Encrypt KEY for MSR</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Encrypt-KEY-for-MSR/m-p/50657#M26075</link>
      <description>&lt;P&gt;What entity issues the encryption key that must be embedded in the read head of an MSR.&amp;nbsp; We use the ID TECH Secure Read head.&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 15:56:43 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Encrypt-KEY-for-MSR/m-p/50657#M26075</guid>
      <dc:creator>upsaferuss</dc:creator>
      <dc:date>2015-05-14T15:56:43Z</dc:date>
    </item>
    <item>
      <title>Re: Need Encrypt KEY for MSR</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Encrypt-KEY-for-MSR/m-p/50658#M26076</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18344"&gt;@upsaferuss&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In order to use an encrypted reader with Authorize.Net, we must generate the key and it must be injected into the device by the manufacturer or an authorized agent. &amp;nbsp;Some devices allow remote injection, but most currently require physical access to inject the key. &amp;nbsp;Authorize.Net does not perform key injection.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A list of devices which currently support the Authorize.Net key are listed at&amp;nbsp;&lt;A href="http://authorizenet.posportal.com/" target="_blank"&gt;http://authorizenet.posportal.com/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you don't see the specific make/model of the device you want to use, please post this using our &lt;A href="https://community.developer.cybersource.com/t5/Ideas/idb-p/ideas" target="_blank"&gt;Ideas forum&lt;/A&gt;. This will allow others add their vote for support as well.&lt;BR /&gt;&lt;BR /&gt;Richard&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2015 17:18:31 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Need-Encrypt-KEY-for-MSR/m-p/50658#M26076</guid>
      <dc:creator>RichardH</dc:creator>
      <dc:date>2015-05-14T17:18:31Z</dc:date>
    </item>
  </channel>
</rss>

