Demo Users

As a part of our commitment to providing a seamless experience for our clients, we offer demo users that allow you to explore the functionalities of our banking module without the need for real bank accounts. These demo users are designed to simulate real banking scenarios, enabling you to test and understand how our system works in a risk-free environment. Please note that the demo users are intended for testing and demonstration purposes only. As such, these users connect towards our own mock bank implementation, which simulates the behavior of real banks but does not connect to any actual financial institutions.

Available Demo Users

We currently offer the following demo users:

Demo User Name	Description
persondemo	Typical demo user for personal banking scenarios. This user simulates a standard individual bank connection with some standard accounts.
companydemo	Typical demo user for business banking scenarios. This user simulates a business bank connection that contains some business accounts.
depot01	Typical demo user for investment banking scenarios. This user simulates an investment account that contains some example securities.

Password combinations

While we provide different demo users for various banking scenarios, the password can define specific behaviors for the demo users, allowing you to test different scenarios and functionalities. The following table outlines the available password combinations and their corresponding behaviors:

Password	Behavior
654321	A TAN must be entered (123456)
999999	Simulates an incorrect password
999991	Simulates a decouples TAN process
999992	Simulates a photoTAN challenge (twice)

Please note that the above password combinations are specific to our demo users and are designed to trigger specific behaviors for testing purposes. These combinations may not reflect real-world banking scenarios and should be used solely for testing and demonstration purposes within our system. Also, if you enter no password at all or just a random combination of characters, the login will succeed, but without any challenge.

Testing connect flows with demo users

To test the connect flows with our demo users, you can follow these steps:

1. Use the Create Connect User Session endpoint to initiate a connect session for the desired demo user.
2. From the bank search UI, search for our mock bank (e.g., "Fino Bank") and select it.
3. When prompted for credentials, enter the demo username (e.g., persondemo) and the desired password from the combinations outlined above.
4. Follow the prompts to complete the connection process, including any additional authentication steps based on the password behavior you have chosen.
5. Once the connection is established, you can explore the functionalities of the banking module using the connected demo user account, allowing you to test various features and scenarios without the need for real bank accounts.

Testing money transfer with demo users

Of course, you can also test the money transfer functionalities with our demo users. To do so, you can follow the steps mentioned above to connect a demo user account, and then use the Create Money Transfer endpoint to initiate a money transfer from the connected demo user account. However, for the demo money transfer to function properly, you need to use a password that triggers a challenge (e.g., 654321) during the connection process of the demo user account.

Force Consent Expire

This parameter allows you to simulate an expired consent in order to test different error and edge-case scenarios.

Behavior

To use this feature, you must authenticate with one of the available demo users listed above and use the PIN 654321.

Depending on the value of triggerChallenge, the endpoint Create Synconization Session behaves as follows:

• triggerChallenge = true
  • The endpoint responds with HTTP 451
  • The response indicates that a user challenge (e.g., re-authentication) is required
• triggerChallenge = false
  • The endpoint responds with HTTP 206 (Partial Content)
  • The related process status is set to SYNC_FAILED if you call the Get Connect User Session Status endpoint

Asynchronous Behavior

In addition to the immediate API response, an asynchronous webhook is triggered:

• Event type: ubasyncerror
• Purpose: Simulates an error during asynchronous processing

Use Cases

This feature is particularly useful for:

• Testing consent expiration scenarios
• Simulating synchronization failures
• Validating error-handling and retry logic
• Verifying webhook processing