I do wish that I received the same response.
I followed the procedure of:
- Go to https://ssllabs.com/ssltest/analyze.html?d=api2.authorize.net
- Wait awhile
- Scroll down to "Additional Certificates (if supplied)
- Look to the right of that title for a download arrow icon.
- It opens up into a window with a path such as: https://www.ssllabs.com/ssltest/getTestChain?d=api2.authorize.net&cid= (...yadayadayadawithatimestampvariable)
I then:
- used Notepad++ and created a new text file.
- Pasted in the -----BEGIN CERTIFICATE----...etc text
- Saved the file as entrust_L1K.crt
The importing of the cert was using these different steps:
- Log in to cPanel (domainnamehere.com:2083)
- Go to SSL/TLS
- Certificates (CRT) > Generate, view, upload, or delete SSL certificates.
- Upload New Certificate -> Choose File (find entrust_L1K.crt in file manager)
- Upload Certificate
The certificate is now visible, at the top of the list of SSL certificates, and shows that:
- the issuer is Entrust, Inc
- The key size is 2048
- The domains are *.authorize.net and authorize.net
When re-attempting a transaction on the website, the same response as before was returned.
By that response, I am referring to the transaction response page immediately loading, but without outputting any results returned from Authorize.net, such as what would normally be returned as:
$response->getTransactionResponse();
and with the value of "1" for:
$tresponse->getResponseCode()
I reviewed the text file which was defined here, earlier in the php file being run:
define("AUTHORIZENET_LOG_FILE", "phplog");
That "phplog" text file includes the XML response. Normally, if it was a declined card, such as with incorrect information being entered, then there would be a detailed response showing why it was declined.
However, with the current response from Authorize.net, that XML log is very short, only returning the values which were sent to Authorize.net, but not any explanation of why the card was declined... or even a log saying that the card was declined. It's almost like a one-way conversation, and I would be expecting at least some reply from Authorize.net showing that the transaction was declined (and why).
For other background information:
- The response on the phplog file is validating that sdk-php-2.0.0 is being used.
- The SSL provider did run a successful test showing that the "leaf" was being provided.
With both of those covered (the host and the SSL provider), the only remaining culprit is Colonel Mustard in the library with the wrench... in other words, Authorize.net.
