Re: Authorize.net?
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 48422
interpreted = N
texte = Yeah, I know what you're saying, it is just my understanding that thisx_tran_key will be the feature that is required come April. From the AIMdocs at authorizenet.com(http://www.authorizenet.com/support/AIM_guide.pdf):Minimum Requirements for AIMThe following is the minimum set of NAME/VALUE pairs that should besubmitted to the gateway when using AIM for a credit card transaction.FIELD NAME FIELD VALUE x_Version 3.1 x_Delim_Data True x_Login Your Login ID x_Tran_Key Transaction key obtained from the Merchant Interface x_Amount Amount of purchase inclusive of taxThis version of AIM supports Transaction Key Last revised: 1/16/2003 ΖΙ 2003Authorize.Net Corpx_Tran_Key Required Varies by merchant 16 Pass the transaction key obtainedfrom the merchant interface.All I know is that my sites are/have been working for years now (with theonce/twice a year changes that would break the code) and now it is going todrastically change. Bob, you're sending the exact same information that Iam, except via TCPConnect. I've had a couple of support tech's at A/N lookat the code and tell me that it will not fly once the 3.1 required upgradeto AIM/SIM takes effect. I'm just telling you what I've been told. Again,I think we're moving on just to avoid the mess altogether. Someone with theofficial word please set me straight if I'm incorrect.GK> I dunno, I followed their instructions in the aim docs. I didn't dive> too far into all the documentation. If you know something I don't.....>> as far as the password is concerned its not necessary but it doesn't> fail with it. I am not sure if the client had the required password> feature turned on.>> On Wednesday, March 5, 2003, at 06:00 PM, Gary Krockover wrote:>> > Isn't this just a relay response method that is being sent via a> > TCPConnect?> > If so, the relay response method is being phased out come April.> >> > The new AIM/SIM method will require a x_Tran_Key value (which I don't> > see on> > your example) which is a value obtained by the merchant interface and> > then> > returned back to the payment processor as a form of authentication.> > Also,> > it is my understanding that passing the x_password value will no> > longer be> > accepted in AIM/SIM.> >> > I very well could be entirely wrong about this, but instead of the> > nightmare> > that I forsee this thing causing, I think we've decided to move over to> > Verisign PayFlowPro.>> Robert Minor> Director of Internet Services-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list
.To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Yeah, I know what you're saying, it is just my understanding that thisx_tran_key will be the feature that is required come April. From the AIMdocs at authorizenet.com(http://www.authorizenet.com/support/AIM_guide.pdf):Minimum Requirements for AIMThe following is the minimum set of NAME/VALUE pairs that should besubmitted to the gateway when using AIM for a credit card transaction.FIELD NAME FIELD VALUE x_Version 3.1 x_Delim_Data True x_Login Your Login ID x_Tran_Key Transaction key obtained from the Merchant Interface x_Amount Amount of purchase inclusive of taxThis version of AIM supports Transaction Key Last revised: 1/16/2003 ΖΙ 2003Authorize.Net Corpx_Tran_Key Required Varies by merchant 16 Pass the transaction key obtainedfrom the merchant interface.All I know is that my sites are/have been working for years now (with theonce/twice a year changes that would break the code) and now it is going todrastically change. Bob, you're sending the exact same information that Iam, except via TCPConnect. I've had a couple of support tech's at A/N lookat the code and tell me that it will not fly once the 3.1 required upgradeto AIM/SIM takes effect. I'm just telling you what I've been told. Again,I think we're moving on just to avoid the mess altogether. Someone with theofficial word please set me straight if I'm incorrect.GK> I dunno, I followed their instructions in the aim docs. I didn't dive> too far into all the documentation. If you know something I don't.....>> as far as the password is concerned its not necessary but it doesn't> fail with it. I am not sure if the client had the required password> feature turned on.>> On Wednesday, March 5, 2003, at 06:00 PM, Gary Krockover wrote:>> > Isn't this just a relay response method that is being sent via a> > TCPConnect?> > If so, the relay response method is being phased out come April.> >> > The new AIM/SIM method will require a x_Tran_Key value (which I don't> > see on> > your example) which is a value obtained by the merchant interface and> > then> > returned back to the payment processor as a form of authentication.> > Also,> > it is my understanding that passing the x_password value will no> > longer be> > accepted in AIM/SIM.> >> > I very well could be entirely wrong about this, but instead of the> > nightmare> > that I forsee this thing causing, I think we've decided to move over to> > Verisign PayFlowPro.>> Robert Minor> Director of Internet Services-------------------------------------------------------------This message is sent to you because you are subscribed to the mailing list .To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Gary Krockover
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WC2b15 - [HTMLx]...[/HTMLx] problems (1997)
[WebDNA] Comparing 2 MySQL tables (2009)
RAM variables (1997)
notification solutions (1997)
searching a range -still don't get it (2000)
[SearchString] problem with [search] context (1997)
Variable Prices (1998)
[isfolder] and [filename] (1997)
off topic - dna snipets (1997)
Version Question (2000)
WebCat2b15MacPlugin - [protect] (1997)
My web page only... (2003)
FAX orders (1996)
shipCost formula (1997)
[WebDNA] Problem with administration (2009)
Javascript Form Validation (2002)
users.db (1999)
RE: [WebDNA] Build Name for 6.1 (2008)
Protect and Serve (1999)
Setting up shop (1997)