View Issue Details

IDProjectCategoryView StatusLast Update
0011385Talerotherpublic2026-05-08 23:54
ReporterChristian Grothoff Assigned Tosebasjm  
PrioritynormalSeveritytweakReproducibilityN/A
Status assignedResolutionopen 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version1.6 
Summary0011385: expose amount & summary in paivana checkout page
DescriptionGet from template, bad to ask to be paid without showing how much ;-)
TagsNo tags attached.

Activities

Christian Grothoff

2026-05-08 23:54

manager   ~0028585

As per 93b1953..d822f2c we now pass the "summary" and the "choices" (see
https://docs.taler.net/design-documents/073-extended-merchant-template.html#tsref-type-TemplateAddDetails )
to the MUST logic that instantiates the template.

contrib/paywall.en.must should be updated to show the summary and the choices. It should be noted that in the
Paivana context there are some limitations:
- We don't know the meaning of the token families, or which token families are available at the wallet
- Tip probably should never be given, and it's OK to not show it
- The main common possibility is that there are multiple choices for multiple currencies

We should probably also already support subscriptions and discount tokens, but for those
it probably is OK to *only* show the description (possibly with i18n applied) of the choice,
without going into details about inputs and outputs; furthermore, because we do not know
if a choice that requires any input token is actually available at the user's wallet, I suggest
we do NOT show such choices by default (KISS!) and only show them after the user clicks
on some "more payment options" button. Just to avoid bloating the screen with tons of choices,
especially given that the wallet will *again* show / auto-apply these choices after scanning
the QR code anyway.

So my suggestion: first iteration, ONLY show summary (if present) and by default ONLY the
choices without input tokens with price and description. If there are more choices, have
"more payment options" button to expand list to also show payment options involving inputs.

To proceed, I think Sebastian should do a first set of modifications to the paywall.en.must, and
then we can ask Vlada to do an iteration on the design for a v2.

Issue History

Date Modified Username Field Change
2026-05-07 12:59 Christian Grothoff New Issue
2026-05-07 12:59 Christian Grothoff Status new => assigned
2026-05-07 12:59 Christian Grothoff Assigned To => Christian Grothoff
2026-05-08 23:54 Christian Grothoff Note Added: 0028585
2026-05-08 23:54 Christian Grothoff Assigned To Christian Grothoff => sebasjm
2026-05-08 23:54 Christian Grothoff Target Version => 1.6