The way its currently setup is that they would login using their account number and billing zip. The following page will show the customer how much is currently due and there is an option to make a payment... so a session is started. Your suggestion I think would work if I just had the customer put in the amount they owe and, when the payment is submitted, I could verify the account with the account ID and zip.
On Wednesday, May 15, 2013 11:32:11 AM UTC-4, Anthony wrote: > > Do you even need the Auth system for the customers? Can't you just have an > accounts table in the DB and verify the account ID and zip when a payment > is made? > > Anthony > > On Wednesday, May 15, 2013 11:14:52 AM UTC-4, Andre Kozaczka wrote: >> >> Is there a way to create two different login/authentication systems for >> different groups? >> >> For example, I'm creating an application for Businesses and their >> Customers. Businesses would have a login and would be able to access >> information for all their customers, run reports, etc. Under the same >> application I wanted to allow Customers to 'login' and make payments. The >> Businesses would have the typical login (email and password - they would >> have to register for an account) but for Customers, I want something >> simpler (really, it's only to verify they are paying for the right account) >> where I would only ask for their account number and billing zip to allow >> them to make a payment. Is this possible to do under one application? As >> an alternative, I may simply create another application for Customer use >> and share databases between the two. >> >> -Andre >> > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
