<?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 Creating Customer and Payment Profiles Getting Duplicate Error in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Creating-Customer-and-Payment-Profiles-Getting-Duplicate-Error/m-p/91862#M57646</link>
    <description>&lt;P&gt;I have a unique situation, i think.&amp;nbsp; I've been working on migrating a customer from a different platform that only used card info and tokens to the CIM API with auth.net.&amp;nbsp; All old card info was migrated by auth.net and presented itself as a unique&amp;nbsp; set of customer ID's and payment profile ID;'s for each individual card.&amp;nbsp; So, this results in a "customer" having up to 10 customer ID's and 10 payment Profiles with the combination being unique instead of one customer profile and 10 payment profiles attached.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have an automated billing system which now uses the auth.net CIM API to process scheduled payments, and we have no issues processing transactions using the migrated data; however, when we attempt to add a new card the first time we do so we get a new customer profile and payment profile (which is fine because we compensated for the non-normalized data), but when we go to add a second card to that account we get the Error 39: duplicate profile for ID xxxxxx.&amp;nbsp; Even if the card number does not match!&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to identify ahead of time if a given card number exists? Or can someone explain why this would happen?&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;</description>
    <pubDate>Mon, 30 Jun 2025 13:49:39 GMT</pubDate>
    <dc:creator>ezaspi</dc:creator>
    <dc:date>2025-06-30T13:49:39Z</dc:date>
    <item>
      <title>Creating Customer and Payment Profiles Getting Duplicate Error</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Creating-Customer-and-Payment-Profiles-Getting-Duplicate-Error/m-p/91862#M57646</link>
      <description>&lt;P&gt;I have a unique situation, i think.&amp;nbsp; I've been working on migrating a customer from a different platform that only used card info and tokens to the CIM API with auth.net.&amp;nbsp; All old card info was migrated by auth.net and presented itself as a unique&amp;nbsp; set of customer ID's and payment profile ID;'s for each individual card.&amp;nbsp; So, this results in a "customer" having up to 10 customer ID's and 10 payment Profiles with the combination being unique instead of one customer profile and 10 payment profiles attached.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have an automated billing system which now uses the auth.net CIM API to process scheduled payments, and we have no issues processing transactions using the migrated data; however, when we attempt to add a new card the first time we do so we get a new customer profile and payment profile (which is fine because we compensated for the non-normalized data), but when we go to add a second card to that account we get the Error 39: duplicate profile for ID xxxxxx.&amp;nbsp; Even if the card number does not match!&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any way to identify ahead of time if a given card number exists? Or can someone explain why this would happen?&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;</description>
      <pubDate>Mon, 30 Jun 2025 13:49:39 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Creating-Customer-and-Payment-Profiles-Getting-Duplicate-Error/m-p/91862#M57646</guid>
      <dc:creator>ezaspi</dc:creator>
      <dc:date>2025-06-30T13:49:39Z</dc:date>
    </item>
  </channel>
</rss>

