validateCustomerPaymentProfileRequest takes up to five values (aside from the merchantAuthentication). These are:
- customerProfileId
- customerPaymentProfileId
- customerShippingAddressId (optional)
- cardCode (optional)
- validationMode
The cardCode parameter is the CCV/CVV, and the payment profile already contains the expiration date of the card, so it is possible to validate all three. In fact, I don't believe you can even create a payment profile without the expiration date. I grabbed the latest C# sample code[^], and added a new method to the Program class that utilizes the provided validateCustomerPaymentProfileRequest class in the same way that the other "request" classes are used. Here is that method:
/// <summary>
/// Validate the payment profile
/// </summary>
/// <param name="profile_id">
/// The customer profile id we are doing this for</param>
/// <param name="PaymentProfileID">
/// The payment profile id that we are validating</param>
/// <param name="cardCode">
/// The card validation code (CCV) to validate with. Optional.</param>
/// <returns>
/// <strong>True</strong> if the payment profile validates; Otherwise
/// <strong>False</strong>.
/// </returns>
public static bool ValidateCustomerPaymentProfile(long profile_id,
string PaymentProfileID,
string cardCode)
{
bool out_bool = false;
// Setup the request
validateCustomerPaymentProfileRequest request =
new validateCustomerPaymentProfileRequest();
XmlAPIUtilities.PopulateMerchantAuthentication((ANetApiRequest)request);
// Set the properties on the request
request.customerProfileId = profile_id.ToString();
request.customerPaymentProfileId = PaymentProfileID;
request.cardCode = cardCode;
request.validationMode = validationModeEnum.liveMode;
// Send the request and get the response
System.Xml.XmlDocument response_xml = null;
bool bResult = XmlAPIUtilities.PostRequest(request, out response_xml);
object response = null;
validateCustomerPaymentProfileResponse api_response = null;
// See what the response was
if (bResult)
{
bResult = XmlAPIUtilities.ProcessXmlResponse(response_xml, out response);
}
if (!(response is validateCustomerPaymentProfileResponse))
{
ANetApiResponse ErrorResponse = (ANetApiResponse)response;
Console.WriteLine(String.Format(
"Validate Payment Profile\n code: {0}\n msg: {1}",
ErrorResponse.messages.message[0].code,
ErrorResponse.messages.message[0].text));
return out_bool;
}
if (bResult) api_response = (validateCustomerPaymentProfileResponse)response;
if (api_response != null)
{
out_bool = true;
Console.WriteLine(String.Format(
"Validate Payment Profile\n code: {0}\n msg: {1}",
api_response.messages.message[0].code,
api_response.messages.message[0].text));
}
return out_bool;
}
I was able to compile and run this without problems. Let me know if you have any problem with this.
IMPORTANT: Please note that on a live account when a validation is submitted with validationMode = "liveMode", then the merchant account associated with the Authorize.net account will be charged transaction fees. I wrote a blog post[^] about this. Also, very recently, Visa has imposed rules about validating credit cards. By using CIM's validateCustomerPaymentProfileRequest feature, you should automatically be in compliance with the new Visa mandates, depending somewhat on the payment processor used by your merchant service provider. You can read the full details of this in this forum announcement[^].
