cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

best practice if duplicate Customer Profile found

I am in the final stages of a hosted CIM integration. I am testing for the unlikely event that the Authorize.net CustomerProfileID is missing from my database, but the customer still has an existing Authorize.net CustomerProfile based on email address. In that case, createCustomerProfileRequest() will return that this is a duplicate and not allow me to "create" the profile. 

 

I wonder what is best practice in that case - should I purge the existing Authorize.net Profile and create a brand new one, or should I update my system with the existing CustomerProfileID* so they are matched up again?

 

*The CustomerProfileId is returns from createCustomerProfileRequest() in the error message.

 

Again it is unlikely that my database will be missing the CustomerProfileID, but I have to test for that anyway.

 

stzoid
Member
1 REPLY 1

keep the old one and update your system.

RaynorC1emen7
Expert