I have a pricing table, something like this:
Scenario #1: Home Page
Actually I'm using one page layout for website, something like this:
and here is an option to put pricing table at the end of the page. Readers after reaching at the end of the page (actually by scrolling it and read all awesome features of our service) start to choose their desired plan and after that they redirects to registration wizard page, and start to complete their registration fields.
"hey, wait! I forgot what plan I choose in previous page." -The User
So, In the first step of the wizard I must put this pricing table again and highlight the plan he choose in home page.
After completing it, the confirmation email sent to their inbox. And then after confirming their email address they will asked for paying the invoice via paypal or any other banking services out there.
"come on! Its 20.99$. No way ! I wanna change my plan to 5.99$." -The User
So, There is also an option in that page that let the user to change his/her decision and choose another plan. And "again" I must put this pricing table to that page, to let the user to change its decision for third time !
Scenario #2: In payment time
There is also another option to put a beautiful register now! image at the end of my one page layout, and then by clicking the image it will redirects user to registration wizard page. And then completing the registration fields and then confirm email address and then he will asked for choosing the desired plan.
just choose and pay !
Scenario #3: Pay when needed
After registration, The User will start using the software, and when he clicks any links on the user's dashboard page he will asked for payment and then the pricing table will shown for him/her.
What do you think about these scenarios ? Which one is better for a web service ? Any other scenario would be most welcome.