Comments on: Authorize.net C# Code

By: Vinoth

Vinoth — Sat, 03 Jul 2010 07:34:56 +0000

Hi,

How to pass the value of track1 (x_track1) to the authorize.net ?
What should be the track1 value?

Please help me asap.

regards
Vinoth

By: Pallavi

Pallavi — Thu, 25 Feb 2010 07:34:45 +0000

Wonderful blog about web development and nice information you have shared here. This post is very helpful and i love reading it. Here i like to share about demellows.com that is very helpful website works for web design and development with advanced features to create an attractive site adding a bit of flash in your presentation so that you can warm up your crowd and bring in the WOW factor. http://www.demellows.com/

By: shiras

shiras — Wed, 17 Jun 2009 06:03:43 +0000

hello can u give sim asp.net integration code

By: Varun

Varun — Fri, 27 Feb 2009 13:21:35 +0000

(TESTMODE) A valid amount is required. (5)
getting this error.
I have turned off my Test account.

hard coded amount=3$.

By: Joel

Joel — Tue, 23 Dec 2008 18:52:23 +0000

Rami,

I’m not trying to sound flip, but apparently you are submitting an invalid value for the amount to Authorize.net. Make sure you aren’t sending blanks, or that the amount is greater than $0, or something along those lines.

You should be able to get more information from the AIM guide you can download from within your Authorize.net account.

By: RamiReddy

RamiReddy — Tue, 23 Dec 2008 11:24:39 +0000

Hi, I implemented this example. Some times it is working properly. some times i am getting the error that “A Valid Amount is required(5)”. Can you explain me reason behind that error?

By: Ravi Vyas

Ravi Vyas — Thu, 21 Aug 2008 07:09:25 +0000

Hello Dave,
This is a great article. Its help me alot.
Now i need to work on refund process.
Please help me for this also.

Thanks & Regards

Ravi vyas

By: Joel

Joel — Thu, 31 Jul 2008 18:32:20 +0000

Great information Dave. Your explanation definitely fits my scenario. The first time I used Authorize.Net was from a non-SSL PHP page that routed the user to an Authorize.Net page for payment. My current project assembles all the information on our page, then submits the request and handles the response on the server.

Thanks for the clarification.

By: Dave Parker

Dave Parker — Thu, 31 Jul 2008 16:30:38 +0000

To answer the question about AIM vs. SIM. With SIM, you use server-side code (ASP/vbscript, ASP.NET/C#/VB.Net, PHP, etc.) which useses your API Login, Transaction Key, Amount, and a couple other params, then it generates some form fields (which are typically hidden) that contain all of this information in an encrypted format. Within this form, you can add fields for the user to enter any other information *except* their cc number, expiration date or CCV code. This form is submitted directly to Authorize.net’s servers where the user can then enter any remaining information required for the transaction. Since no critical CC data is transmitted between the client’s browser and *your* server, using SIM does not require an SSL certificate on your site.

The AIM method has the user enter all of their information, including the CC data in forms on your site and submit to your server. Then server-side code on your server reads the form fields, generates a specially formatted request and performs an HTTP GET to submit the payment request to Authorize.net’s servers and receive the response in one call. Your server-side code then parses the response to determine if it succeeded or failed and to extract other information like the Authorization Code or Transaction ID. From their your server-side code can store the results in a database, send email notifications, display the results on a page to the user, or whatever your requirements deem. However, because the user’s credit card data in transferred between their browser and your server, you need an SSL certificate to enable the browser to encrypt the data before sending.

SSL certificates are no longer super-expensive, though. You can get them as low as $14.99/year at http://www.godaddy.com. (Hint: if you go straight to GoDaddy, the price is $19.99/year for a standard SSL. But if you do a search on “Buy SSL” in google, it displays a sponsored link advertising them for $14.99 )

Ultimately, the decision to use SIM or AIM depends on your requirements. One problem with SIM is that the amount is calculated into the encrypted form field *before* the form is displayed to the user, so if you only have a single page where the user enters their information as well as sets the amount they are paying, using SIM becomes more problematic. For example, I have built several pages for clients that take donations. They are typically non-profits and want to avoid using an SSL certificate and just put up a simple page to enter the amount and submit to SIM. But since SIM requires the amount prior to displaying the form, these pages either end up using AIM or, as in at least one case, the donation form submits to an intermediate page which generates another form with the data and submits that directly to Authorize.net’s SIM form to collect the rest of the user’s information.

Authorize.net also has their new “Simple Payment” service which is supposed to get around this but it still has issues which make it not the right solution for many sites.

I hope this helps clarify things.

Dave Parker
Authorize.net Certified Developer
President/CEO
IT DevWorks, LLC
http://www.itdevworks.com

By: Jrodd

Jrodd — Fri, 11 Jul 2008 21:17:57 +0000

I had to tweak some of the logic in the ExpDate property of the TransactionRequestInfo class where the year was converting to an int and not cross referencing say 9 being greater than 2008. I convert it to string, then substring it to just look at the last two digits of the current year versus the whole year. Might want to tweak that a bit too But other than that, it was quite helpful! Very much, thanks!