merchant

Merchant backend to process payments, run by merchants
Log | Files | Refs | Submodules | README | LICENSE

commit 44d207002cddd288355380657f84d8576d5be053
parent f0ddb591ca1744318d07b45acdeb73caec3b02dd
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat, 17 Nov 2018 12:07:53 +0100

adjust callback to match revised libtalerexchange API for /deposit

Diffstat:
Msrc/backend/taler-merchant-httpd_pay.c | 4+++-
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/backend/taler-merchant-httpd_pay.c b/src/backend/taler-merchant-httpd_pay.c @@ -898,6 +898,7 @@ begin_transaction (struct PayContext *pc); * (200) for successful deposit; 0 if the exchange's reply is bogus (fails * to follow the protocol) * @param ec taler-specific error code, #TALER_EC_NONE on success + * @param exchange_sig signature from the exchange over the deposit confirmation * @param sign_key which key did the exchange use to sign the @a proof * @param proof the received JSON reply, * should be kept as proof (and, in case of errors, be forwarded to @@ -907,7 +908,8 @@ static void deposit_cb (void *cls, unsigned int http_status, enum TALER_ErrorCode ec, - const struct TALER_ExchangePublicKeyP *sign_key, + const struct TALER_ExchangeSignatureP *exchange_sig, + const struct TALER_ExchangePublicKeyP *sign_key, const json_t *proof) { struct DepositConfirmation *dc = cls;