CiviCRM Community Forums (archive)

I can have the option of paying not online (implying a delay until payment arrives and registration is complete.
A fair way of handling the situation (from the point of registrant) would be:
Registration with online payment:participant.status_id=1 (registered)
Registration with offline payment: participant.status_id=5 (pending)
 The sublimits for categories are updated accordingly.
Registration that exceed the capacity(registered + pending): participant.status_id=6 (waiting-list)
Registration with offline payment that exceed payment delay limit will receive: participant.status_id=7 (payment_delayed).

Any registration with pending has priority over waiting-list. Those that have registered and are paying within the time delay set, will not be crowded out by later registrants that pay online.
Any registration that exceeds maximum capacity can only be done to the waiting list.
Any registration that has status payment_delayed can, when the payment enters, have status manually changed to registered if maximum is not exceeded. If maximum is exceeded, registration is put to end of waiting list. Eventually money needs to be payed back.

Can I add the participant status 6 and 7?
Where to add the logic I have described here above?
Where to set the payment delay limit (create an option group )?

If registrations of the pending status drop out (not paying within time)