Implementation of a simple double entry accounting module with a sample deposit account module.
                        <h2>Preloaded Users</h2>
                        <b>Marion Mueller</b>
                        * Login: <b>marion.mueller</b>
                        * PIN: 12345
                        * SCA: No SCA Method configured. All operations a retuerned with scaStatus EXEMPTED
                        * IBAN: <b>DE69760700240340283600</b>
                        </br>
                        <b>Anton Brueckner</b>
                        * Login: <b>anton.brueckner</b>
                        * PIN: 12345
                        * SCA: One single sca method configuered.
                        * IBAN: <b>DE80760700240271232400</b>
                        * Login SCA: initiated login process will automatically send the TAN to the configured email and return the scaStatus SCAMETHODSELECTED
                        * Payment and Consent SCA: initiated payment or consent sca will automatically send the TAN to the configured sca method and return the scaStatus SCAMETHODSELECTED
                        * TAN: configured fake TAN generator will always send the TAN 123456
                        </br>
                        <b>Max Musterman</b>
                        * Login: <b>max.musterman</b>
                        * PIN: 12345
                        * SCA: two sca methods configured.
                        * IBAN: <b>DE38760700240320465700</b>
                        * Login SCA: initiated login process will return the scaStatus PSUIDENTIFIED and a list of sca methods for selection
                        * Payment and Consent SCA: initiated payment or consent sca will return the scaStatus PSUAUTHENTICATED and a list of sca methods for selection
                        * TAN: configured fake TAN generator will always send the TAN 123456
                        </br>
                        <b>Users for Multi-Level-SCA testing</b>
                        <b>All following users share access to one account</b>
                        * IBAN: <b>DE32760700240271232100</b>
                        </br>
                        <b>Accountant</b>
                        * Login: <b>accountant</b>
                        * ScaWeight: 30%
                        </br>
                        <b>Chief Accountant</b>
                        * Login: <b>chief.accountant</b>
                        * ScaWeight: 60%
                        * Supply Chain Manager
                        * Login: <b>sc.manager</b>
                        * ScaWeight: 10%
                        </br>
                        <b>General Manager</b>
                        * Login: <b>g.manager</b>
                        * ScaWeight: 90%
                        </br>
                        <b>All following data is relevant for all users in this section</b>
                        * PIN: 12345
                        * SCA: One single sca method configured.
                        * Login SCA: initiated login process will automatically send the TAN to the configured email and return the scaStatus SCAMETHODSELECTED
                        * Payment and Consent SCA: initiated payment or consent sca will automatically send the TAN to the configured sca method and return the scaStatus SCAMETHODSELECTED
                        * TAN: configured fake TAN generator will always send the TAN 123456
                        </br>
                        <b>Registration and Login Process</b>
                        You can use the User Login Endpoint to gain a login token (or an access token in case of exemption).
                        Then use the access token with the prefix 'Bearer ' to Authorize on this ui before using Select Sca Method and/or Submit Auth Code.
                        </br>
                        <b>Endpoints</b>
                        * Register: <b>/users/register</b>
                        * Login: <b>/users/login</b>
                        * Select Sca Method: <b>/users/{scaId}/authorisations/{authorisationId}/scaMethods/{scaMethodId}</b>
                        * Submit Auth Code: <b>/users/{scaId}/authorisations/{authorisationId}/authCode</b>
                        </br>
                        <b>Access Token Types</b>
                        * <b>LOGIN</b>: login token are only issued during the multiphase login process and can not be used to access other resources.
                        * <b>DIRECT_ACCESS</b>: access token issued to a user after a successful login (one or two phases). Can be used to access resources
                        * <b>DELEGATED_ACCESS</b>: delegation token are issued as a result of a successful consent grant or payment authorization. A delegation token issued as result of a succesful payment authorisation can be used to access the corresponding transaction. Delegation token are general stored in the consent database and used to authenticate TPP requests with the core banking system.