Forum Moderators: buckworks
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!
IMHO, you should avoid sending sensitive data to another site via standard html form post.
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.
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 . . . )