AIM transaction question

[swothapepi]

Hello,

I'm updating some old code and have a question.  The existing (perl) code uses the old SimLib function "GenerateInspFP" to generate a hash key which is included with each transaction using x_fp_hash.  The form is then directly submitted to the transact.dll URL.  I was working on updating it to use the Digest module but I don't see anything in the guide or sample code that suggests the x_fp* fields are supported by AIM.  Are these fields ignored?  If so, how do I ensure that x_amount hasn't been altered by a user before the form is submitted?  (Or is this old code doing something entirely wrong?)

Thanks

[swothapepi]

Hello,

I'm updating some old code and have a question.  The existing (perl) code uses the old SimLib function "GenerateInspFP" to generate a hash key which is included with each transaction using x_fp_hash.  The form is then directly submitted to the transact.dll URL.  I was working on updating it to use the Digest module but I don't see anything in the guide or sample code that suggests the x_fp* fields are supported by AIM.  Are these fields ignored?  If so, how do I ensure that x_amount hasn't been altered by a user before the form is submitted?  (Or is this old code doing something entirely wrong?)

Thanks

[TJPride]

AIM is submitted directly from your site to Authorize.net. How exactly would a customer change the amount? Are you sure you're not mixing up AIM and SIM?