taler-docs

commit a6a507a2c16a22f12d61c88b0b84fb81dcd9afcf
parent 0a7e53613091f68af6102dd9dc562bb88e83a943
Author: Özgür Kesim <oec-taler@kesim.org>
Date:   Wed, 19 Mar 2025 22:04:06 +0100

[exchange] added withdraw_commitment_hash to /recoup

With the new /withdraw endpoint and related database schema,
in order to find the reserve related to a coin for recoup,
we need the hash of the commitment to the original withdraw
request.

Diffstat:
M
core/api-exchange.rst
 | 
10
+++++++---

1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
@@ -3924,8 +3924,8 @@ in using this API.
     The coin's signature is invalid.
     This response comes with a standard `ErrorDetail` response.
   :http:statuscode:`404 Not found`:
-    The denomination key is unknown, or the blinded
-    coin is not known to have been withdrawn.
+    The denomination key is unknown, the withdraw commitment is unknown
+    or the blinded coin is not known to have been withdrawn.
     If the denomination key is unknown, the response will be
     a `DenominationUnknownMessage`.
   :http:statuscode:`409 Conflict`:
@@ -3954,8 +3954,12 @@ in using this API.
       // Signature over the `coin public key <eddsa-coin-pub>` by the denomination.
       denom_sig: DenominationSignature;
 
+      // The hash of the original withdraw commitment (TALER_WithdrawCommitmentHashP)
+      // that this coin was part of.
+      h_commitment: HashCode;
+
       // Exchange-contributed values during the refresh
-      // operation (see /csr-withdraw).
+      // operation (see /blinding-prepare).
       ewv: ExchangeWithdrawValue;
 
       // Signature of `TALER_RecoupRequestPS` created with