I'm in the process of building a custom tool using the CIM SOAP service to replace our old AIM based transaction authorization handling and I have a few (more) questions.
1) One of the issues that has been brought up here is that they occasionally need to contact a customer and get approval to place additional charges on an order using the same payment method. They are apparently doing this via the management tools directly on authorize.net and not through our existing AIM/cart tools. I assume that if a customer chooses not to keep their payment information stored in the CIM database (i.e. I remove the payment profile when they complete their transaction with a DeleteCustomerPaymentProfile request) that they will still be able to use the web-based management tool in the same way?
2) If a PRIOR_AUTH_CAPTURE is sent via a:
am I to assume correctly that this goes to the same system used by the AIM methods and therefore the same authorization code could be captured using the authcode with an AIM methodology later?
3) If you run a PRIOR_AUTH_CAPTURE on a credit card, what types of holds are placed on the customer account and how long do they remain if they are not captured? Does a hold-on-funds/balance remain if the PRIOR_AUTH_CAPTURE is voided shortly thereafter, and if so, for how long?
Finally but not as important, are there any methods to find a customerProfileId using the other fields in the customer profile such as the email or merchantCustomerId?
Can you provide more information? Is your server displaying this message to you or is this part of the response that you are receiving from Authorize.Net?
If this is an error that your server is displaying to you, perhaps you could include the details such as where it is occurring in the script and any additional information your server may be logging in relation to this error.
If this is part of the response that you are receiving from Authorize.Net, can you provide the full response?