taler-docs

commit b3df4cf18decb81ed16dac1f46c861dd29d689fe
parent fef6a3eb8b34c88ba7a9a274844969baee899f15
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Fri, 26 Mar 2021 14:12:07 -0400

update timestamp values in example to use ‘{ "t_ms": NUMBER }’ format; add note

Diffstat:
M
taler-mcig.rst
 | 
10
++++++----

1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/taler-mcig.rst b/taler-mcig.rst
@@ -461,10 +461,10 @@ The backend returns ``200 OK`` with body:
          "description": "Beethoven Sonatas"
        }
      ],
-     "timestamp": "2021/03/23 22:14:25",
-     "refund_deadline": "2021/03/23 22:14:25",
-     "pay_deadline": "2021/03/23 22:15:25",
-     "wire_transfer_deadline": "2021/03/23 22:16:25",
+     "timestamp": { "t_ms": 1616537665000 },
+     "refund_deadline": { "t_ms": 1616537665000 },
+     "pay_deadline": { "t_ms": 1616537725000 },
+     "wire_transfer_deadline": { "t_ms": 1616537785000 },
      "merchant_pub": FIXME,
      "merchant_base_url": "https://example.com/",
      "merchant":
@@ -484,6 +484,8 @@ The backend returns ``200 OK`` with body:
 
 Notes:
 - The ``order_id`` value is the one given in the ``PostOrderResponse``.
+- The ``timestamp`` value represents 2021-03-23 22:14:25 UTC
+  in milliseconds after the epoch.
 - The ``refund_deadline`` value is the same as the ``timestamp`` value
   (no refunds possible).
 - The ``pay_deadline`` value is one minute after the ``timestamp`` value.