This section examines the on-line payment process from the perspective of someone registering for a class, program or event.
The appearance of payment screen will of course vary depending on how the event is setup. We've chosen in the example below to model a reasonable complex class registration example. In this example we have made on-line payment "Mandatory", but have provided an option in the payment setup for a registrant to pay a deposit of $75.00 to secure their space in this program.
We proceed with the choice by select "Submit Payment Choice". We've intentionally chosen a payment example where we are registering very late for the session to show how late registrations, pro-rated fees and deposit policies work together. This program actually started on May 8th, but the date of our registration is August 7th. Note that the system gives me a two week grace period automatically allowing me to select class start dates of August 7th, 14th or 21st. We do not want to allow later start dates, otherwise we are tying up slots and making them unavailable to paying customers.
Once we select August 21st as our preferred start date, we see the payment confirmation screen generated below:
A |
The $300.00 is reflecting the cost as setup in the event definition - in this example we've expressed the cost as a cost for the entire program vs. a "cost per class" which is alternate way of expressing the price. |
B |
If pro-rated registration is enabled, and we've selected a late start date within the allowable late registration window, the number of weeks from the start of classes to the late start date is reflected here. Note that for later registration the system will not expose late registration options until the regular class start date has come and gone. This is because we want to maximize attendance and revenue for our classes. |
C |
The discount associated with the missed classes is then reflect here. In our simple example we've missed 15 weeks @ $10.00 per week with a "linear" discount policy - therefore $150.00 is deducted from the fee |
D |
This is the net amount owing after factoring the late registration and the site pro-rate policy - in this example $150.00 |
E |
To add more complexity we've allowed the user to make a deposit for this event which the user has elected to do - this means that while the amount "due" for the class (prior to additional fees) is $150.00, we are going to allow registration to proceed with a $75.00 deposit. |
F |
NeatClubs.COM can validate against central registration databases and conditionally assess fees or discounts depending on member status. In this example we detect that this registrant is not found and we levy an additional membership fee while making it user-selectable whether this fee should be paid or not. |
G |
Just for illustration purposes, we might have another rule that offers a discount of a member were found in a central database - in this case of course the rule would not apply and no discount is offered. |
H |
We can also levy taxes (not shown) and additional administrative fees calculated based on the baseline price as shown here. |
I |
This field reflects the total amount that we are requesting this registrant to authorize. |