Mock users
User credentials for testing. Use different credentials to test different responses.
These credentials can be used with the mock bank for testing successful transactions and different errors.
| Username | Password | Behaviour |
|---|---|---|
"john""john1""john2"... "john100" | "doe""doe1""doe2"... "doe100" | Successful authentication. Example data available via Data API. Connection extend will return {action_type: "authentication_needed"}. |
"john""john1""john2"... "john100" | "iban""iban1""iban2"... "iban100" | Successful authentication. Example data available via Data API. The iban field of the accounts payload will be a different valid IBAN for each account.Connection extend will return {action_type: "authentication_needed"}. |
"john" | "eternal" | Successful authentication. Example data available via Data API. Connection extend will return {action_type: "no_action_needed"}. |
"error.account_permanently_locked" | "error" | Successful authentication. All calls to Data API will fail with account_permanently_locked. |
"error.account_temporarily_locked" | "error" | Successful authentication. All calls to Data API will fail with account_temporarily_locked. |
"error.internal_error" | "error" | Successful authentication. All calls to Data API will fail with internal_error. |
"error.provider_error" | "error" | Successful authentication. All calls to Data API will fail with provider_error. |
"error.user_input_required" | "error" | Successful authentication. All calls to Data API will fail with user_input_required. |
"error.wrong_credentials" | "error" | Successful authentication. All calls to Data API will fail with wrong_credentials. |
Updated about 1 year ago