That is what eventbrite gets, and I think we'll need the same info.
We shouldn't assume the billing address is their actual address, and should let people add another address if there's a discrepancy there. (if they choose not to geolocate, we'll need a working address to show them buses/events close to them)
so the data needed for a new user is
- first name
- last name
- date of birth
- address (if different from billing)
- billing address
- CC info
- number of seats
- additional names/birthdays
for an existing user we should have most things saved/cached, so we'll only need:
- number of seats
- (additional names/birthdays)
##next steps I'll need to get more familiar with stripe to see how they cache CC info