Forum Moderators: buckworks

Message Too Old, No Replies

authorize.net AIM integration

         

singlehouse03

12:00 am on Mar 27, 2009 (gmt 0)

10+ Year Member



I need to integrate authorize.net with my site.And I take advanced integration method(AIM) becuase payment form is on my server,not authorize.net.

I read AIM and SIM developer guide.They have a lot of similiarities.
In form,both
action=https://secure.authorize.net/gateway/transact.dll

So how authorize.net can tell one specific form is calling AIM not SIM?Any setting inside my authorize.net mechant acct or....?

Thanks in advance!

rachel123

1:28 am on Mar 27, 2009 (gmt 0)

10+ Year Member



AIM does not use a form post to their servers. For AIM the form posts to an API script on your site, which then processes and formats the data and securely transmits it to authnet. Authnet provides sample code for several languages.

IMHO, you should avoid sending sensitive data to another site via standard html form post.

jwolthuis

9:09 pm on Mar 27, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



In both cases, the data is securely transmitted via a secure SSL channel. There is no security advantage that one method holds over another.

The AIM method offers more flexibility in designing your payment methods webpage, as the customer input task is logically separated from the data submission task.

rocknbil

3:44 pm on Mar 28, 2009 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Welcome aboard singlehouse03, the process is a little complicated but here is the basic method for AIM (For those reading, this is Advanced Integration Method, as opposed to Simple.)

As said, make sure this is in a SECURE location on your server, https, or it will not work. AIM will reject any post from non-ssl.

1. Submit form to YOUR script

2. Your script uses cuRL to silently post to A.N.,

3. Your script receives response from A.N. Depending on the response, you either a) return an error to the browser, or b) update database, send emails, etc.

4. Return response to the browser, which in one scenario may be directly to the member control panel of a paid subscription service.

Note the important part here is cURL. Curl allows you to post to the server and "listen" for a response. The overall effect is that the user never leaves your site.

Dig though their documentation. They have sample code for ASP, PHP, and I think even perl (they used to anyway . . . )