View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011798 | Taler | wallet-core | public | 2026-09-16 13:15 | 2026-09-24 12:28 |
| Reporter | MarcS | Assigned To | Florian Dold | ||
| Priority | normal | Severity | tweak | Reproducibility | have not tried |
| Status | confirmed | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | 1.7 | ||||
| Summary | 0011798: checkPayForTemplate should return amountAvailable | ||||
| Description | When the user scans a pay-template talerURI, the amount can be nil, which means that the user can type in the amount to pay. For this, we should show the user how much money they have available. Instead of creating a new call (like getMaxPeerPushDebitAmount), wallet-core should always (mandatory) return "amountAvailable" (or "maxAmountAvailable") directly from checkPayForTemplate - not only if the requested amount is nil. If a fixed amount is set, wallets can immediately compare it with amountAvailable and show whether the payment is possible or not. If the user can type in an amount, wallets can limit it to amountAvailable. Future: merchants can return multiple accepted currencies (array). The user first needs to choose an exchange, then type in the amount. Thus amountAvailable also should become an array. Consider using scopeIdx (0011651) | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-16 13:15 | MarcS | New Issue | |
| 2026-09-16 13:16 | MarcS | Relationship added | related to 0011651 |
| 2026-09-24 12:28 | Christian Grothoff | Assigned To | => Florian Dold |
| 2026-09-24 12:28 | Christian Grothoff | Severity | minor => tweak |
| 2026-09-24 12:28 | Christian Grothoff | Status | new => confirmed |
| 2026-09-24 12:28 | Christian Grothoff | Product Version | 1.7 => git (master) |
| 2026-09-24 12:28 | Christian Grothoff | Target Version | => 1.7 |
