topic Re: Required Fields for DPM using ASP.NET in Integration and Testing

Required Fields for DPM using ASP.NET

njsokalski — Sun, 22 Apr 2012 22:43:16 GMT

I have been receiving the following error when attempting to post using DPM and ASP.NET:

(13) The merchant login ID or password is invalid or the account is inactive.

I am currently including the following fields:

x_card_num

x_exp_date

x_card_code

x_amount

x_tax

x_first_name

x_last_name

x_address

x_city

x_state

x_zip

x_ship_to_first_name

x_ship_to_last_name

x_ship_to_address

x_ship_to_city

x_ship_to_state

x_ship_to_zip

x_login

x_tran_key

x_fp_sequence

x_fp_timestamp

x_fp_hash

x_relay_url

x_relay_response

I am posting to the following URL using a developer account:

https://test.authorize.net/gateway/transact.dll

The account is in LIVE MODE. Are there any other fields I should or need to include, or any settings I should check or set? I can't figure out what the problem could be, or what steps I should take next to try to get everything working. Any help would be appreciated. Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Mon, 23 Apr 2012 00:37:03 GMT

The min fields for DPM (is form the documentation - section JAVA)

<form id='secure_redirect_form_id' action='https://test.authorize.net/gateway/transact.dll' method='POST'>
<input type='text' class='text' id='x_card_num' name='x_card_num' size='20' maxlength='16' />
<input type='text' class='text' id='x_exp_date' name='x_exp_date' size='6' maxlength='6'/>
<input type='hidden' name='x_invoice_num' value='<%=System.currentTimeMillis()%>' />
<input type='hidden' name='x_relay_url' value='<%=relayResponseUrl%>' />
<input type='hidden' name='x_login' value='<%=apiLoginId%>' />
<input type='hidden' name='x_fp_sequence' value='<%=x_fp_sequence%>' />
<input type='hidden' name='x_fp_timestamp' value='<%=x_fp_timestamp%>' />
<input type='hidden' name='x_fp_hash' value='<%=x_fp_hash%>' />
<input type='hidden' name='x_version' value='3.1' />
<input type='hidden' name='x_method' value='CC' />
<input type='hidden' name='x_type' value='AUTH_CAPTURE' />
<input type='hidden' name='x_amount' value='<%=amount%>' />
<input type='hidden' name='x_test_request' value='FALSE' />
<input type='hidden' name='notes' value='extra hot please' />
<input type='submit' name='buy_button' value='BUY' />
</form>

And you do NOT pass the x_tran_key

Did you look at the page source when you run the web page on the browser? to make sure everything is pass correctly?

Re: Required Fields for DPM using ASP.NET

njsokalski — Mon, 23 Apr 2012 21:48:09 GMT

I have included all the fields you mention, and removed the x_tran_key field, but still same error. I have also viewed the page source and it is what I expect, but still not success. Any other ideas? Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Mon, 23 Apr 2012 22:58:03 GMT

If and only if this is a test account, post the web broswer page source here.

Re: Required Fields for DPM using ASP.NET

njsokalski — Wed, 25 Apr 2012 19:48:40 GMT

Here is the page source from the page:

The form tag is:

The input fields are:

You will notice that the form tag uses two WebMethods to set the x_fp_timestamp and x_fp_hash fields so that the timestamp is at the time it is submitted. Here is the codebehind code I used for the WebMethods:

Imports System.Web.Services

<ScriptService()> Public Class MPWebServices : Inherits System.Web.Services.WebService

<WebMethod()> Public Function GenerateTimestamp() As String

Return AuthorizeNet.Crypto.GenerateTimestamp().ToString()

End Function

<WebMethod()> Public Function GenerateFingerprint(transactionkey As String, login As String, amount As Decimal, sequence As String, timestamp As String) As String

Return AuthorizeNet.Crypto.GenerateFingerprint(transactionkey, login, amount, sequence, timestamp)

End Function End Class

