[ic] Preventing duplicate real-time changes using PayFlo Pro

Mike Heins interchange-users@interchange.redhat.com
Thu May 23 12:25:00 2002


Quoting Bill Carr (bill@worldwideimpact.com):
> It turns out that the duplicate charge never resulted in an interchange
> order. Just a guess but maybe interchange never got a response from
> versign and the user hit place order again. In any case I think this was
> a rare occurrence and I am not going to worry about it much.

This can happen if you have the charge operation in your profile
and it uses some amount that is not derived from [total-cost].

You can put in a fail-safe if you want, by setting a Scratch variable

	[set placed_order]1[/set]

at time of order completion then asking for a confirmation of a second
order in the same session.

-- 
Mike Heins
Perusion -- Expert Interchange Consulting
phone +1.513.523.7621      <mike@perusion.com>

I have a cop friend who thinks he ought be able to give a new ticket;
"too dumb for conditions".