Authorize.net will pass back to you any argument you send them. We assign
the userreferenceargument a name in the form that posts to them and then
reassign it when it comes back to us.
I'm not sure about hard coding the full return path - as I understand it all
their new security system requires is the domain name you're posting from.
I just went through these changes so feel free to contact me off list if you
want to further discuss how we got it all to work.
-Cornelius
on 6/4/02 8:43 AM, Troy Sosamon at [EMAIL PROTECTED] wrote:
> For security, you could put it in both places and check to make sure they
> are they match before you process the form results.
>
> Troy
>
> ===== Original Message from [EMAIL PROTECTED] at 6/04/02 9:04 am
>> Hello, Troy Sosamon! On 6/04/2002 8:47 AM -0600, you wrote in whole or part:
>>> Beverly
>>>
>>> Try putting the ?<@userreferenceargument> tag at the end of the URL in the
>>> form tag.
>>
>>
>> Thanks, Troy. Therein lies the rub. I must *hard-code* the FULL return path
>> on the
> authorize.net site. This is their new security...
>>
>>
>> :^(
>>
>> Beverly
>> ________________________________________________________________________
>> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
>> with unsubscribe witango-talk in the message body
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