If you need the rest of the code, I can send it, but these are the lines that seemed like they were the most significant. Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Tue, 24 Apr 2012 01:34:19 GMT

It not working because you can NOT use a production login ID on the test server https://test.authorize.net/gateway/transact.dll

I try it on secure.authorize.net and getting a code (99) https://developer.authorize.net/tools/responsecode99/ with a fake transactionKey, which is expected.

Get a test account https://developer.authorize.net/testaccount/

and test in to https://test.authorize.net/gateway and set x_test_request to "false"

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Tue, 24 Apr 2012 11:27:46 GMT

Another thing.

The way you have for GenerateFingerprint methods on the page is not secure.

The point for the fingerprint is 1)hide you transactionKey, because with both loginID and transactionKey, someone could use your info to test CC#. 2)make sure the amount is not tampered with, since both in on the form, someone change the amount from something like 126.00 to 12.60.

P.S. you have 4 decimal on the amount for the GenerateFingerPrint, it should only be just 2.

Re: Required Fields for DPM using ASP.NET

njsokalski — Tue, 24 Apr 2012 20:08:01 GMT

I am using a test account from https://developer.authorize.net/testaccount/ Is there something that I could possibly need to change in the account that could be causing the code to think it is not a test account? To try it on secure.authorize.net with a fake transaction key, where would I get the fake transaction key? Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Tue, 24 Apr 2012 20:41:06 GMT

It is from a test account? I think you will better off getting a new test account, it sound like it mess up on something on authorize.net side and it is not code related. Maybe one on the MOD will know what to do with that one.

A fake transaction key is just that could be ABCD could be 1234. The point is that with the loginID on secure.authorize.net is returning error code 99 meaning the fingerprint is not valid, but the loginID is valid(not getting error 13).

Re: Required Fields for DPM using ASP.NET

njsokalski — Wed, 25 Apr 2012 18:13:36 GMT

I got a new test account and am using the new Api Login Id and Transaction Key, but still same problem. I also tried a fake transaction key, no difference.

Re: Required Fields for DPM using ASP.NET

Michelle — Wed, 25 Apr 2012 18:29:18 GMT

Hey njsokalski,

Looking at the code you posted above, we were able to determine that the information you are using is from a live account, not a test account. I masked the login ID from your original post as a security precaution.

If you try the code above, with your Transaction Key, but change the post location to the production URL, then it should work fine.

Hope that helps.

Thanks,

Michelle

Developer Community Manager

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Wed, 25 Apr 2012 18:32:50 GMT

njsokalski, Are you posting to the test.authorize.net on your new test account loginID?

Michelle, it also in the fingerprint method The form tag is: <form name="aspnetForm"....

Re: Required Fields for DPM using ASP.NET

njsokalski — Wed, 25 Apr 2012 19:16:52 GMT

OK, here is the new code using the Api Login Id and Transaction Key I was given with my new test account:

Even though the login id and transaction key are from a test account, I tried it with both of the following form tags (notice that the only difference between the two is the action attribute to determine which server it posts to):

Because I just created the test account about an hour ago, and haven't touched any of the account settings, I would think it is a test account right now, right? Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Wed, 25 Apr 2012 19:34:35 GMT

I should have spot it earlier, must not be getting enough sleep.

The problem is it need the name attribute for the input, not just the id.

So every input should be like

after that it work on test.authorize.net

Re: Required Fields for DPM using ASP.NET

njsokalski — Thu, 26 Apr 2012 16:10:04 GMT

Well, I haven't made it to solved yet, but I guess it's good that I've managed to get something other than that error 13. I am now getting the following after submitting:

An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

This transaction cannot be accepted.

And I then receive the following email:

**Please DO NOT REPLY to this message. E-mail developer@authorize.net if you have any questions.

Authorize.Net Developer Center Merchant,

Your script timed out while we were trying to post transaction results to it.

Transaction ID: 0

Transaction Result: This transaction cannot be accepted.

The following message was displayed to the customer:

------------------------------An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

