Cardholder Authentication Fields Ignored

edcoffin — Wed, 17 Apr 2013 13:06:52 GMT

Greetings,

My team is using AIM, with PHP - connected to the Shopp e-commerce plugin for Wordpress.

We have been using authorize.net for several months without an issue.

Recently we were asked to integrate 3Ds security via Cardinal into our solution. Connecting to Cardinal and retrieving the ECI/UCAF, as well as the CAVV/AVV is working without a hitch for my MasterCard that is enrolled. However, upon passing these values to to auth.net [via the fields: x_authentication_indicator, and x_cardholder_authentication_value], the transaction succeeds, but reports that:

CAVV Result Code:

Not Applicable

I have contacted customer support, and got an escalated response that Authorize.net did not receive the fields [x_authentication_indicator, and x_cardholder_authentication_value]. Our account is in Live mode, and we are configured to accept Secure Visa and MasterCard payments in the admin panel. In Test mode, I disabled the secure payment option and tried passing a transaction with the cardholder authentication fields. The transaction failed with Error 3. At least in test mode, it was able to parse these values.

Cardinal is returning the CAVV string in Base64 encoding. I am definitely URL encoding the string before Posting the request. The transaction is of type AUTH_CAPTURE.

Our merchant account is with Chase Payment Tech. After reading a similar thread on this forum, I contacted Chase Payment and they ensured me that our account is capable of receiving the Cardholder Authentication.

I have used the Data Validation URL and it parsed all the values accordingly.

I will post the parameters I am POSTing, as well as a response I got for the request. If anyone has any ideas, I'm all ears. A number of the fields have been given 'x's to 'hopefully' keep the data anonymous.

My request to authorize.net

x_test_request=FALSE&x_login=xxxxxxx&x_tran_key=xxxxxxxxx&x_Delim_Data=TRUE&x_Delim_Char=%7C&x_Encap_Char=&x_version=3.1&x_relay_response=FALSE&x_method=CC&x_email_customer=FALSE&x_merchant_email=&x_type=&x_amount=12.05&x_customer_ip=71.7.137.234&x_fp_sequence=1365536039&x_fp_timestamp=1365536039&x_first_name=Jon&x_last_name=Doe&x_email=jondoe@email.com&x_phone=55555555555&x_card_num=xxxxxxxxxxx&x_exp_date=xxxx&x_card_code=455&x_address=xxxx&x_city=xxxxxn&x_state=xxxx&x_zip=xxxxx&x_country=CA&x_ship_to_first_name=xxxx&x_ship_to_last_name=xxxxx&x_ship_to_address=xxxxxx+Ave&x_ship_to_city=Nowhere&x_ship_to_state=AZ&x_ship_to_zip=C1A+9S1&x_ship_to_country=CA&x_freight=5.449&x_tax=1.61345&x_line_item%5B0%5D=1%3C%7C%3E3pc+Mini+Measuring+Spoons%3C%7C%3E%3C%7C%3E1%3C%7C%3E4.99%3C%7C%3EY&x_cardholder_authentication_value=jK6KjTOD%2BPULCBAUi1ADBYMAAAA%3D&x_authentication_indicator=2

the response:

1|1|1|This transaction has been approved.|15340Z|X|5150332237|||12.05|CC|auth_capture||Jon|Doe||xxxxx|xxxxx|AZ|C1A 9S1|CA|55555555555||jondoe@email.com|Jon|Doe||Address|City|AZ|C1A 9S1|CA|1.61||5.45|||2DC906F69C79A9105D59645300E4018A|M||||||||||||XXXX9870|MasterCard|||||||||||||||||1<|>3pc Mini Measuring Spoons<|><|>1<|>4.99<|>Y

Best regards!

Eric

Re: Cardholder Authentication Fields Ignored

edcoffin — Mon, 29 Apr 2013 12:50:51 GMT

No ideas?

Re: Cardholder Authentication Fields Ignored

RaynorC1emen7 — Mon, 29 Apr 2013 13:54:19 GMT

did you ask authorize.net to double check the account setup?

Re: Cardholder Authentication Fields Ignored

lz854434716 — Tue, 02 Dec 2014 02:58:33 GMT

hi sir , the Cardholder Authentication Value is required only for authoOnly and authCapture turansactions processed through carhodler authentication programs.When submitted with other transaction types, this value is ignored.

topic Re: Cardholder Authentication Fields Ignored in Integration and Testing

Cardholder Authentication Fields Ignored

Re: Cardholder Authentication Fields Ignored

Re: Cardholder Authentication Fields Ignored

Re: Cardholder Authentication Fields Ignored