<?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 First Partial Authorization Release in News and Announcements</title>
    <link>https://community.developer.cybersource.com/t5/News-and-Announcements/First-Partial-Authorization-Release/m-p/3838#M31</link>
    <description>&lt;P&gt;Hey everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On Tuesday, June 29th, we released support for partial authorization transactions as described in our &lt;A rel="nofollow" href="http://community.developer.authorize.net/t5/News-and-Announcements/New-MasterCard-Discover-Processing-Requirements/td-p/2634" target="_blank"&gt;previous post&lt;/A&gt; . With this release, Authorize.Net now supports these transactions on two processors, FDC Nashville and RBS WorldPay. This means that any merchant using those processors may now begin processing partial authorization transactions.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;It also means you can begin testing your own integrations using your test account. Yay! :smileyvery-happy:&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you’re looking for the information necessary to update your systems for partial authorization capabilities, well then, here you go:&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;AIM&lt;/STRONG&gt;&lt;BR /&gt;For the necessary information on what changes you will need to make if you integrate via Advanced Integration Method (AIM) please see the AIM guide at &lt;A rel="nofollow" href="http://www.authorize.net/support/AIM_guide.pdf" target="_blank"&gt;http://www.authorize.net/support/AIM_guide.pdf&lt;/A&gt; or review the updates at &lt;A rel="nofollow" href="http://www.authorize.net/support/AIM_apiupdates.pdf" target="_blank"&gt;http://www.authorize.net/support/AIM_apiupdates.pdf&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;SIM&lt;/STRONG&gt;&lt;BR /&gt;If you use the Server Integration Method (SIM), please review the updated SIM guide at &lt;A rel="nofollow" href="http://www.authorize.net/support/SIM_guide.pdf" target="_blank"&gt;http://www.authorize.net/support/SIM_guide.pdf&lt;/A&gt;.&amp;nbsp; Please note that the Relay Response field order has changed.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Additionally, you’ll see that all SIM Relay Response and Silent Post transaction responses will now include the card type and last four digits of the credit card number, regardless of whether or not the original transaction was enabled for partial authorizations.&amp;nbsp; This has been a long-awaited feature that we’re happy to be able to provide now. This information will be included in the following fields:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;Field Name&lt;/TD&gt;
&lt;TD&gt;Value&lt;/TD&gt;
&lt;TD&gt;Format&lt;/TD&gt;
&lt;TD&gt;Notes&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;x_account_number&lt;/TD&gt;
&lt;TD&gt;Last 4 digits of the card provided&lt;/TD&gt;
&lt;TD&gt;Alphanumeric (XXXX6835)&lt;/TD&gt;
&lt;TD&gt;This is a new field that is returned with all transactions.&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;x_card_type&lt;/TD&gt;
&lt;TD&gt;Visa, MasterCard, American Express, Discover, Diners Club, EnRoute, JCB&lt;/TD&gt;
&lt;TD&gt;Text&lt;/TD&gt;
&lt;TD&gt;This is a new field that is returned with all transactions.&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;STRONG&gt;Simple Checkout&lt;/STRONG&gt;&lt;BR /&gt;For anyone using Simple Checkout, simply log into the Merchant Interface, click &lt;STRONG&gt;Settings &lt;/STRONG&gt;under Account in the main menu, then click &lt;STRONG&gt;Partial Authorization&lt;/STRONG&gt;. From that page, check the box next to &lt;STRONG&gt;Allow Partial Payments&lt;/STRONG&gt; and click &lt;STRONG&gt;Submit&lt;/STRONG&gt;. Click &lt;STRONG&gt;OK &lt;/STRONG&gt;to confirm and you’re ready to process partial authorization transactions from your Simple Checkout buttons.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Value-Adding Services&lt;/STRONG&gt;&lt;BR /&gt;Stay tuned in the next few weeks for information on how the changes will affect the Advanced Fraud Detection Suite (AFDS), Customer Information Manager (CIM) and the Virtual Point of Sale (VPOS).&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The partial authorization release does not affect Automated Recurring Billing (ARB) or batch upload transactions, or any transaction run through the Virtual Terminal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Michelle&lt;/P&gt;
&lt;P&gt;Developer Community Manager&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jul 2010 22:45:02 GMT</pubDate>
    <dc:creator>Michelle</dc:creator>
    <dc:date>2010-07-14T22:45:02Z</dc:date>
    <item>
      <title>First Partial Authorization Release</title>
      <link>https://community.developer.cybersource.com/t5/News-and-Announcements/First-Partial-Authorization-Release/m-p/3838#M31</link>
      <description>&lt;P&gt;Hey everyone,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;On Tuesday, June 29th, we released support for partial authorization transactions as described in our &lt;A rel="nofollow" href="http://community.developer.authorize.net/t5/News-and-Announcements/New-MasterCard-Discover-Processing-Requirements/td-p/2634" target="_blank"&gt;previous post&lt;/A&gt; . With this release, Authorize.Net now supports these transactions on two processors, FDC Nashville and RBS WorldPay. This means that any merchant using those processors may now begin processing partial authorization transactions.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;It also means you can begin testing your own integrations using your test account. Yay! :smileyvery-happy:&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you’re looking for the information necessary to update your systems for partial authorization capabilities, well then, here you go:&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;AIM&lt;/STRONG&gt;&lt;BR /&gt;For the necessary information on what changes you will need to make if you integrate via Advanced Integration Method (AIM) please see the AIM guide at &lt;A rel="nofollow" href="http://www.authorize.net/support/AIM_guide.pdf" target="_blank"&gt;http://www.authorize.net/support/AIM_guide.pdf&lt;/A&gt; or review the updates at &lt;A rel="nofollow" href="http://www.authorize.net/support/AIM_apiupdates.pdf" target="_blank"&gt;http://www.authorize.net/support/AIM_apiupdates.pdf&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;SIM&lt;/STRONG&gt;&lt;BR /&gt;If you use the Server Integration Method (SIM), please review the updated SIM guide at &lt;A rel="nofollow" href="http://www.authorize.net/support/SIM_guide.pdf" target="_blank"&gt;http://www.authorize.net/support/SIM_guide.pdf&lt;/A&gt;.&amp;nbsp; Please note that the Relay Response field order has changed.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Additionally, you’ll see that all SIM Relay Response and Silent Post transaction responses will now include the card type and last four digits of the credit card number, regardless of whether or not the original transaction was enabled for partial authorizations.&amp;nbsp; This has been a long-awaited feature that we’re happy to be able to provide now. This information will be included in the following fields:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD&gt;Field Name&lt;/TD&gt;
