taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 27899628e73e315685a9c34fea0e223144f84d3d
parent f357f261c5369586ad67f8efa580fe737d6e2619
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Wed, 11 Aug 2021 05:33:13 -0400

simplify; swap out old FIXME for new FIXME

Diffstat:
Mtaler-merchant-manual.rst | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst @@ -197,9 +197,9 @@ to the wallet as part of the order URI. Additionally, when stocks are limited, you can configure Taler to set a *product lock* on items (say, while composing the shopping cart). These locks, as well as the *order lock* (when the order is complete), -can be configured to auto-unlock at a certain time or triggering event. +can be configured to auto-unlock at certain times. -.. FIXME: Is the "or event" correct? If so, what events are triggers? +.. FIXME: Is "can be configured" correct? (Are there controls surfaced?) A wallet may *pay* for a claimed order, at which point the order turns into a (paid) contract. Orders have an expiration date after which the commercial