topic Re: error: E00001 An error occurred during processing. Please try again. in Integration and Testing

error: E00001 An error occurred during processing. Please try again.

ansherina — Tue, 21 Feb 2017 19:07:12 GMT

working on getHostedPaymentPageRequest API with my sandbox account.

getting this error:

ErrorE00001An error occurred during processing. Please try again.

Here's the xml post:

<getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
    <merchantAuthentication>
        <name>name</name>
        <transactionKey>transactionkey</transactionKey>
    </merchantAuthentication>
    <transactionRequest>
        <transactionType>authCaptureTransaction</transactionType>
        <amount>20.00</amount>
    </transactionRequest>
    <hostedPaymentSettings>
        <setting>
            <settingName>hostedPaymentBillingAddressOptions</settingName>
            <settingValue>{"show": true, "required":true}</settingValue>
        </setting>
        <setting>
            <settingName>hostedPaymentButtonOptions</settingName>
            <settingValue>{"text": "Pay"}</settingValue>
        </setting>
        <setting>
            <settingName>hostedPaymentReturnOptions</settingName>
            <settingValue>{"url":"https://testurl.com/good","urlText":"Continue","cancelUrl":"https://testurl.com/cancel","cancelUrlText":"Cancel"}</settingValue>
        </setting>
    </hostedPaymentSettings>
</getHostedPaymentPageRequest>

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Tue, 21 Feb 2017 19:24:04 GMT

Hi @ansherina,

Can you verify the url you're posting this too? Also, are you sending a Content-Type: header in your HTTP post? If so, what is it set to?

One other thing is to check the "hostedPaymentReturnOptions". It looks like from what you pasted, the closing curly brace is url encoded as %7D, although I don't know if it's our forum software that did that. Make sure that in your code that section looks like:

        <setting>
            <settingName>hostedPaymentReturnOptions</settingName>
            <settingValue>{"url":"https://testurl.com/good","urlText":"Continue","cancelUrl":"https://testurl.com/cancel","cancelUrlText":"cancel"}</settingValue>
        </setting>

If there's any way to capture the full HTTP request and post it here, that would be helpful.

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Tue, 21 Feb 2017 19:44:16 GMT

Hi @Aaron,

I'm using application/xml as content type. Kindly check the code below. I got it from your documentation on github just for testing.

<?php

$xmlStr = <<<XML
<?xml version="1.0" encoding="utf-8"?>
<getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
    <merchantAuthentication></merchantAuthentication>
    <transactionRequest>
        <transactionType>authCaptureTransaction</transactionType>
        <amount>20.00</amount>
    </transactionRequest>
    <hostedPaymentSettings>
        <setting>
            <settingName>hostedPaymentBillingAddressOptions</settingName>
            <settingValue>{"show": true, "required":true}</settingValue>
        </setting>
        <setting>
            <settingName>hostedPaymentButtonOptions</settingName>
            <settingValue>{"text": "Pay"}</settingValue>
        </setting>
    </hostedPaymentSettings>
</getHostedPaymentPageRequest>
XML;
$xml = simplexml_load_string($xmlStr,'SimpleXMLElement', LIBXML_NOWARNING);

$xml->merchantAuthentication->addChild('name','name');
$xml->merchantAuthentication->addChild('transactionKey','transactionkey');

$commUrl = json_encode(array('url' => thisPageURL()."iCommunicator.html" ),JSON_UNESCAPED_SLASHES);
$xml->hostedPaymentSettings->setting[0]->addChild('settingValue',$commUrl);

$retUrl = json_encode(array("showReceipt" => false ,'url' => thisPageURL()."return.html","urlText"=>"Continue to site", "cancelUrl" => thisPageURL()."return.html", "cancelUrlText" => "Cancel" ),JSON_UNESCAPED_SLASHES);
$xml->hostedPaymentSettings->setting[2]->addChild('settingValue',$retUrl);

