Let me be more clear -- My "going a different way" suggestion was, for the regular existing real time order process:
1. User registers/requests event seats, just as happens now. EME Unique Number generated, just as happens now. But #_BOOKEDSEATS does NOT increment yet.
2. User then clicks the provided PayPal link and immediately pays for seats (via PayPal or new method). EME Unique Number switches to PAID, just as happens now.
3. Only THEN, with the EME Unique Switched to PAID, does the #_BOOKEDSEATS get incremented.
This way we could track "registered" (requested) spots versus actual confirmed/paid spots. This behavior for #BOOKEDSEATS could be controlled by a new "require payment confirmation" toggle WITHOUT having to deploy a separate #_CONFIRMEDSEATS counter, which was my original thought.
As to the "asynchronous payment" idea, my related wishlist item was having a few variables (either replacing or in addition to #_BOOKEDSEATS) that would tell not only who had "registered" for (requested) the event but also who had PAID (or been approved for) the event. Right now EME seems to treat every unconfirmed request as reducing the number of available seats. This is not realistic for many purposes.
The asynchronous payment idea is similar to GuiltyCol's request #4 at PayPal Integration Feedback
Ideally the email confirmation should contain a url that allows the user to return and pay at some point in the future (the url of the Thank You page in (3) above would do...."
Anyhow, just food for thought for your future road map.