topic Re: Requesting API getHostedPaymentPageRequest to get Token Failed, now suddenly works again in Integration and Testing

Requesting API getHostedPaymentPageRequest to get Token Failed, now suddenly works again

Mullie — Tue, 08 May 2018 09:46:46 GMT

Since end of last week our system was not able to call the Authorize.net API via https://api.authorize.net/xml/v1/request.api

By submitting a XML string <getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">... we retrieve the token and display the hosted payment page to our customers.

This request suddenly stopped working last week. Yesterday i was debugging the issue and the only thing the API returned was 'true'. Today is seems to be working fine again.

Was there an issue on your side? What's going on?

Regards,
Rick

Re: Requesting API getHostedPaymentPageRequest to get Token Failed, now suddenly works again

Mullie — Tue, 08 May 2018 14:49:05 GMT

Sorry! Seems the problem is still occuring. Our CURL command gives the following debug output:
* Hostname was NOT found in DNS cache * Trying 64.94.118.84... * Connected to api.authorize.net (64.94.118.84) port 443 (#0) * successfully set certificate verify locations: * CAfile: none CApath: /etc/ssl/certs * SSL certificate problem: self signed certificate in certificate chain * Closing connection 0 !data:1!

Re: Requesting API getHostedPaymentPageRequest to get Token Failed, now suddenly works again

Mullie — Wed, 09 May 2018 09:03:51 GMT

Issue solved by adding:

cd /etc/ssl/certs/
wget http://curl.haxx.se/ca/cacert.pem

and adding the following line to my servers php.ini:
curl.cainfo = "/etc/ssl/certs/cacert.pem"