<?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 How to avoid creating duplicate customer profiles with CreateCustomerProfileFromTransactionRequest in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-avoid-creating-duplicate-customer-profiles-with/m-p/82174#M51792</link>
    <description>&lt;P&gt;We are attempting to integrate Big Commerce and an Order Management System with Authorize.net&lt;/P&gt;&lt;P&gt;Big Commerce is creating the initial transaction during the checkout for an authorization.&lt;/P&gt;&lt;P&gt;We are then retrieving the order details from Big Commerce as well as the Gateway Transaction ID.&lt;/P&gt;&lt;P&gt;We then are attempting to locate an existing customer profile ID based on email address.&lt;/P&gt;&lt;P&gt;If we do not obtain an existing Profile, we are then looking to create a new profile from the transaction ID.&lt;/P&gt;&lt;P&gt;This process seems to create duplicate customer profiles every time in our sandbox.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have tried to call the method while providing merchantCustomerID as well.&lt;/P&gt;&lt;P&gt;So we would expect to get an error about dupes when sending a second "CreateCustomerProfileFromTransactionRequest" with a different transaction and the same merchantCustomerID, but we just create a duplicate profile. &amp;nbsp;We aren't seeing customer payment id's merging with customer profiles on subsequent calls either.&lt;/P&gt;&lt;P&gt;Is there a best practice for creating a Customer Profile using a transaction ID without creating a duplicate that also would merge new payments into an existing customer profile (if exists)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 14 Apr 2022 13:54:46 GMT</pubDate>
    <dc:creator>stevesh</dc:creator>
    <dc:date>2022-04-14T13:54:46Z</dc:date>
    <item>
      <title>How to avoid creating duplicate customer profiles with CreateCustomerProfileFromTransactionRequest</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-avoid-creating-duplicate-customer-profiles-with/m-p/82174#M51792</link>
      <description>&lt;P&gt;We are attempting to integrate Big Commerce and an Order Management System with Authorize.net&lt;/P&gt;&lt;P&gt;Big Commerce is creating the initial transaction during the checkout for an authorization.&lt;/P&gt;&lt;P&gt;We are then retrieving the order details from Big Commerce as well as the Gateway Transaction ID.&lt;/P&gt;&lt;P&gt;We then are attempting to locate an existing customer profile ID based on email address.&lt;/P&gt;&lt;P&gt;If we do not obtain an existing Profile, we are then looking to create a new profile from the transaction ID.&lt;/P&gt;&lt;P&gt;This process seems to create duplicate customer profiles every time in our sandbox.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have tried to call the method while providing merchantCustomerID as well.&lt;/P&gt;&lt;P&gt;So we would expect to get an error about dupes when sending a second "CreateCustomerProfileFromTransactionRequest" with a different transaction and the same merchantCustomerID, but we just create a duplicate profile. &amp;nbsp;We aren't seeing customer payment id's merging with customer profiles on subsequent calls either.&lt;/P&gt;&lt;P&gt;Is there a best practice for creating a Customer Profile using a transaction ID without creating a duplicate that also would merge new payments into an existing customer profile (if exists)?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 14 Apr 2022 13:54:46 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/How-to-avoid-creating-duplicate-customer-profiles-with/m-p/82174#M51792</guid>
      <dc:creator>stevesh</dc:creator>
      <dc:date>2022-04-14T13:54:46Z</dc:date>
    </item>
  </channel>
</rss>

