taler-docs

commit 232ca2b475de66e42a6112c9dbf106e48f734d2b
parent a8dcf19e1adb43b2bae42f32e667c19bc4ba866a
Author: Christian Blättler <blatc2@bfh.ch>
Date:   Mon,  3 Jun 2024 20:46:10 +0200

work on create orders api

Diffstat:
M
core/api-merchant.rst
 | 
19
+++++++++++--------

1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -2400,8 +2400,10 @@ Creating orders
 
     interface Order {
       // If this field is omitted, version 0 is assumed.
-      // Version 1 orders support the ``choices`` array.
-      version?: "1" | "0";
+      // Version 1 supports the ``choices`` array, see
+      // https://docs.taler.net/design-documents/046-mumimo-contracts.html
+      // @since protocol **vSUBSCRIBE**
+      version?: 0 | 1;
 
       // Only available in v0 orders.
       // Total price for the transaction. The exchange will subtract deposit
@@ -2542,11 +2544,6 @@ protocol **vSUBSCRIBE**.
       // across all configured tokens of a merchant.
       token_family_slug: string;
 
-      // Start of the validity period of the token. Based on this, the merchant
-      // will select the relevant signing key. This value is rounded down
-      // according to the configured rounding duration in the token family.
-      valid_after: Timestamp;
-
       // How many units of the input are required.
       // Defaults to 1 if not specified. Output with count == 0 are ignored by
       // the merchant backend.
@@ -2572,7 +2569,8 @@ protocol **vSUBSCRIBE**.
       // Start of the validity period of the token. Based on this, the merchant
       // will select the relevant signing key. This value is rounded down
       // according to the configured rounding duration in the token family.
-      valid_after: Timestamp;
+      // If not specified, the current time is used.
+      valid_after?: Timestamp;
 
       // How many units of the output are issued by the merchant.
       // Defaults to 1 if not specified. Output with count == 0 are ignored by
@@ -4215,6 +4213,11 @@ The contract terms must have the following structure:
 .. ts:def:: ContractTerms
 
   interface ContractTerms {
+    // If this field is omitted, version 0 is assumed.
+    // Version 1 supports the ``choices`` array, see
+    // https://docs.taler.net/design-documents/046-mumimo-contracts.html
+    version?: 0 | 1;
+
     // Human-readable description of the whole purchase.
     summary: string;