commit 3f18953a21019015c4ea748c0f9e3cdd00abb93e
parent 47aab2b85b89d265b0cf1705e5532edd59062a49
Author: Jeff Burdges <burdges@gnunet.org>
Date: Tue, 10 Nov 2015 16:45:43 +0100
Fix another JSON signature object
Diffstat:
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/api-mint.rst b/api-mint.rst
@@ -235,7 +235,10 @@ When transfering money to the mint such as via SEPA transfers, the mint creates
:>jsonarr string type: either the string "WITHDRAW" or the string "DEPOSIT"
:>jsonarr object amount: the amount_ that was withdrawn or deposited
:>jsonarr object wire: a JSON object with the wiring details needed by the banking system in use, present in case the `type` was "DEPOSIT"
- :>jsonarr object signature: signature_ (full object with all details) made with purpose `TALER_SIGNATURE_WALLET_RESERVE_WITHDRAW` made with the reserve's public key over the original "WITHDRAW" request, present if the `type` was "WITHDRAW"
+ :>jsonarr string details: base32_ binary encoding of the transaction data as a `TALER_WithdrawRequestPS` struct described in :ref:`Signatures`, only present if the `type` was "WITHDRAW". Its `purpose` should match our `type`, `amount_with_fee`, should match our `amount`, and its `size` should be consistent.
+ :>jsonarr object signature: the EdDSA signature_ (binary-only) made with purpose `TALER_SIGNATURE_WALLET_COIN_DEPOSIT` or `TALER_SIGNATURE_WALLET_COIN_MELT` over the transaction's details, again only present if the `type` was "WITHDRAW".
+
+
**Error Response: Unknown reserve**