At 2/14/01 10:29 AM, Scott Allan wrote:
>Renewal orders are being re-engineered to be actual orders; this will allow
>for better tracking. In addition to this, they will respect the "process
>orders immediately" flag. This functionality is in QA right now (should
>show up reasonably soon).
May I suggest/request that there be a separate flag?
The reason we (and probably most RSPs) don't process initial orders
immediately is that these people are brand new customers, and therefore
we want to check them with a human eye towards potential fraud.
However, in the case of renewals, we know that their order a year ago
wasn't fraudulent. Therefore we trust them a great deal more and are
willing to process their orders immediately.
Much better, of course, would be the ability to set the flag individually
for each order from the script. Then we could each do what we wanted on
individual orders -- for example, if it's an order for only one year, and
the credit card AVS matches, and we've processed less than five orders in
the last few hours, I might want to process it right away. But if it's a
ten-year order, or our registration volume is suddenly unusually heavy,
or the credit card info doesn't match, I might want someone looking at
the order and giving the customer a call.
This could be implemented in a backwards compatible manner. You could add
a parameter to the "renew" and "order" XCP messages that, if present,
overrides the default RSP setting. If this parameter is not passed, the
default setting is used.
This sounds like a pretty easy change if you're messing with this stuff
anyway, and would address a longstanding concern. Just my 2¢.
--
Robert L Mathews, Tiger Technologies
