diff options
Diffstat (limited to 'design-documents/028-deposit-policies.rst')
-rw-r--r-- | design-documents/028-deposit-policies.rst | 27 |
1 files changed, 23 insertions, 4 deletions
diff --git a/design-documents/028-deposit-policies.rst b/design-documents/028-deposit-policies.rst index d0a1b107..1bdf4801 100644 --- a/design-documents/028-deposit-policies.rst +++ b/design-documents/028-deposit-policies.rst @@ -1,5 +1,5 @@ -DD28: Deposit Policy Extensions -############################### +DD 28: Deposit Policy Extensions +################################ .. note:: @@ -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 =============== |