| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011072 | Taler | merchant portal webui | public | 2026-02-14 14:52 | 2026-04-01 14:10 |
| Reporter | how | Assigned To | vlada.svirsh | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | won't fix | ||
| Product Version | git (master) | ||||
| Target Version | 1.6 | Fixed in Version | 1.6 | ||
| Summary | 0011072: Issues with Merchant back office onboarding process | ||||
| Description | There are several issues with the backend form. Here is my feedforth using https://stage.my.taler-ops.ch/ 1. Firefox fails to recognize the username for saving the password. Instead of capturing the username it captures the business name. This is because of how Firefox tries to catch the username. It first looks for 'login', 'username' or 'email' field above the password field. If those do not exist, it goes for the text field immediately above the password field. Therefore the username field should be called username and not id. 2. But point 1 is not the only issue. UX would be much better with the following process: a three-step wizard with simpler forms. (see attached screenshots) Step 1: Ask for a phone or email contact (to send a verification token to) and a business name (for public facing UI and for username generation), plus the acceptance of terms. Step 2: Provide a unique username based on the business name (ASCII-based hyphen-separated version of the given business name -- which should therefore be limited for URL compliance, i.e., in length) + a field for the token sent by phone, or the one sent by email (which would actually be an URL that brings you straight to that wizard step so you only have the password to enter). This allows the user to spend the time waiting for the confirmation token actively entering a password. Step 3: Confirmation, celebration! | ||||
| Steps To Reproduce | To reproduce the Firefox password saving issue, go to the merchant onboarding page and enter a business name that is different from the username, then click 'create': if autosave passwords is active in Firefox (which is the default), you should see a popup with the Business name as the username. | ||||
| Additional Information | The screenshots show what could a three-step process look like. Note that the second step is doubled, depending on whether the first input was a phone or an email. Extra fields (an email if a phone was entered, or vice-versa) should belong to the onboarding notifications once the account was created. See for example how Infomaniak keeps notifying the user to ask for more details -- which also teaches about notifications. | ||||
| Tags | design-required, ux | ||||
- Anonymous