marketing

Marketing materials (presentations, posters, flyers)
Log | Files | Refs

commit 684af09b0508a4005fffaf4eaf49cf8ff4d9fee0
parent 852ce5146ac3f1f1fc266a3504467fdf2b44f692
Author: Sebastian <sebasjm@gmail.com>
Date:   Sat, 12 Nov 2022 20:38:20 -0300

refund SHOULD be consulted

Diffstat:
Mstandards/draft-grothoff-taler.xml | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/standards/draft-grothoff-taler.xml b/standards/draft-grothoff-taler.xml @@ -281,7 +281,7 @@ also <xref target="taler-registry" />). <section anchor="registry-entry-refund" title="Action: refund"> <t> A "refund" action instructs the wallet to download information about - an available refund, possibly consult the user about the refund, and + an available refund. Wallet SHOULD consult the user about the refund and then obtain the refund for an already paid order. </t> <t> @@ -387,7 +387,7 @@ also <xref target="taler-registry" />). are not specified in the argument list must not be submitted. </t> <t> - Wallets do not have to support users entering all possible fields + Wallets MAY to support users entering all possible fields of a contract. Keys that MUST be supported at this time are the "amount" and the "summary" fields. The wallet MUST validate that the amount entered by the user is well-formed. For the amount,