$url = "https://apitest.authorize.net/xml/v1/request.api";

    try{
        $ch = curl_init();
        if (FALSE === $ch)
        	throw new Exception('failed to initialize');
        curl_setopt($ch, CURLOPT_URL, $url);
		curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/xml'));
        curl_setopt($ch, CURLOPT_POSTFIELDS, $xml->asXML());
        curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
        curl_setopt($ch, CURLOPT_CONNECTTIMEOUT, 300);
        curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
        curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);
        curl_setopt($ch, CURLOPT_DNS_USE_GLOBAL_CACHE, false );
        
        $content = curl_exec($ch);
        $content = str_replace('xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"', '', $content);

        $hostedPaymentResponse = new SimpleXMLElement($content);
        if (FALSE === $content)
        	throw new Exception(curl_error($ch), curl_errno($ch));
        curl_close($ch);

    }catch(Exception $e) {
    	trigger_error(sprintf('Curl failed with error #%d: %s', $e->getCode(), $e->getMessage()), E_USER_ERROR);
	}

    function thisPageURL() {
     $pageURL = 'http';
     if ($_SERVER["HTTPS"] == "on") {$pageURL .= "s";}
     $pageURL .= "://";
     if ($_SERVER["SERVER_PORT"] != "80") {
      $pageURL .= $_SERVER["SERVER_NAME"].":".$_SERVER["SERVER_PORT"].$_SERVER["REQUEST_URI"];
     } else {
      $pageURL .= $_SERVER["SERVER_NAME"].$_SERVER["REQUEST_URI"];
     }

     $pageLocation = str_replace('index.php', '', $pageURL);

     return $pageLocation;
    }

?>

Thank You,

Ansherina

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Tue, 21 Feb 2017 22:27:55 GMT

Hi @ansherina,

The way your code is constructed in the sample below, the part that adds $commUrl and $retUrl to the XML request isn't putting them in the right place. For example, it's trying to add $commUrl to the first <setting> element, but that's not a "hostedPaymentIFrameCommunicatorUrl" setting. Instead, it's adding a JSON string for the IFrame communicator URL to the hostedPaymentBillingAddressOptions setting, resulting in a malformed setting string. Once our system gets that, it doesn't know what to make of it, so it returns E00001.

If you replaced the XML part of the code with the following, everything would work correctly with that code sample:

<getHostedPaymentPageRequest xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd">
    <merchantAuthentication></merchantAuthentication>
    <transactionRequest>
        <transactionType>authCaptureTransaction</transactionType>
        <amount>20.00</amount>
    </transactionRequest>
    <hostedPaymentSettings>
        <setting>
            <settingName>hostedPaymentIFrameCommunicatorUrl</settingName>
        </setting>
        <setting>
            <settingName>hostedPaymentBillingAddressOptions</settingName>
            <settingValue>{"show": true, "required":true}</settingValue>
        </setting>
        <setting>
            <settingName>hostedPaymentReturnOptions</settingName>
        </setting>
        <setting>
            <settingName>hostedPaymentButtonOptions</settingName>
            <settingValue>{"text": "Pay"}</settingValue>
        </setting>
    </hostedPaymentSettings>
</getHostedPaymentPageRequest>

The XML above has 2 more setting elements and has everything in the right order, so when the code tries to add strings to setting[0] and setting[2], it's adding those strings to the right settings.

By the way, was the XML in your post adapted from some of the things on GitHub, or is it something you copied directly out of one of our samples. If it's something you copied directly, please let us know where from so we can fix it!

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Tue, 21 Feb 2017 22:53:41 GMT

Hi @Aaron,

Thank you very much for the help. Yup i got this from one of your github.

https://github.com/AuthorizeNet/accept-sample-app

- this file : getHostedPaymentForm.php

- Ansherina

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Tue, 21 Feb 2017 22:58:54 GMT

The getHostedPaymentForm.php file appears to have all the right <setting> elements in it, so fortunately we don't have to fix anything there. It appears that you may have just pared it down for your use without updating the array references where the code was trying to modify settings.

No worries, though. If anything else isn't working for you, please let us know! We're happy to walk you through it.

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Tue, 21 Feb 2017 23:01:01 GMT

By the way @Aaron, i also tested the one on your samples and it also gave me the same error.

- Ansherina

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Tue, 21 Feb 2017 23:09:20 GMT

Shoot, that's frustrating, because the same part on the same page works fine for me.

Do you still get E000001 on that page now?

What happens if you try using the default credentials on that page instead of your credentials?

The default credentials are:

	<merchantAuthentication>
		<name>5KP3u95bQpv</name>
		<transactionKey>346HZ32z3fP4hTG2</transactionKey>
	</merchantAuthentication>

