PS3 Check Out Failure

My clients store is working fine except for one product that triggers a check out failure. Authorize.Net reports no problems on their end. One order that failed through the store was processed manually through Elavon without failure, so the credit card was valid in at least one case. The message on the check out failure page is that the credit card information or address is incorrect. I added the code found on this forum to the check out failure page. This is the result, with personal information masked:

Auth Net:

Full Request: x_login=657rKr26ZYu&x_tran_key=6T2BeQ56a79jU67V&x_version=3.1&x_invoice_num=604d3db431903f38bf70bd1398e2102a&x_test_request=0&x_method=CC&x_type=AUTH_CAPTURE&x_relay_response=FALSE&x_delim_data=TRUE&x_delim_char=::&x_customer_ip=50.131.143.82&x_amount=503.99&x_description=1 Enclosure Kit (5)&x_line_item=5<|>Enclosure Kit <|><p><strong>Enclosure Kit</strong></p><p><span style="color: rgb(255, 0, 0); ">S</span><span style="color: rgb(255, 0, 0); ">ave $25 to $160&#160; - &#160;all Enclosures on Sale! &#160;Enter coupon code 275</span></p><p></p><|>1<|>399.99<|>YES&x_card_num=xxxxxxxxxxxx2604&x_exp_date=062015&x_card_code=610&x_email_customer=TRUE&x_tax=32&x_tax_exempt=FALSE&x_freight=72.00&x_first_name=john&x_last_name=doe&x_address=po box 5555&x_city=petaluma&x_state=CA&x_zip=55555&x_phone=7075555555&x_fax=&x_email=johnd@pets.com&x_country=US&x_ship_to_first_name=john&x_ship_to_last_name=doe&x_ship_to_address=po box 5555&x_ship_to_city=petaluma&x_ship_to_state=CA&x_ship_to_zip=55555&x_ship_to_country=US&x_ship_to_phone=7075555555&x_ship_to_fax=&x_recurring_billing=NO
Full Response: 3::1::270::Line item 1 is invalid.::::P::0::604d3db431903f38bf70::1 Enclosure Kit (5)::503.99::CC::auth_capture::::john::doe::::po box 5555::petaluma::CA::55555::US::7075555555::::johnd@pets.com::john::doe::::po box 5555::petaluma::CA::55555::US::32.00::::72.00::FALSE::::AE765708C99F764245A3535F8279F0AC::::::::::::::::::::::::::XXXX2604::::::::::::::::::::::::::::::::::::::::::7075555555::

Express Authorize:
Full Request: n/a
Full Response: n/a

Express Process:
Full Request: n/a
Full Response: n/a

I see within the report that "line item 1 is invalid", but not sure what line item 1 is.

Your help is appreciated.
Robert

line item 1 reefers to the item info being sent to authorize.net:

x_description=1 Enclosure Kit (5)&x_line_item=5<|>Enclosure Kit <|><p><strong>Enclosure Kit</strong></p><p><span style="color: rgb(255, 0, 0); ">S</span><span style="color: rgb(255, 0, 0); ">ave $25 to $160 - all Enclosures on Sale! Enter coupon code 275</span></p><p></p><|>1<|>399.99<|>YES



the problem is caused by the HTML code in the cart description. The cart description cannot contain HTML code.

Thanks Jason.

I see that but I am not sure I follow. The client entered the information (where previously there was just the title "Enclosures". The html is visible when in source view, but not in the view the customer used. Even the word "Enclosure" has html associated with it, and when only the title was present previously there was no check out failure.

I guess my question is why is the html being passed, or is there a character limit to the description? Or could it be the inline css present (red text) rendered by the text editor?

Thanks,
Robert

the HTML is being passed because it is being added as part of the cart description.


The cart description cannot be given any styling like adding strong or changing the color.

Thanks Jason.

Changing the description text from red to black seemed to fix the problem. Not to belabor the point, but the option of bold text does not seem to be an issue, as the "title" is <p><strong>Enclosures</strong></p>, instead of using the h tag.

So, perhaps this has changed with newer versions of Power Store, but if things like text color are a problem within the description, shouldn't the text editor reflect that by not allowing these types of decoration, or should the code be changed within the store to allow this information to be passed?

Thanks!

1. My PS3 client just shared an email from Authorize.net. Apparently they announced they are upgrading api.authorize.net to new security certificates later this month, which are signed using Security Hash Algorithm 2 (SHA-2) and 2048-bit signatures. These upgrades were already completed on secure.authorize.net in May of 2015. Looking at the AuthNet_PHP.php file it looks like PS3 uses secure.authorize.net, (I am not aware of any transactions failing). So can I assume that the gateway and PS3 solution should continue to work using SHA-2 signed certificates (i.e. api.authorize.net does not come into play with PS3.)?

2. In October 2015, due to Authorize.net to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order. Does PS3 have any functionality that expects Authorize.Net-generated IDs to be sequential? I do not see anything in the PS3 code that expects sequential IDs. Am I correct?

3. Authorize.net also will no longer allow a 10 character field limit on the Transaction ID. They are saying that if any solution (PS3 in this case) is required to define a character limit when storing any of their IDs, the limit should be no less than 20 characters. Is PS3 fine with more than 10 characters?

4. Authorize.net is switching to Akamai (third-party cloud network service) that routes and delivers Internet traffic.They recommend updating to new transaction URLs that are available now. The one that seems to apply to PS3 is https://secure2.authorize.net/gateway/transact.dll. The following line of code appears in the PS3 AuthNet_PHP.php file:
curl_setopt($ch, CURLOPT_URL,"https://" . ($reqArray[1][4] == 1 ? 'test' : 'secure') . ".authorize.net/gateway/transact.dll");
Can I just append a "2" after "secure"?

5. Finally, do any of the answers to the above change if I can convince my client to upgrade to PS4? Or should I wait for responsive, mobile friendly PS5? Any release dates for PS5?

Thanks very much for your help!
Robert

There should be no issues with the transition by Authorize.net. It should not effect your client's store.

No need to update yet, and we don't have a public release date for ps5.

Thanks Ray!