Reply
Member
Posts: 1
Registered: ‎06-07-2011
Accepted Solution

AIM transaction question

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


Accepted Solutions
Solution
Accepted by topic author syndesis
‎08-21-2015 01:58 AM
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: AIM transaction question

If it submit thru form post to transact.dll is SIM. If the form post to your server code and you pass the info to transact.dll it AIM.

View solution in original post


All Replies
Solution
Accepted by topic author syndesis
‎08-21-2015 01:58 AM
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: AIM transaction question

If it submit thru form post to transact.dll is SIM. If the form post to your server code and you pass the info to transact.dll it AIM.