commit 95490a3234556594957a270ff0d051961b4b0ebc
parent e06eebdae47e9443fb7e9db6e5ce3de03a6bc10e
Author: Özgür Kesim <oec-taler@kesim.org>
Date: Thu, 7 Dec 2023 20:41:58 +0100
[dd 28] added motivation
Diffstat:
1 file changed, 21 insertions(+), 2 deletions(-)
diff --git a/design-documents/028-deposit-policies.rst b/design-documents/028-deposit-policies.rst
@@ -41,7 +41,19 @@ The policies shall be implemented as *extensions* to the exchange (see
Motivation
**********
-TODO
+GNU Taler's initial set of API's (withdraw, deposit, refresh) support most
+payment situations in which customers pay for goods and services within an
+otherwise unconditioned transaction. (A notable exception from this the
+ability to provide refunds, which will be re-factored into a policy extension).
+
+However, in many payments depend on additional conditions to be met. GNU Taler
+already supports payments with age restriction applied, but there are other
+scenarious that we want to support.
+
+Our aim is to provide an API for extensions of GNU Taler that implement
+particular policies and policy-handling for payments (also called *conditioned
+payments*).
+
Background and Requirements
***************************
@@ -56,9 +68,16 @@ TODO, explain:
- C-structs for policy extensions (esp. the handlers)
- Naming conventions for policy extensions
- Deadlines and -handling
-- API-endpoints (``/extensions/policy_...``)
- Typical choreography of a deposit with policy and its fulfillment
+
+API-Endpoints of the Exchange
+=============================
+
+TODO
+
+
+
Database-schema
===============
