modify schema and DB to accept LEVEL TWO users banking data

[islandbitcoin]

When accepting user data (business address and banking information - account # ) we will store this data on the same record that is kept on the flash backend.

@brh28 what would be best practice in this use case?

[brh28]

Overall, I need some more context here to better understand what exactly a level 2 account implies. That said, I do see "level" is already a defined in the AccountSchema as an enum of [0, 1, 2] (see here), so to my current understanding, this shouldn't require structural changes to the schema.

More generally, I think we still have a quite limited understanding of the data model. Up til now, this hasn't been a problem as we haven't made any significant changes to Galoy, but as we move forward with some of these featuers on the roadmap, getting a better understanding of the data model will be quite important. I'd suggest we create a task to document the data model as it stands today and can be used in conversations moving forward.

Resource: Mongo data modeling