commit 73f61323554df47079e19cd4236d148e2c17a1b3 parent e8c9ce8cb78b3594a1f4e6fe03c42eda5a08fb7e Author: Christian Grothoff <christian@grothoff.org> Date: Wed, 12 Aug 2020 12:04:11 +0200 need more ECs Diffstat:
| M | gnu-taler-error-codes/registry.rec | | | 9 | +++++++-- |
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec @@ -618,10 +618,15 @@ Description: The exchange knows literally nothing about the coin we were asked t HttpStatus: 404 Value: 1501 -Name: REFUND_CONFLICT -Description: We could not process the refund request as the coin's transaction history does not permit the requested refund at this time. The "history" in the response proves this. +Name: REFUND_CONFLICT_DEPOSIT_INSUFFICIENT +Description: We could not process the refund request as the coin's transaction history does not permit the requested refund because then refunds would exceed the deposit amount. The "history" in the response proves this. HttpStatus: 409 +Value: 1502 +Name: REFUND_INCONSITENT_AMOUNT +Description: We could not process the refund request as the same refund transaction ID was already used with a different amount. Retrying with a different refund transaction ID may work. The "history" in the response proves this by providing the conflicting entry. +HttpStatus: 412 + Value: 1503 Name: REFUND_DEPOSIT_NOT_FOUND Description: The exchange knows about the coin we were asked to refund, but not about the specific /deposit operation. Hence, we cannot issue a refund (as we do not know if this merchant public key is authorized to do a refund).