Why am I getting this result using AIM cold fusion???

[rlichner]

Using the sample code provided in the AIM and am getting this return response:

3|1|103|This transaction cannot be accepted...

I am using the API login ID and Transaction Code provided by Authorize.net and have even gone as far as getting a new transaction key.

Any ideas?

Thanks!

[RaynorC1emen7]

3

103

This transaction cannot be accepted.

A valid fingerprint, Transaction Key, or password is required for this transaction.

Can you see/debug post data before sending to authorize.net?

[rlichner]

I hard-coded the test page to get it working before trying to dynamically populate values because I didn't want to have to figure out what went wrong with everything there.

At this point, I'm using the exact code provided by authorize.net. At first I didn't use the <cfsetting enablecfoutputonly="true">, but added it after I first started having problems to make sure that the data getting sent over in the cfhttp post was clean.

Is't pulling error message 103 which is an invalid transaction key, fingerprint or password. As far as I know, there's no fingerprint or password code in the sample provided by authorize.net.

Do you think thats the problem? If so, how do I generate a fingerprint? Is the password the API Login ID?

Thanks!

[RaynorC1emen7]

Just want to make it clear, the only thing you change on the sample code sample.cfm is put your loginID and transactionKEY, and you getting 103 error? make sure there are no spaces in transactionKey.

[rlichner]

That's the deal.... I even got a new transaction key because that's what support told me to do.

I'm also sending the data to https://test.authorize.net/gateway/transact.dll

Do I have to do anything to activate the test account other than login?

Just to make sure - the x_login field is populated with the API Login ID provided at signup, right?

[RaynorC1emen7]

Do I have to do anything to activate the test account other than login?

No

Just to make sure - the x_login field is populated with the API Login ID provided at signup, right?

Yes

Copy the following link and change the [yourID] and [yourKey] and run it in a browser and see if this work

link

[rlichner]

That works.... but it still doesn't work on the page.

Here's the exact code I'm using:

---------------------------------------------

<cfsetting enablecfoutputonly="true">

<!--- test the card with authorize.net to make sure it is valid --->
<cfhttp method="POST" url="https://test.authorize.net/gateway/transact.dll">
<cfhttpparam type="FORMFIELD" name="x_login" value="#login#">
<cfhttpparam type="FORMFIELD" name="x_trans_key" value="#transkey#">
<cfhttpparam type="FORMFIELD" name="x_delim_data" value="TRUE">
<cfhttpparam type="FORMFIELD" name="x_delim_char" value="|">
<cfhttpparam type="FORMFIELD" name="x_relay_response" value="FALSE">
<cfhttpparam type="FORMFIELD" name="x_type" value="AUTH_ONLY">
<cfhttpparam type="FORMFIELD" name="x_method" value="CC">
<cfhttpparam type="FORMFIELD" name="x_card_num" value="4111111111111111">
<cfhttpparam type="FORMFIELD" name="x_exp_date" value="0115">
<cfhttpparam type="FORMFIELD" name="x_amount" value="1.00">
<cfhttpparam type="FORMFIELD" name="x_description" value="Card Verification">
<cfhttpparam type="FORMFIELD" name="x_first_name" value="John">
<cfhttpparam type="FORMFIELD" name="x_last_name" value="Doe">
<cfhttpparam type="FORMFIELD" name="x_address" value="1234 20 Street">
<cfhttpparam type="FORMFIELD" name="x_state" value="WA">
<cfhttpparam type="FORMFIELD" name="x_zip" value="98004">
</cfhttp>

[RaynorC1emen7 · Accepted solution]

<cfhttpparam type="FORMFIELD" name="x_trans_key" value="#transkey#">

Should be x_tran_key

[rlichner]

That was it. Thank you , thank you, thank you!