View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010525 | Taler | merchant backoffice SPA | public | 2025-10-23 10:00 | 2025-10-23 10:00 |
| Reporter | Christian Grothoff | Assigned To | sebasjm | ||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.2 | ||||
| Summary | 0010525: merchant backend SPA should implement payment target restrictions | ||||
| Description | With protocol v22, we introduced the ability to restrict account types. See /config: // Space-separated list of enabled payment target types. // Useful if the SPA should not show allow adding other // types of bank accounts. "*" is used to represent no // restriction. // Since protocol **v22** payment_target_types: string; // Regular expression representing further restrictions // on allowed payment targets. Any "payto://"-URI supplied // for a bank account must match the given regular expression. // For example, "payto://iban/CH.*" would restrict the system // to only Swiss bank accounts. // Optional, no restrictions are imposed if the field is // absent. // Since protocol **v22** payment_target_regex? string; The SPA should enforce these. (The backend _also_ does, but never good to get a 400 Bad request :-)). | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-10-23 10:00 | Christian Grothoff | New Issue | |
| 2025-10-23 10:00 | Christian Grothoff | Status | new => assigned |
| 2025-10-23 10:00 | Christian Grothoff | Assigned To | => sebasjm |
