exchange

Base system with REST service to issue digital coins, run by the payment service provider
Log | Files | Refs | Submodules | README | LICENSE

commit 129223e1d0d4ff54ceff44485afcc4abeaa0ee83
parent 3c484c71a2924cb20e7468a325ca7e230068febb
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed, 17 Jan 2024 21:11:23 +0100

-fix doc

Diffstat:
Msrc/include/taler_exchange_service.h | 4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/include/taler_exchange_service.h b/src/include/taler_exchange_service.h @@ -2690,9 +2690,9 @@ struct TALER_EXCHANGE_Withdraw2Handle; * Withdraw a coin from the exchange using a /reserves/$RESERVE_PUB/withdraw * request. This API is typically used by a merchant to withdraw a tip * where the blinding factor is unknown to the merchant. Note that unlike - * the #TALER_EXCHANGE_withdraw() API, this API neither unblinds the signatures + * the #TALER_EXCHANGE_batch_withdraw() API, this API neither unblinds the signatures * nor can it verify that the exchange signatures are valid, so these tasks - * are left to the caller. Wallets probably should use #TALER_EXCHANGE_withdraw() + * are left to the caller. Wallets probably should use #TALER_EXCHANGE_batch_withdraw() * which integrates these steps. * * Note that to ensure that no money is lost in case of hardware