A couple days ago, I got a complaint from a customer who spent over L$20,000 on one of my venders. Initially I thought it was someone trying a con, because when he showed me his transaction log, the timestamp was from a point about 8 hours into the future (and about 17 hours after the alleged transaction). On a whim, I downloaded about a week worth of transactions and searched the specific TN. To my surprise, it was in there. I had received a payment from someone else a few days before (and I don't remember if the dollar amount was the same, though, I suppose I could repeat the process and find out). Since the person had venders of his own, I had him check his TN sequence in his own log. He had several transactions in a row that were numerically out of sequence. Example:

842358829
842356340
817330281 <<--- old number
842354212
842351776

Possibly the buyer pays a vender, but rather than a new TN being created, an old one gets used. The buyer loses his money and the seller never gets it because that transaction is already completed. And, of course, no money event triggered to the vender.

As a commentary on this problem, though, I'm a bit surprised this isn't one of the one or two highest priorities. As one friend put it about the fuss over windlight, "people aren't too likely to remember a pretty sunset in SL, but they WILL remember losing L$50,000." And not only is this a pain for residents, this also moves what has to be a lot of people to the support pages to try to get their money back, and that's a burden for customer support. Either that, or they think they've been robbed, so they file an AR and then the g-team gets them.

If you observe L$ service problems like this in the future, please open a SVC jira for it (technically someone should move this one into the SVC project but I don't have the JIRA-fu to achieve that myself).