How to normalize a lookup table containing NULL? - or should I bother?
Perhaps a better policy:


When registering a user, store the fee charged into the user's history.
Derive the fee from some business logic that may or may not be stored in a database table.


Note how this policy freezes the fee as soon as it is billed.  This is safer than having it in some other table that might accidentally be changed for unrelated reasons.