Can you copy and post the exact request out of that page that gives you an error?

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Wed, 22 Feb 2017 18:09:37 GMT

Hi @Aaron,

Its weird cause it works using your default credentials, however it still gives me the same error whenever i use mine.

- Ansherina

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Wed, 22 Feb 2017 18:36:51 GMT

Hi Ansherina,

ansherina wrote:
Its weird cause it works using your default credentials, however it still gives me the same error whenever i use mine.

Ugh, that's frustrating. Are you using sandbox credentials or production credentials? Using production credentials to request a token in the sandbox won't work, but I assume it would give a different error than that.

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Wed, 22 Feb 2017 18:49:52 GMT

Hi @Aaron

Im using sandbox credentials.

Re: error: E00001 An error occurred during processing. Please try again.

ferdie33 — Thu, 23 Feb 2017 14:45:52 GMT

I am getting the exact same error. My Merchant Account is currently on TEST mode (it gives me the warning in my dashboard that I'm on TEST, click here to update). I generated a Transaction Key but it giving me the exact same error.

Accept Hosted is supposedly the easiest way of integrating authorize.net this usually takes me 5 mins, but it had gone into 5 days and we are alll really frustrated. I tried live chat but found out those are for merchant support only. Can someone point us in the right direction? I can only run this using your credentials. But when I turn on production it gives me the error.

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Thu, 23 Feb 2017 16:50:13 GMT

Hi @ansherina,

In the "Try It" tab in our API Reference, do your credentials work for the other requests, like the Charge a Credit Card request? I'm trying to find out if it's only the token request that would give you an error.

If so, can you please let me know your sandbox login ID, and I can start digging into it on my end to see what might be different or broken on your account.

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Thu, 23 Feb 2017 16:53:58 GMT

Hi @ferdie33,

You're right, it is supposed to be easy. I'm really sorry that it's not going well for your. Rest assured that whatever the problem may be, whether that's a bug on our side or a documentation issue, we'll get it fixed.

First thing to check is whether you have created the signature key as described in our documentation (In the section heading "Authorize.Net Signature Key"). You said you created a transaction key, and I'm assuming you meant signature key. But if not, I just want to double check that since the transaction key and signature key are two different things.

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Thu, 23 Feb 2017 16:55:19 GMT

Hi @ansherina,

I can't remember whether we checked the signature key on your account. Can you tell me whether you have created the signature key as described in our documentation (In the section heading "Authorize.Net Signature Key"). Note: the transaction key and signature key are two different things.

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Thu, 23 Feb 2017 17:17:12 GMT

Hi @Aaron,

Yes its working on Charge a Credit Card api. Please see below for my credentials and test screenshot.

API Login ID - 4h3WgK9R
Transaction Key - 64xX4Mh5w5hbN8UG

- Ansherina

Re: error: E00001 An error occurred during processing. Please try again.

ferdie33 — Thu, 23 Feb 2017 17:21:53 GMT

Hello Aaron:

Thank you sir for replying, yes I have a signature key, its the longer charactered one as opposed to the transaction key. I'm checking the parameters in the documention but I can't find anything that requires the use of it. (Or maybe I've missed it).

Also, can I just continue replying to you in my own thread? I started downloading the sample-app on github. I've read the php file that has xml parses in it (I'm more familiar using JSON) and it should work eitherway but here I am on my fifth day giving this a shot.

Thanks!

Re: error: E00001 An error occurred during processing. Please try again.

ansherina — Thu, 23 Feb 2017 17:52:41 GMT

Hi @Aaron,

Its working using my sandbox credentials now. I added the signature key in the header as what you have mentioned. Thank you very much for you help.

Regards,

Ansherina

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Thu, 23 Feb 2017 18:12:51 GMT

Excellent! Thanks for the update. Sorry for the trouble.

The signature key will be created automatically in a future release if it doesn't exist, so hopefully others won't have as much trouble.

Re: error: E00001 An error occurred during processing. Please try again.

Aaron — Thu, 23 Feb 2017 18:17:18 GMT

Hi @ferdie33,

I'll follow up in your thread, but you're right that nothing requires the use of the signature key. It simply has to exist in the account for us to use it for encryption on our side.

In the future, the system will auto-create the signature key if it trys to use it and finds that it's not there. However, for now, it's very confusing to people to have to go in and create it themselves.