EDIT: Either AspNetUsers or a new Users table would still have to have a one-to-many relationship with a Salutations table (Mr, Mrs, etc) and a Payments table.
I don't know your application requirements and can only make general recommendations based on past experience. If you do not need a one to many relationship then storing the user information in the AspNetUser table is fine.
For example, payments commonly consist of a billing and shipping address. I don't know if shipping applies to your application.