MiniVend Akopia Services

[Date Prev][Date Next][Thread Prev][Thread Next][Minivend by date ][Minivend by thread ]

Re: Changed it: Synchronizing order number, Cybercash



The problem with using the order number is that the order number is incremented
at the end of the checkout process. If you simply try to get the number and
add 1
to it to pass to Cybercash, then everything is great right (as shown
below)? Wrong,
what happens when you have 2 customers at once? One may complete the sale
using the order number that another was already trying to process at Cybercash.
So you then have to hack it so that it does not increment the order number
at the
end of the process, but instead before Cybercash. Thats fine as long as
that is the
only way you can order. But then you will find you are missing order
numbers because
some of those credit cards were declined. Then you begin to wonder if maybe
there
were good orders and they just did not get to you etc...

In the end it is up to you, but think carefully about multiple customers and
checkout methods, and where the increment takes place.

KC (Kyle Cook)

At 07:59 PM 9/5/99 -0400, you wrote:
>******    message to minivend-users from Aaron Rubin <brubin@idt.net>     
>******
>
>I'm not sure why cybercash was given a date/time ID instead of the OrderID,
>but if you'd like to have them both be the same:
>
>In 3.14: At line 218 of order.pm (or there abouts) change "$orderID = ...;"
>to "$orderID = $::Values->{mv_order_number} + 1;"
>
>--Aaron
>
>
>
>-
>To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
>email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
>Archive of past messages: http://www.minivend.com/minivend/minivend-list


http://www.invisio.com 
Web site design, database driven sites,
and shopping cart programming. 
Great sites, value priced!



Search for: Match: Format: Sort by: