I have a unique situation, i think. 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. All old card info was migrated by auth.net and presented itself as a unique set of customer ID's and payment profile ID;'s for each individual card. 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.
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. Even if the card number does not match!
Is there any way to identify ahead of time if a given card number exists? Or can someone explain why this would happen?
thanks
