- 🇺🇸United States rhovland Oregon
Like #3154898: E00039 A duplicate customer payment profile already exists → we need a way to reproduce this reliably if we can ever hope to fix it.
I had a chat with Authorize.net support. It seems the commerce authorize.net module is requiring the customer profile on the Authorize.net system to be there in order to process payments. If there's no profile commerce just stops processing the payment with the E00040 error, it doesn't wait for the profile to be created.
In addition, the second error message that usually comes is the E00039: A duplicate customer payment profile already exists. Commerce doesn't seem to be trying to use the profile in the system, but tries to create a new one in addition to processing the payment on the existing profile.
From what I can tell, Commerce Authorize module needs to check if a profile exists, if one exists use it, if one doesnt exist request it to be created and wait until the profile is created then use that profile.
NOTE: this does not happen on every transaction. Will try to dig up stats and report back here.
I'm also ok, at least in our situation, to not use the Customer Information Management (CIM) system at all. We don't care about reoccurring payments. We're ok if customers need to enter their credit card in a second time in the future as this happens only annually.
I have seen other issues related this this:
-
#3154898: E00039 A duplicate customer payment profile already exists →
-
#3281961: Remove dependency on CIM. →
Postponed: needs info
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Like #3154898: E00039 A duplicate customer payment profile already exists → we need a way to reproduce this reliably if we can ever hope to fix it.