Question : web application design

Hi,

I am designing a web application where visitors can join by filling up a form with their details (name, location, age,...), they also select their membership period (6 month or 12 month) in the same form. When they click submit, I am adding their details to members table in the database and
then send them to PayPal page for payment. this is PayPal basic feature. This feature only send an email to the member and the business owner.

The problem is, sometimes people can not make a successful payment and declined by PayPal. The problem is, I have already added them to the table and I don't want them to be added to the table while they are not considered as a member yet.

I know that I can set up features for authorizing members/non members, but I don't want them to be in the database at all.

What can I do?

Thanks in advance.

Answer : web application design

Ok. Based on those requirements it would be practical to have a second table for applicants. You can insert all applications into that table and she can decide whether to approve applicants and move to the members table.

You did say that you didn't want them in the database at all - so instead of a second table consider storing them in an XML or text file until they are approved.

I would just add the second table for applicants. Usually relational databases have no limits on the number of tables within.