&lt;TD&gt;Value&lt;/TD&gt;
&lt;TD&gt;Format&lt;/TD&gt;
&lt;TD&gt;Notes&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;x_account_number&lt;/TD&gt;
&lt;TD&gt;Last 4 digits of the card provided&lt;/TD&gt;
&lt;TD&gt;Alphanumeric (XXXX6835)&lt;/TD&gt;
&lt;TD&gt;This is a new field that is returned with all transactions.&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR&gt;
&lt;TD&gt;x_card_type&lt;/TD&gt;
&lt;TD&gt;Visa, MasterCard, American Express, Discover, Diners Club, EnRoute, JCB&lt;/TD&gt;
&lt;TD&gt;Text&lt;/TD&gt;
&lt;TD&gt;This is a new field that is returned with all transactions.&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;BR /&gt;&lt;STRONG&gt;Simple Checkout&lt;/STRONG&gt;&lt;BR /&gt;For anyone using Simple Checkout, simply log into the Merchant Interface, click &lt;STRONG&gt;Settings &lt;/STRONG&gt;under Account in the main menu, then click &lt;STRONG&gt;Partial Authorization&lt;/STRONG&gt;. From that page, check the box next to &lt;STRONG&gt;Allow Partial Payments&lt;/STRONG&gt; and click &lt;STRONG&gt;Submit&lt;/STRONG&gt;. Click &lt;STRONG&gt;OK &lt;/STRONG&gt;to confirm and you’re ready to process partial authorization transactions from your Simple Checkout buttons.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Value-Adding Services&lt;/STRONG&gt;&lt;BR /&gt;Stay tuned in the next few weeks for information on how the changes will affect the Advanced Fraud Detection Suite (AFDS), Customer Information Manager (CIM) and the Virtual Point of Sale (VPOS).&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;The partial authorization release does not affect Automated Recurring Billing (ARB) or batch upload transactions, or any transaction run through the Virtual Terminal.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Michelle&lt;/P&gt;
&lt;P&gt;Developer Community Manager&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jul 2010 22:45:02 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/News-and-Announcements/First-Partial-Authorization-Release/m-p/3838#M31</guid>
      <dc:creator>Michelle</dc:creator>
      <dc:date>2010-07-14T22:45:02Z</dc:date>
    </item>
  </channel>
</rss>

