<?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 Required fields triggering refund errors through PHP SDK in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Required-fields-triggering-refund-errors-through-PHP-SDK/m-p/74096#M45999</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;During our testing, we are seeing the Refund API call trigger errors about Billing Form fields not being included if they are specially marked as Required in the payments form settings area. Is this intentional? It would seem that refunds should just require either the last 4 of the CC and transaction ID, or the full card number and expiration. Billing field requirements should just be restricted to charges/auths. We have a SaaS service that connects to customer Authorize.net accounts for billing, and occasionally some have required fields checked due to other business requirements.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Nov 2020 17:01:25 GMT</pubDate>
    <dc:creator>rsvpBOOKDev</dc:creator>
    <dc:date>2020-11-24T17:01:25Z</dc:date>
    <item>
      <title>Required fields triggering refund errors through PHP SDK</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Required-fields-triggering-refund-errors-through-PHP-SDK/m-p/74096#M45999</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;During our testing, we are seeing the Refund API call trigger errors about Billing Form fields not being included if they are specially marked as Required in the payments form settings area. Is this intentional? It would seem that refunds should just require either the last 4 of the CC and transaction ID, or the full card number and expiration. Billing field requirements should just be restricted to charges/auths. We have a SaaS service that connects to customer Authorize.net accounts for billing, and occasionally some have required fields checked due to other business requirements.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Nov 2020 17:01:25 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Required-fields-triggering-refund-errors-through-PHP-SDK/m-p/74096#M45999</guid>
      <dc:creator>rsvpBOOKDev</dc:creator>
      <dc:date>2020-11-24T17:01:25Z</dc:date>
    </item>
  </channel>
</rss>