This transaction cannot be accepted.

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

This is when posting to https://test.authorize.net/gateway/transact.dll using my new test account and all the same fields & code I posted in my previous post (with the name attribute included with the id now, of course). I'm not really sure what to do next, because all it really says is "An error occurred while trying to report this transaction", it doesn't give any error codes or details, and I couldn't really find anything from the searches I did for the error message. Are there any common mistakes that cause this error, or somewhere I should be looking to get more details? Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Thu, 26 Apr 2012 16:41:08 GMT

....

It mean your relay response it not working.

Relay Response Basics and Troubleshooting

When I put your relay_url http://www.mckeepottery.com/catalog/Receipt.aspx it getting a 302 then to http://www.mckeepottery.com/catalog/CheckoutError.aspx which is 404

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

Transaction ID: 0

Could be error 99 https://developer.authorize.net/tools/responsecode99/

Change your relay_url to get the raw output https://developer.authorize.net/tools/paramdump/index.php

remember to add that to your merchant account valid relay url list.

Did you add the attribute name="???" to all the inputs e.g. name="x_fp_timestamp", name="x_fp_sequence", etc

Re: Required Fields for DPM using ASP.NET

njsokalski — Fri, 27 Apr 2012 00:29:18 GMT

OK, on the Relay Response Basics and Troubleshooting page it says:

It instructs the payment gateway to return transaction results to the merchant using an HTML form POST to a specified URL on the merchant's Web server. A script or program at the URL can be used to create a custom receipt page using the transaction information. The custom receipt page is then relayed back to the customer's browser. Relay Response does not redirect the end user back to the merchant’s server, but relays the page content to the end user instead of displaying the Authorize.Net default receipt page.

Wouldn't "a specified URL on the merchant's Web server" mean http://www.mckeepottery.com/catalog/Receipt.aspx in my case? Is it going to http://www.mckeepottery.com/catalog/Receipt.aspxand then giving the error? How can I see the 302 and 404 errors you mention? I also tried changing the x_relay_url field as you mention (including in the valid relay url list), but it didn't help. Any suggestions? Thanks.

(NOTE: I did add the name attribute to all of my fields)

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Fri, 27 Apr 2012 00:51:42 GMT

1)your site DPM form post to authorize.net

2)authorize.net process and post the result (in code) to your relay response page. In code mean something like http://msdn.microsoft.com/en-us/library/debx8sh9.aspx

3)in your relay response page, check for approve or decline, save the post data or back to DPM form. Then, if approve, using javascript to redirect or a javascript form post to the final receipt page that will display to your customer. If you don't use javascript, the URL will stay at authorize.net

The 302 and 404 was from using firebug with firefox, or fiddler with IE, right now if I go to straight to the receipt.aspx it showing error 500 Parameter count mismatch.

When you change the x_relay_url to https://developer.authorize.net/tools/paramdump/index.php

didn't it post all the result data? Which should all the fields in http://developer.authorize.net/guides/AIM/Transaction_Response/Fields_in_the_Payment_Gateway_Response.htm

which you can look up the response reason code and text in http://developer.authorize.net/guides/AIM/Transaction_Response/Response_Reason_Codes_and_Response_Reason_Text.htm

Re: Required Fields for DPM using ASP.NET

njsokalski — Fri, 27 Apr 2012 15:46:56 GMT

I'm confused about what I can and need to do in my relay response page (Receipt.aspx). If I'm supposed to use Javascript, wouldn't it need to be open in the user's browser (but obviously it isn't). Is there anywhere that I can see an example of a basic ASP.NET relay response page? Thanks.

Re: Required Fields for DPM using ASP.NET

RaynorC1emen7 — Fri, 27 Apr 2012 18:06:27 GMT

Do a simple Receipt.aspx, just display all the post param or just a just any text to the screen and you will see what they mean by it relay your page content.

Also, I not sure if you knew this, but you will need to set EnableViewStateMAC = false on both your DPM page and the relay response page or set the machinekey on your web.config