<?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 CyberSource Double Authorization in cybersource APIs</title>
    <link>https://community.developer.cybersource.com/t5/cybersource-APIs/CyberSource-Double-Authorization/m-p/85163#M670</link>
    <description>&lt;P&gt;&lt;SPAN&gt;We are using CyberSource as our credit card processing and have split the authorization from the capture functions. We preauthorize the card when we take the sales order, and charge the card several weeks later prior to shipping but we are authorizing the card again upon the process. Does anyone know the settings I need in my Credit Card Processing File to make the authorization not occur when I charge the card because authorization has already occurred?&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 06 Dec 2022 07:36:55 GMT</pubDate>
    <dc:creator>NatwanTilembar</dc:creator>
    <dc:date>2022-12-06T07:36:55Z</dc:date>
    <item>
      <title>CyberSource Double Authorization</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/CyberSource-Double-Authorization/m-p/85163#M670</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We are using CyberSource as our credit card processing and have split the authorization from the capture functions. We preauthorize the card when we take the sales order, and charge the card several weeks later prior to shipping but we are authorizing the card again upon the process. Does anyone know the settings I need in my Credit Card Processing File to make the authorization not occur when I charge the card because authorization has already occurred?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Dec 2022 07:36:55 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/CyberSource-Double-Authorization/m-p/85163#M670</guid>
      <dc:creator>NatwanTilembar</dc:creator>
      <dc:date>2022-12-06T07:36:55Z</dc:date>
    </item>
    <item>
      <title>Re: CyberSource Double Authorization</title>
      <link>https://community.developer.cybersource.com/t5/cybersource-APIs/CyberSource-Double-Authorization/m-p/85183#M678</link>
      <description>&lt;P&gt;Have you considered doing the flow in the following order:&lt;BR /&gt;Step #1:&amp;nbsp; &amp;nbsp;&lt;A href="https://developer.cybersource.com/api-reference-assets/index.html#payments_payments_process-a-payment" target="_blank"&gt;https://developer.cybersource.com/api-reference-assets/index.html#payments_payments_process-a-payment&lt;/A&gt;&amp;nbsp;- only authorize the intended amount here.&lt;BR /&gt;Step #2: Then after a few days, when you are ready to capture the amount, just call this:&amp;nbsp;&lt;A href="https://developer.cybersource.com/api-reference-assets/index.html#payments_capture_capture-a-payment" target="_blank"&gt;https://developer.cybersource.com/api-reference-assets/index.html#payments_capture_capture-a-payment&lt;/A&gt;&amp;nbsp;(Note that this API, in the url, accepts a id - that is the transactionId returned from the API call made for authorization in the step #1)&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Dec 2022 23:41:38 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/cybersource-APIs/CyberSource-Double-Authorization/m-p/85183#M678</guid>
      <dc:creator>rajvpate</dc:creator>
      <dc:date>2022-12-07T23:41:38Z</dc:date>
    </item>
  </channel>
</rss>

