Multiple Tables or multiple fields
===

What would be the best way to do this and why?  

Here is a quick look at a part of my database design, I'm looking for the best way to organize this data.

    "Leads" has many "Students", Leads has many "Contacts"

    "Students" belongs to "Leads" and belongs to "People"
       id, person_id, lead_id

    "Contacts" belongs to "Leads" and belongs to "People"
       id, person_id, lead_id

I want to be able to signify which contact is going to be a "payer" and if a contact would be the primary contact or not.

I thought originally I would add two more tables like this:

    "PrimaryContacts" belongs to "Contacts"
       id, contact_id
    "Payer" belongs to "Contacts"
       id, contact_id

Then I realized it seems kind of over kill to add two more tables with something I can easily represent in the initial Contacts table like this

    "Contacts"
      id, person_id, lead_id, type, payer

Then I could have type be 1 or 2, meaning primary or secondary, and then the payer field would be 1 or 2 meaning they either are paying or they aren't.

Is there a benefit of doing it one way or the other or does it matter at all?

Thanks!
 