Implementation of a simple double entry accounting module with a sample deposit account module.
                        <h1>Preloaded Users</h2>
                        <h2>Regular users for simple Sca testing</h2>
                        <li> All users have a pin: 12345, and a static tan: 123456 if they have some Sca methods</li>
                        </br>
                        <b>Marion Mueller</b>
                        <li> Login: <b>marion.mueller</b> </li>
                        <li> SCA: No SCA Method configured. All operations a retuerned with scaStatus EXEMPTED </li>
                        <li> IBAN: <b>DE69760700240340283600</b> </li>
                        </br>
                        <b>Anton Brueckner</b>
                        <li> Login: <b>anton.brueckner</b> </li>
                        <li> SCA: One single sca method configuered. </li>
                        <li> IBAN: <b>DE80760700240271232400</b> </li>
                        </br>
                        <b>Max Musterman</b>
                        <li> Login: <b>max.musterman</b> </li>
                        <li> SCA: two sca methods configured. </li>
                        <li> IBAN: <b>DE38760700240320465700</b> </li>
                        <h2>Multi account user</h2>
                        <b>Carl Schwarz</b>
                        <li> Login: <b>carl.schwarz</b> </li>
                        <li> SCA: one sca method configured. </li>
                        <li> IBAN: <b>DE87760320000000000001</b> </li>
                        <li> IBAN: <b>DE60760320000000000002</b> </li>
                        <li> IBAN: <b>DE33760320000000000003</b> </li>
                        <h2>Users for Multi-Level-SCA testing</h2>
                        <b>All following users share access to one account</b>
                        <li> IBAN: <b>DE32760700240271232100</b> </li>
                        </br>
                        <b>Accountant</b>
                        <li> Login: <b>accountant</b> </li>
                        <li> ScaWeight: 30% </li>
                        </br>
                        <b>Chief Accountant</b>
                        <li> Login: <b>chief.accountant</b> </li>
                        <li> ScaWeight: 60% </li>
                        </br>
                        <b> Supply Chain Manager </b>
                        <li> Login: <b>sc.manager</b> </li>
                        <li> ScaWeight: 10% </li>
                        </br>
                        <b>General Manager</b>
                        <li> Login: <b>g.manager</b> </li>
                        <li> ScaWeight: 90% </li>
                        </br>
                        <b>All following data is relevant for all users in this section</b>
                        <li> PIN: 12345 </li>
                        <li> SCA: One single sca method configured. </li>
                        <li> Login SCA: initiated login process will automatically send the TAN to the configured email and return the scaStatus SCAMETHODSELECTED </li>
                        <li> Payment and Consent SCA: initiated payment or consent sca will automatically send the TAN to the configured sca method and return the scaStatus SCAMETHODSELECTED </li>
                        <li> TAN: configured fake TAN generator will always send the TAN 123456 </li> 
                        <br/>
                        <b>Access Token Scopes</b>
                        <li> if there is no additional scope it is considered that the token has an info access, it is also valid for payment/consent initiation. </li>
                        <li> <b>sca</b>: is received upon payment/consent initiation and extends previous one with ability to perform sca operation. </li>
                        <li> <b>partial_access</b>: is received upon finalizing sca operation with insufficient sca weight for operation execution, further extends previous token. </li>
                        <li> <b>full_access</b>: is received upon finalizing sca operation with sufficient sca weight for operation execution, extends previous token with ability to execute operations like payment, for consent adds validity time as
                        mentioned in requested consent. </li>