<?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 Refund CIM transaction API request elements in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Refund-CIM-transaction-API-request-elements/m-p/55560#M30429</link>
    <description>&lt;P&gt;From &lt;A href="http://developer.authorize.net/api/reference/features/customer_profiles.html" target="_blank"&gt;http://developer.authorize.net/api/reference/features/customer_profiles.html&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;If you are submitting a refund against a previous CIM transaction, the following guidelines apply:
Include customerProfileId, customerPaymentProfileId, and transId.
customerShippingAddressId is optional.
creditCardNumberMasked, bankRoutingNumberMasked, and bankAccountNumberMasked do not need to be included, but they are validated if they are included.
&lt;BR /&gt;If you are submitting a refund for a non-CIM transaction, the following guidelines apply:
You must include transId, creditCardNumberMasked (or bankRoutingNumberMasked and bankAccountNumberMasked).
Do not include customerProfileId, customerPaymentProfileId, or customerShippingAddressId.
&lt;BR /&gt;You can also issue an unlinked refund for a CIM transaction. In this case, the following rules apply:
You must be enrolled in Expanded Credit Capabilities (ECC). For more information about ECC, go to http://www.authorize.net/files/ecc.pdf.
You must include customerProfileId and customerPaymentProfileId.
customerShippingAddressId is optional.
Do not include transId, creditCardNumberMasked, bankRoutingNumberMasked, or bankAccountNumberMasked.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both in testing and API reference, profile related fields are not allowed in a&amp;nbsp;createTransactionRequest request of type&amp;nbsp;voidTransaction. How should I be submitting a refund for a CIM charge?&lt;/P&gt;</description>
    <pubDate>Wed, 24 Aug 2016 18:12:43 GMT</pubDate>
    <dc:creator>monki</dc:creator>
    <dc:date>2016-08-24T18:12:43Z</dc:date>
    <item>
      <title>Refund CIM transaction API request elements</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Refund-CIM-transaction-API-request-elements/m-p/55560#M30429</link>
      <description>&lt;P&gt;From &lt;A href="http://developer.authorize.net/api/reference/features/customer_profiles.html" target="_blank"&gt;http://developer.authorize.net/api/reference/features/customer_profiles.html&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;If you are submitting a refund against a previous CIM transaction, the following guidelines apply:
Include customerProfileId, customerPaymentProfileId, and transId.
customerShippingAddressId is optional.
creditCardNumberMasked, bankRoutingNumberMasked, and bankAccountNumberMasked do not need to be included, but they are validated if they are included.
&lt;BR /&gt;If you are submitting a refund for a non-CIM transaction, the following guidelines apply:
You must include transId, creditCardNumberMasked (or bankRoutingNumberMasked and bankAccountNumberMasked).
Do not include customerProfileId, customerPaymentProfileId, or customerShippingAddressId.
&lt;BR /&gt;You can also issue an unlinked refund for a CIM transaction. In this case, the following rules apply:
You must be enrolled in Expanded Credit Capabilities (ECC). For more information about ECC, go to http://www.authorize.net/files/ecc.pdf.
You must include customerProfileId and customerPaymentProfileId.
customerShippingAddressId is optional.
Do not include transId, creditCardNumberMasked, bankRoutingNumberMasked, or bankAccountNumberMasked.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both in testing and API reference, profile related fields are not allowed in a&amp;nbsp;createTransactionRequest request of type&amp;nbsp;voidTransaction. How should I be submitting a refund for a CIM charge?&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 18:12:43 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Refund-CIM-transaction-API-request-elements/m-p/55560#M30429</guid>
      <dc:creator>monki</dc:creator>
      <dc:date>2016-08-24T18:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Refund CIM transaction API request elements</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Refund-CIM-transaction-API-request-elements/m-p/55573#M30440</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi&amp;nbsp;&lt;SPAN class=""&gt;&lt;A id="link_1" class="lia-link-navigation lia-page-link lia-user-name-link" href="https://community.developer.cybersource.com/t5/user/viewprofilepage/user-id/18977" target="_self"&gt;monki&lt;/A&gt;,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;A void and refund are two different transaction types and different requests. We do have not a specific example for unlinked refunds against a profile. However the API reference refund can be followed&amp;nbsp;&lt;A href="http://developer.authorize.net/api/reference/index.html#payment-transactions-refund-a-transaction" target="_blank"&gt;http://developer.authorize.net/api/reference/index.html#payment-transactions-refund-a-transaction&lt;/A&gt; and you only need to add the profile IDs as you add them in an authorization request.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class=""&gt;Joy&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 26 Aug 2016 22:09:27 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Refund-CIM-transaction-API-request-elements/m-p/55573#M30440</guid>
      <dc:creator>Joy</dc:creator>
      <dc:date>2016-08-26T22:09:27Z</dc:date>
    </item>
  </channel>
</rss>

