I am at 1.3.8a. (This is our busy season and upgrade is planned for upcoming down time.)

We are a club which holds running races open to the public. Our "products" are races for which people are purchasing registration. There are a number of attributes associated with a registration, such as gender, name, address, shirt size, etc. (We don't use the customer fields because one person in a family tends to register others.)

This is what is happening. Person A selects the race product, fills out the attributes, adds to cart, confirms, pops over to PayPal and pays, comes back and completes the order. No problem.

At some point a little later (or sometimes they are on the site at the same time) Person B also selects this race, fills out their attributes, and adds to cart. But when they go to the confirm screen, the attribute information shown is for Person A. A number of people don't even look at this and go right through the payment process and pay for a registration of the wrong attributes for them. This gets us into the hassle of refunds, getting in touch with them to redo registration, etc.

This all makes our payment collections site look a little hokey and we are getting people expressing fears about the security of their data and purchase information.

This seems to happen more when the site is a little busy. We had 85 registrations yesterday and I had to refund 8 of them and advise the person to go again. I also fielded a number of calls from people who spotted the problem and had to explain what to do. And then there were probably a few people who figured out how to fix it themselves.

Can someone explain what is happening and how to fix it?

Thanks!