|
|
The attached screenshot shows what happens otherwise: here we need the user to fill in the "Form" (bank account), but we show rules that would only apply to wallets, possibly causing the user to try to satisfy the wrong requirement! bad-rules.png (49,921 bytes) |
|
|
taler-docs.git::bb475832..352c11eb adds an "is_wallet" to the AML /decisions response, so that the AML-SPA can tell which rules should be given as choices. |
|
|
exchange.git :: c64322d5f..a1e12a191 implements the 'is_wallet' extension of /decisions. Still does NOT actually filter is own rules (TBD!). |
|
|
3665a932b..19173147e completes the implementation in the exchange backend. SPA update (& QC) missing on this. |
|
|
commit a458ec3b5558908d3176cce4178b6c6bf7926938 (HEAD -> master, origin/master, origin/HEAD) Author: Sebastian <sebasjm@gmail.com> Date: Tue Apr 22 16:59:06 2025 -0300 add warning based on account type, also hide buttons if not needed and hint in the title the type of account |
|
|
i think that aml spa was the missing piece |
- Anonymous
