<?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 FDS Response Authorize.Net API in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/FDS-Response-Authorize-Net-API/m-p/67657#M41024</link>
    <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;We updated our AIM integration to &lt;A href="https://developer.authorize.net/api/reference/index.html" target="_blank" rel="noopener"&gt;Authorize.Net API&lt;/A&gt; a while back and with AIM, when a transaction was "FDS: Hold for Review" we used to get notified of this as I would get an error code of 253 and I could mark the transaction for special attention. Now this doesn't seem to be happening. I set a transaction limit in the Sandbox to Hold for Review transactions above a certain limit, tried a transaction above that and get a normal Code 1, "This transaction has been approved". I check in the Auth.net control panel and the transaction is indeed held for review however. My question is, is there any way to get notification that a transaction is held for review and hasn't actually been captured? I will post the JSON response below for this test transaction...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Beans&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;{&lt;BR /&gt;"transactionResponse": {&lt;BR /&gt;"responseCode": "1",&lt;BR /&gt;"authCode": "H4SE6Z",&lt;BR /&gt;"avsResultCode": "Y",&lt;BR /&gt;"cvvResultCode": "P",&lt;BR /&gt;"cavvResultCode": "2",&lt;BR /&gt;"transId": "60120886754",&lt;BR /&gt;"refTransID": "",&lt;BR /&gt;"transHash": "",&lt;BR /&gt;"testRequest": "0",&lt;BR /&gt;"accountNumber": "XXXX1111",&lt;BR /&gt;"accountType": "Visa",&lt;BR /&gt;"messages": [&lt;BR /&gt;{&lt;BR /&gt;"code": "1",&lt;BR /&gt;"description": "This transaction has been approved."&lt;BR /&gt;}&lt;BR /&gt;],&lt;BR /&gt;"transHashSha2": "B65CBA7EE66D62028CEA788D5E1CA182D0EA2CEF788D3B12DE10838D4B09B1416FDDA7D6A39D6DB6B21B4E48A185C5C11D9853860FA4E29345B9DAA9763CE7CC",&lt;BR /&gt;"SupplementalDataQualificationIndicator": 0&lt;BR /&gt;},&lt;BR /&gt;"messages": {&lt;BR /&gt;"resultCode": "Ok",&lt;BR /&gt;"message": [&lt;BR /&gt;{&lt;BR /&gt;"code": "I00001",&lt;BR /&gt;"text": "Successful."&lt;BR /&gt;}&lt;BR /&gt;]&lt;BR /&gt;}&lt;BR /&gt;}&lt;/P&gt;</description>
    <pubDate>Thu, 09 May 2019 09:57:41 GMT</pubDate>
    <dc:creator>ectdeveloper</dc:creator>
    <dc:date>2019-05-09T09:57:41Z</dc:date>
    <item>
      <title>FDS Response Authorize.Net API</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/FDS-Response-Authorize-Net-API/m-p/67657#M41024</link>
      <description>&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;We updated our AIM integration to &lt;A href="https://developer.authorize.net/api/reference/index.html" target="_blank" rel="noopener"&gt;Authorize.Net API&lt;/A&gt; a while back and with AIM, when a transaction was "FDS: Hold for Review" we used to get notified of this as I would get an error code of 253 and I could mark the transaction for special attention. Now this doesn't seem to be happening. I set a transaction limit in the Sandbox to Hold for Review transactions above a certain limit, tried a transaction above that and get a normal Code 1, "This transaction has been approved". I check in the Auth.net control panel and the transaction is indeed held for review however. My question is, is there any way to get notification that a transaction is held for review and hasn't actually been captured? I will post the JSON response below for this test transaction...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Many thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Beans&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;{&lt;BR /&gt;"transactionResponse": {&lt;BR /&gt;"responseCode": "1",&lt;BR /&gt;"authCode": "H4SE6Z",&lt;BR /&gt;"avsResultCode": "Y",&lt;BR /&gt;"cvvResultCode": "P",&lt;BR /&gt;"cavvResultCode": "2",&lt;BR /&gt;"transId": "60120886754",&lt;BR /&gt;"refTransID": "",&lt;BR /&gt;"transHash": "",&lt;BR /&gt;"testRequest": "0",&lt;BR /&gt;"accountNumber": "XXXX1111",&lt;BR /&gt;"accountType": "Visa",&lt;BR /&gt;"messages": [&lt;BR /&gt;{&lt;BR /&gt;"code": "1",&lt;BR /&gt;"description": "This transaction has been approved."&lt;BR /&gt;}&lt;BR /&gt;],&lt;BR /&gt;"transHashSha2": "B65CBA7EE66D62028CEA788D5E1CA182D0EA2CEF788D3B12DE10838D4B09B1416FDDA7D6A39D6DB6B21B4E48A185C5C11D9853860FA4E29345B9DAA9763CE7CC",&lt;BR /&gt;"SupplementalDataQualificationIndicator": 0&lt;BR /&gt;},&lt;BR /&gt;"messages": {&lt;BR /&gt;"resultCode": "Ok",&lt;BR /&gt;"message": [&lt;BR /&gt;{&lt;BR /&gt;"code": "I00001",&lt;BR /&gt;"text": "Successful."&lt;BR /&gt;}&lt;BR /&gt;]&lt;BR /&gt;}&lt;BR /&gt;}&lt;/P&gt;</description>
      <pubDate>Thu, 09 May 2019 09:57:41 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/FDS-Response-Authorize-Net-API/m-p/67657#M41024</guid>
      <dc:creator>ectdeveloper</dc:creator>
      <dc:date>2019-05-09T09:57:41Z</dc:date>
    </item>
    <item>
      <title>Re: FDS Response Authorize.Net API</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/FDS-Response-Authorize-Net-API/m-p/67688#M41047</link>
      <description>&lt;a href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/28579"&gt;@ectdeveloper&lt;/a&gt;&lt;BR /&gt;&lt;BR /&gt;You need webhooks. You can set it up in your interface if to have authnet ping your server when this happens.</description>
      <pubDate>Tue, 14 May 2019 08:05:57 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/FDS-Response-Authorize-Net-API/m-p/67688#M41047</guid>
      <dc:creator>Renaissance</dc:creator>
      <dc:date>2019-05-14T08:05:57Z</dc:date>
    </item>
  </channel>
</rss>

