gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [taler-api] 01/02: fix spec to match actual implementation


From: gnunet
Subject: [GNUnet-SVN] [taler-api] 01/02: fix spec to match actual implementation
Date: Thu, 04 Jan 2018 12:06:49 +0100

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository api.

commit ecd05947b2e0e0a89a3a120208f63b7756c27a4c
Author: Christian Grothoff <address@hidden>
AuthorDate: Mon Jan 1 22:32:25 2018 +0100

    fix spec to match actual implementation
---
 api-merchant.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/api-merchant.rst b/api-merchant.rst
index 2a1fafc..7c70fd4 100644
--- a/api-merchant.rst
+++ b/api-merchant.rst
@@ -220,6 +220,8 @@ The following API are made available by the merchant's 
`backend` to the merchant
   :status 412 Precondition Failed:
     The given exchange is not acceptable for this merchant, as it is not in the
     list of accepted exchanges and not audited by an approved auditor.
+  :status 401 Unauthorized:
+    One of the coin signatures was not valid.
   :status 403 Forbidden:
     The exchange rejected the payment because a coin was already spent before.
     The response will include the `coin_pub` for which the payment failed,
@@ -267,7 +269,7 @@ The following API are made available by the merchant's 
`backend` to the merchant
     interface RefundDetail {
       // Merchant signature over the hashed order id.
       // The purpose is `TALER_SIGNATURE_MERCHANT_REFUND_OK`.
-      sig: EddsaSignature;
+      merchant_sig: EddsaSignature;
 
       // refund transaction ID chosen by the merchant.
       rtransaction_id: uint64_t;

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]