Hello,
We have been using Authorize.Net CIM for quite some time now and we are happy, but we decided to move to Accept js to avoid PCI compliance issues.
So far, we have been following this workflow during order creation:
1) Try to create customer profile
2) If it exists we are getting a 'duplicate' error and the existing customer profile ID is returned, if it does not then it is created and we get a customer profile id anyway
3) Try to create a customer payment profile (sending the card data [card number, expiration date, card code])
4) If it exists we are getting a 'duplicate' error and the existing customer payment profile ID is returned, if it does not then it is created and we get a customer payment profile id anyway
Now that we moved to Accept js we are having the following issue:
1) Try to get customer profile
2) If it exists, we get the customer profile ID, if not then we create a new one (new request) and we get a customer profile id anyway
3) Try to create a customer payment profile (sending opaqueData since we do not have any card details)
4) In both cases where a customer payment profile exists or not, the system initiates a create and never responds with a 'duplicate' error. So, if this customer profile contains 10 customer payment profiles already, we are getting the error mentioned in the title [code: E00042]
Is there any way (option in Authorize.Net's back-end) to enable step 4 to work as it used to before Accept js and return duplicate error when a payment profile with the same billing data exists (including the existing payment profile's ID so we can reuse it and not have to create a new profile)?
If not, then what is the best way/workaround to achieve the same results as before?
