Well, they won't match if the CCard place isn't returning ALL values...
And that's what's happening. The UserRef is gone, the order cannot be completed, the
client is p.o.'d...
We have a 'trap' that should return the UserRef as another form parameter, but even it
doesn't always get passed back.
Thanks,
Beverly
Hello, Troy Sosamon! On 6/04/2002 9:43 AM -0600, you wrote in whole or part:
>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
