gana

registry.rec (147683B)

---

 # -*- mode: rec -*-
 #
 # Registry for HTTP status codes
 #
 %rec: TalerErrorCode
 %key: Value
 %singular: Value
 %typedef: ValueRange_t range 0 9999
 %typedef: ValueRange_t regexp /^[0123456789]?[0123456789]?[0123456789]?[0123456789]?$/
 %constraint: ( Value < 100 ) || ( Value > 999 )
 %type: Value ValueRange_t
 %mandatory: Value
 %typedef: Description_t regexp |^[abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_-][abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_\(\)\.,;!"':#`\/ -]*$|
 %type: Description Description_t
 %mandatory: Description
 %typedef: Name_t regexp /^[ABCDEFGHIJKLMNOPQRSTUVWXYZ_][ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789]*$/
 %type: Name Name_t
 %unique: Name
 %mandatory: Name
 %singular: Name
 # A status of 0 means not an HTTP status (i.e. created client-side)
 %type: HttpStatus rec HttpStatusCode
 %mandatory: HttpStatus
 %sort: Value
 
 # 0 - 99: Reserved for GENERIC error codes
 
 Value: 0
 Name: NONE
 Description: Special code to indicate success (no error).
 HttpStatus: 0
 
 # We could not get the error code.
 Value: 1
 Name: INVALID
 Description: An error response did not include an error code in the format expected by the client. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
 HttpStatus: 0
 
 Value: 2
 Name: GENERIC_CLIENT_INTERNAL_ERROR
 Description: An internal failure occurred on the client side. Details should be in the local logs. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 0
 
 Value: 3
 Name: GENERIC_CLIENT_UNSUPPORTED_PROTOCOL_VERSION
 Description: The client does not support the protocol version advertised by the server.
 HttpStatus: 0
 
 # Fundamental problems detected client-side (10-19)
 
 Value: 10
 Name: GENERIC_INVALID_RESPONSE
 Description: The response received from the server was not in the expected format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and the network connection to the server.
 HttpStatus: 0
 
 Value: 11
 Name: GENERIC_TIMEOUT
 Description: The operation timed out. Trying again might help. Check the network connection.
 HttpStatus: 0
 
 Value: 12
 Name: GENERIC_VERSION_MALFORMED
 Description: The protocol version given by the server does not follow the required format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
 HttpStatus: 0
 
 Value: 13
 Name: GENERIC_REPLY_MALFORMED
 Description: The service returned a response in the correct data format, but its content did not satisfy the protocol. File a bug report.
 HttpStatus: 0
 
 Value: 14
 Name: GENERIC_CONFIGURATION_INVALID
 Description: There is an error in the client-side configuration, for example an option is set to an invalid value. Check the logs and fix the local configuration.
 HttpStatus: 0
 
 Value: 15
 Name: GENERIC_UNEXPECTED_REQUEST_ERROR
 Description: The client made a request to a service, but received an error response it does not know how to handle. Please file a bug report.
 HttpStatus: 0
 
 Value: 16
 Name: GENERIC_TOKEN_PERMISSION_INSUFFICIENT
 Description: The token used by the client to authorize the request does not grant the required permissions for the request. Check the requirements and obtain a suitable authorization token to proceed.
 HttpStatus: 403
 
 # Fundamental client-side protocol problems (20-29)
 # (fundamental: cannot be helped, client is very broken)
 
 Value: 20
 Name: GENERIC_METHOD_INVALID
 Description: The HTTP method used is invalid for this endpoint. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 405
 
 Value: 21
 Name: GENERIC_ENDPOINT_UNKNOWN
 Description: There is no endpoint defined for the URL provided by the client. Check whether the URL is correct or file a report with the client software developers.
 HttpStatus: 404
 
 Value: 22
 Name: GENERIC_JSON_INVALID
 Description: The JSON in the client's request was malformed. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 400
 
 Value: 23
 Name: GENERIC_HTTP_HEADERS_MALFORMED
 Description: Some of the HTTP headers provided by the client were malformed, so the server could not handle the request. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 400
 
 Value: 24
 Name: GENERIC_PAYTO_URI_MALFORMED
 Description: The `payto://` URI provided by the client is malformed. Check that it uses the syntax specified by RFC 8905 and that the bank account number is correct.
 HttpStatus: 400
 
 Value: 25
 Name: GENERIC_PARAMETER_MISSING
 Description: A required parameter in the request was missing. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 400
 
 Value: 26
 Name: GENERIC_PARAMETER_MALFORMED
 Description: A parameter in the request was malformed. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 400
 
 Value: 27
 Name: GENERIC_RESERVE_PUB_MALFORMED
 Description: The reserve public key was malformed.
 HttpStatus: 400
 FIXME: Fold with 26?
 
 Value: 28
 Name: GENERIC_COMPRESSION_INVALID
 Description: The body in the request could not be decompressed by the server. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 400
 
 Value: 29
 Name: GENERIC_PATH_SEGMENT_MALFORMED
 Description: A segment in the path of the URL provided by the client is malformed. Check that the URL uses the correct encoding.
 HttpStatus: 400
 
 # Circumstantial client-side protocol problems (30-39)
 # (Circumstantial == may work with another server, but not this one)
 
 Value: 30
 Name: GENERIC_CURRENCY_MISMATCH
 Description: The currency involved in the operation is not acceptable for this server. Check the configuration and ensure that the currency specified for the service provider is supported by that provider.
 HttpStatus: 400
 
 Value: 31
 Name: GENERIC_URI_TOO_LONG
 Description: The URI is longer than the longest URI the HTTP server is willing to parse. If this was a legitimate request, the server administrator or software developers may need to increase the limit.
 HttpStatus: 414
 
 Value: 32
 Name: GENERIC_UPLOAD_EXCEEDS_LIMIT
 Description: The body is too large for the endpoint. If this was a legitimate request, the server administrator or software developers may need to increase the limit.
 HttpStatus: 413
 
 Value: 33
 Name: GENERIC_PARAMETER_EXTRA
 Description: A parameter that must not be present was included in the request. This is likely a bug in the client implementation. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 400
 
 # 40-49: access control issues
 Value: 40
 Name: GENERIC_UNAUTHORIZED
 Description: The service refused the request due to lack of proper authorization. Accessing this endpoint requires an access token from the account owner.
 HttpStatus: 401
 
 Value: 41
 Name: GENERIC_TOKEN_UNKNOWN
 Description: The service refused the request because the given authorization token is unknown. The client should request a valid access token from the account owner.
 HttpStatus: 401
 
 Value: 42
 Name: GENERIC_TOKEN_EXPIRED
 Description: The service refused the request because the given authorization token expired. The client should request a fresh authorization token from the account owner.
 HttpStatus: 401
 
 Value: 43
 Name: GENERIC_TOKEN_MALFORMED
 Description: The service refused the request because the given authorization token is invalid or malformed. The client should check that it has the correct credentials.
 HttpStatus: 401
 
 Value: 44
 Name: GENERIC_FORBIDDEN
 Description: The service refused the request because the client lacks the required rights on the resource. The client may need different credentials to perform this operation.
 HttpStatus: 403
 
 # Server-side database problems (50-59)
 
 Value: 50
 Name: GENERIC_DB_SETUP_FAILED
 Description: The service failed to initialize its connection to the database. The system administrator should check that the service has permission to access the database and that the database is running.
 HttpStatus: 500
 
 Value: 51
 Name: GENERIC_DB_START_FAILED
 Description: The service encountered an error while starting the database transaction. The system administrator should check that the database is running.
 HttpStatus: 500
 
 Value: 52
 Name: GENERIC_DB_STORE_FAILED
 Description: The service failed to store information in its database. The system administrator should check that the database is running and review the service logs.
 HttpStatus: 500
 
 Value: 53
 Name: GENERIC_DB_FETCH_FAILED
 Description: The service failed to fetch information from its database. The system administrator should check that the database is running and review the service logs.
 HttpStatus: 500
 
 Value: 54
 Name: GENERIC_DB_COMMIT_FAILED
 Description: The service encountered an unrecoverable error trying to commit a transaction to the database. The system administrator should check that the database is running and review the service logs.
 HttpStatus: 500
 
 Value: 55
 Name: GENERIC_DB_SOFT_FAILURE
 Description: The service encountered an error while committing the database transaction; despite repeated retries, a conflicting transaction persisted. This indicates a serialization error. It may be caused by conflicting concurrent transactions or a missing index. Check that the latest available version is being used and file a report with the developers if the problem persists.
 HttpStatus: 500
 
 Value: 56
 Name: GENERIC_DB_INVARIANT_FAILURE
 Description: The service's database is inconsistent and violates service-internal invariants. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 500
 
 
 # Server-side computational problems (60-69)
 
 Value: 60
 Name: GENERIC_INTERNAL_INVARIANT_FAILURE
 Description: The HTTP server experienced an internal invariant failure (bug). Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 500
 
 Value: 61
 Name: GENERIC_FAILED_COMPUTE_JSON_HASH
 Description: The service could not compute a cryptographic hash over a JSON value. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 500
 
 Value: 62
 Name: GENERIC_FAILED_COMPUTE_AMOUNT
 Description: The service could not compute an amount. Check whether the latest available version is in use or file a report with the developers.
 HttpStatus: 500
 
 
 # Server-side resource problems (70-79)
 
 Value: 70
 Name: GENERIC_PARSER_OUT_OF_MEMORY
 Description: The HTTP server had insufficient memory to parse the request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
 HttpStatus: 500
 
 Value: 71
 Name: GENERIC_ALLOCATION_FAILURE
 Description: The HTTP server failed to allocate memory. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
 HttpStatus: 500
 
 Value: 72
 Name: GENERIC_JSON_ALLOCATION_FAILURE
 Description: The HTTP server failed to allocate memory for building a JSON response. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Ask the system administrator to investigate.
 HttpStatus: 500
 
 Value: 73
 Name: GENERIC_CURL_ALLOCATION_FAILURE
 Description: The HTTP server failed to allocate memory for making a CURL request. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
 HttpStatus: 500
 
 Value: 74
 Name: GENERIC_FAILED_TO_LOAD_TEMPLATE
 Description: The backend could not locate a required template to generate an HTML response. The system administrator should check whether the resource files are installed in the correct location and readable by the service.
 HttpStatus: 406
 
 Value: 75
 Name: GENERIC_FAILED_TO_EXPAND_TEMPLATE
 Description: The backend could not expand the template to generate an HTML response. The system administrator should investigate the logs and check whether the templates are well-formed.
 HttpStatus: 500
 
 Value: 76
 Name: GENERIC_FEATURE_NOT_IMPLEMENTED
 Description: The requested feature is not implemented by the server. The system administrator of the server may try to update the software or build it with other options to enable the feature.
 HttpStatus: 501
 
 Value: 77
 Name: GENERIC_OS_RESOURCE_ALLOCATION_FAILURE
 Description: The operating system failed to allocate required resources. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
 HttpStatus: 500
 
 Value: 78
 Name: GENERIC_REQUESTED_FORMAT_UNSUPPORTED
 Description: The requested content type is not supported by the server. The client should try requesting a different format.
 HttpStatus: 406
 
 # 80-99: available for future use
 
 
 
 # 100 - 999: VERBOTEN due to confusion with HTTP status codes (at least 100-599).
 
 # 1000 - 1999: Reserved for exchange
 # 1000 - 1099: Reserved for EXCHANGE_GENERIC
 
 Value: 1000
 Name: EXCHANGE_GENERIC_BAD_CONFIGURATION
 Description: Exchange is badly configured and thus cannot operate.
 HttpStatus: 500
 
 Value: 1001
 Name: EXCHANGE_GENERIC_OPERATION_UNKNOWN
 Description: The specified operation is unknown for this endpoint.
 HttpStatus: 404
 
 Value: 1002
 Name: EXCHANGE_GENERIC_WRONG_NUMBER_OF_SEGMENTS
 Description: The number of segments included in the URI does not match the number of segments expected by the endpoint.
 HttpStatus: 404
 
 Value: 1003
 Name: EXCHANGE_GENERIC_COIN_CONFLICTING_DENOMINATION_KEY
 Description: The same coin was already used with a different denomination previously.
 HttpStatus: 409
 
 Value: 1004
 Name: EXCHANGE_GENERIC_COINS_INVALID_COIN_PUB
 Description: The public key given to the `/coins/` endpoint of the exchange was malformed.
 HttpStatus: 400
 
 Value: 1005
 Name: EXCHANGE_GENERIC_DENOMINATION_KEY_UNKNOWN
 Description: The exchange is not aware of the denomination key the wallet requested for the operation.
 HttpStatus: 404
 
 Value: 1006
 Name: EXCHANGE_DENOMINATION_SIGNATURE_INVALID
 Description: The signature of the denomination key over the coin is not valid.
 HttpStatus: 403
 
 Value: 1007
 Name: EXCHANGE_GENERIC_KEYS_MISSING
 Description: The exchange failed to perform the operation as it could not find the private keys. This is a problem with the exchange setup, not with the client's request.
 HttpStatus: 503
 
 Value: 1008
 Name: EXCHANGE_GENERIC_DENOMINATION_VALIDITY_IN_FUTURE
 Description: Validity period of the denomination lies in the future.
 HttpStatus: 412
 
 Value: 1009
 Name: EXCHANGE_GENERIC_DENOMINATION_EXPIRED
 Description: The denomination key of the coin has passed its expiration time for the requested operation.
 HttpStatus: 410
 
 Value: 1010
 Name: EXCHANGE_GENERIC_DENOMINATION_REVOKED
 Description: Denomination key of the coin has been revoked.
 HttpStatus: 410
 
 Value: 1011
 Name: EXCHANGE_GENERIC_SECMOD_TIMEOUT
 Description: An operation where the exchange interacted with a security module timed out.
 HttpStatus: 500
 
 Value: 1012
 Name: EXCHANGE_GENERIC_INSUFFICIENT_FUNDS
 Description: The coin did not have sufficient residual value for the operation. The `history` in this response provides the coin's `residual_value`, which may be less than its `original_value`.
 HttpStatus: 409
 
 Value: 1013
 Name: EXCHANGE_GENERIC_COIN_HISTORY_COMPUTATION_FAILED
 Description: The exchange had an internal error reconstructing the transaction history of the coin that was being processed.
 HttpStatus: 500
 
 Value: 1014
 Name: EXCHANGE_GENERIC_HISTORY_DB_ERROR_INSUFFICIENT_FUNDS
 Description: The exchange failed to obtain the transaction history of the given coin from the database while generating an insufficient funds errors.
 HttpStatus: 500
 
 Value: 1015
 Name: EXCHANGE_GENERIC_COIN_CONFLICTING_AGE_HASH
 Description: The same coin was already used with a different age hash previously.
 HttpStatus: 409
 
 Value: 1016
 Name: EXCHANGE_GENERIC_INVALID_DENOMINATION_CIPHER_FOR_OPERATION
 Description: The requested operation is not valid for the cipher used by the selected denomination.
 HttpStatus: 400
 
 Value: 1017
 Name: EXCHANGE_GENERIC_CIPHER_MISMATCH
 Description: The provided arguments for the operation use inconsistent ciphers.
 HttpStatus: 400
 
 Value: 1018
 Name: EXCHANGE_GENERIC_NEW_DENOMS_ARRAY_SIZE_EXCESSIVE
 Description: The number of denominations specified in the request exceeds the limit of the exchange.
 HttpStatus: 400
 
 Value: 1019
 Name: EXCHANGE_GENERIC_COIN_UNKNOWN
 Description: The coin is not known to the exchange (yet).
 HttpStatus: 404
 
 Value: 1020
 Name: EXCHANGE_GENERIC_CLOCK_SKEW
 Description: The time at the server is too far off from the time specified in the request. Most likely the client system time is wrong.
 HttpStatus: 400
 
 Value: 1021
 Name: EXCHANGE_GENERIC_AMOUNT_EXCEEDS_DENOMINATION_VALUE
 Description: The specified amount for the coin is higher than the value of the denomination of the coin.
 HttpStatus: 400
 
 Value: 1022
 Name: EXCHANGE_GENERIC_GLOBAL_FEES_MISSING
 Description: The exchange was not properly configured with global fees.
 HttpStatus: 500
 
 Value: 1023
 Name: EXCHANGE_GENERIC_WIRE_FEES_MISSING
 Description: The exchange was not properly configured with wire fees.
 HttpStatus: 500
 
 Value: 1024
 Name: EXCHANGE_GENERIC_PURSE_PUB_MALFORMED
 Description: The purse public key was malformed.
 HttpStatus: 400
 
 Value: 1025
 Name: EXCHANGE_GENERIC_PURSE_UNKNOWN
 Description: The purse is unknown.
 HttpStatus: 404
 
 Value: 1026
 Name: EXCHANGE_GENERIC_PURSE_EXPIRED
 Description: The purse has expired.
 HttpStatus: 410
 
 Value: 1027
 Name: EXCHANGE_GENERIC_RESERVE_UNKNOWN
 Description: The exchange has no information about the `reserve_pub` that was provided.
 HttpStatus: 404
 
 Value: 1028
 Name: EXCHANGE_GENERIC_KYC_REQUIRED
 Description: The exchange is not allowed to proceed with the operation until the client has satisfied a KYC check.
 HttpStatus: 451
 
 Value: 1029
 Name: EXCHANGE_PURSE_DEPOSIT_COIN_CONFLICTING_ATTEST_VS_AGE_COMMITMENT
 Description: The provided age commitment and attestation are inconsistent: either both must be provided or neither may be provided.
 HttpStatus: 400
 
 Value: 1030
 Name: EXCHANGE_PURSE_DEPOSIT_COIN_AGE_ATTESTATION_FAILURE
 Description: The provided attestation for the minimum age could not be verified by the exchange.
 HttpStatus: 400
 
 Value: 1031
 Name: EXCHANGE_GENERIC_PURSE_DELETED
 Description: The purse was deleted.
 HttpStatus: 410
 
 Value: 1032
 Name: EXCHANGE_GENERIC_AML_OFFICER_PUB_MALFORMED
 Description: The public key of the AML officer in the URL was malformed.
 HttpStatus: 400
 
 Value: 1033
 Name: EXCHANGE_GENERIC_AML_OFFICER_GET_SIGNATURE_INVALID
 Description: The signature affirming the GET request of the AML officer is invalid.
 HttpStatus: 403
 
 Value: 1034
 Name: EXCHANGE_GENERIC_AML_OFFICER_ACCESS_DENIED
 Description: The specified AML officer does not have access at this time.
 HttpStatus: 403
 
 Value: 1035
 Name: EXCHANGE_GENERIC_AML_PENDING
 Description: The requested operation is denied pending the resolution of an anti-money laundering investigation by the exchange operator. This is a manual process, please wait and retry later.
 HttpStatus: 451
 
 Value: 1036
 Name: EXCHANGE_GENERIC_AML_FROZEN
 Description: The requested operation is denied as the account was frozen on suspicion of money laundering. Please contact the exchange operator.
 HttpStatus: 451
 
 Value: 1037
 Name: EXCHANGE_GENERIC_KYC_CONVERTER_FAILED
 Description: The exchange failed to start a KYC attribute conversion helper process. It is likely configured incorrectly.
 HttpStatus: 500
 
 Value: 1038
 Name: EXCHANGE_GENERIC_KYC_FAILED
 Description: The KYC operation failed. This could be because the KYC provider rejected the KYC data provided, or because the user aborted the KYC process.
 HttpStatus: 500
 
 Value: 1039
 Name: EXCHANGE_GENERIC_KYC_FALLBACK_FAILED
 Description: A fallback measure for a KYC operation failed. This is a bug. Users should contact the exchange operator.
 HttpStatus: 500
 
 Value: 1040
 Name: EXCHANGE_GENERIC_KYC_FALLBACK_UNKNOWN
 Description: The specified fallback measure for a KYC operation is unknown. This is a bug. Users should contact the exchange operator.
 HttpStatus: 500
 
 Value: 1041
 Name: EXCHANGE_GENERIC_BANK_ACCOUNT_UNKNOWN
 Description: The exchange is not aware of the bank account (payto URI or hash thereof) specified in the request and thus cannot perform the requested operation. The client should check that the selected account is correct.
 HttpStatus: 404
 
 Value: 1042
 Name: EXCHANGE_GENERIC_AML_PROGRAM_RECURSION_DETECTED
 Description: The AML processing at the exchange did not terminate in an adequate timeframe. This is likely a configuration problem at the payment service provider. Users should contact the exchange operator.
 HttpStatus: 500
 
 Value: 1043
 Name: EXCHANGE_GENERIC_KYC_SANCTION_LIST_CHECK_FAILED
 Description: A check against sanctions lists failed. This indicates an internal error in the sanctions-list processing logic. The exchange operator should investigate.
 HttpStatus: 500
 
 Value: 1044
 Name: EXCHANGE_GENERIC_TYPST_TEMPLATE_FAILURE
 Description: The process to generate a PDF from a template failed. A likely cause is a syntactic error in the template. This needs to be investigated by the exchange operator.
 HttpStatus: 500
 
 Value: 1045
 Name: EXCHANGE_GENERIC_PDFTK_FAILURE
 Description: A process to combine multiple PDFs into one larger document failed. A likely cause is a resource exhaustion problem on the server. This needs to be investigated by the exchange operator.
 HttpStatus: 500
 
 Value: 1046
 Name: EXCHANGE_GENERIC_TYPST_CRASH
 Description: The process to generate a PDF from a template crashed. A likely cause is a bug in the Typst software. This needs to be investigated by the exchange operator.
 HttpStatus: 500
 
 Value: 1047
 Name: EXCHANGE_GENERIC_PDFTK_CRASH
 Description: The process to combine multiple PDFs into a larger document crashed. A likely cause is a bug in the pdftk software. This needs to be investigated by the exchange operator.
 HttpStatus: 500
 
 Value: 1048
 Name: EXCHANGE_GENERIC_NO_TYPST_OR_PDFTK
 Description: One of the binaries needed to generate the PDF is not installed. If this feature is required, the system administrator should make sure Typst and pdftk are both installed.
 HttpStatus: 501
 
 Value: 1049
 Name: EXCHANGE_GENERIC_TARGET_ACCOUNT_UNKNOWN
 Description: The exchange is not aware of the given target account. The specified account is not a customer of this service.
 HttpStatus: 404
 
 Value: 1050
 Name: EXCHANGE_GENERIC_AML_OFFICER_READ_ONLY
 Description: The specified AML officer does not have write access at this time.
 HttpStatus: 409
 
 Value: 1100
 Name: EXCHANGE_DEPOSITS_GET_NOT_FOUND
 Description: The exchange did not find information about the specified transaction in the database.
 HttpStatus: 404
 
 Value: 1101
 Name: EXCHANGE_DEPOSITS_GET_INVALID_H_WIRE
 Description: The wire hash given to the `/deposits/` handler was malformed.
 HttpStatus: 400
 
 Value: 1102
 Name: EXCHANGE_DEPOSITS_GET_INVALID_MERCHANT_PUB
 Description: The merchant key given to the `/deposits/` handler was malformed.
 HttpStatus: 400
 
 Value: 1103
 Name: EXCHANGE_DEPOSITS_GET_INVALID_H_CONTRACT_TERMS
 Description: The hash of the contract terms given to the `/deposits/` handler was malformed.
 HttpStatus: 400
 
 Value: 1104
 Name: EXCHANGE_DEPOSITS_GET_INVALID_COIN_PUB
 Description: The coin public key given to the `/deposits/` handler was malformed.
 HttpStatus: 400
 
 Value: 1105
 Name: EXCHANGE_DEPOSITS_GET_INVALID_SIGNATURE_BY_EXCHANGE
 Description: The signature returned by the exchange in a `/deposits/` request was malformed.
 HttpStatus: 0
 
 Value: 1106
 Name: EXCHANGE_DEPOSITS_GET_MERCHANT_SIGNATURE_INVALID
 Description: The signature of the merchant is invalid.
 HttpStatus: 403
 
 Value: 1107
 Name: EXCHANGE_DEPOSITS_POLICY_NOT_ACCEPTED
 Description: The provided policy data was not accepted.
 HttpStatus: 400
 
 Value: 1150
 Name: EXCHANGE_WITHDRAW_INSUFFICIENT_FUNDS
 Description: The given reserve does not have sufficient funds to admit the requested withdrawal operation at this time. The response includes the current `balance` of the reserve and the transaction `history` that led to this balance.
 HttpStatus: 409
 
 Value: 1151
 Name: EXCHANGE_AGE_WITHDRAW_INSUFFICIENT_FUNDS
 Description: The given reserve does not have sufficient funds to admit the requested age-withdrawal operation at this time. The response includes the current `balance` of the reserve and the transaction `history` that led to this balance.
 HttpStatus: 409
 
 Value: 1152
 Name: EXCHANGE_WITHDRAW_AMOUNT_FEE_OVERFLOW
 Description: The amount to withdraw together with the fee exceeds the numeric range for Taler amounts.  This is not a client failure, as the coin value and fees come from the exchange's configuration.
 HttpStatus: 500
 
 Value: 1153
 Name: EXCHANGE_WITHDRAW_SIGNATURE_FAILED
 Description: The exchange failed to create the signature using the denomination key.
 HttpStatus: 500
 
 Value: 1154
 Name: EXCHANGE_WITHDRAW_RESERVE_SIGNATURE_INVALID
 Description: The signature of the reserve is not valid.
 HttpStatus: 403
 
 Value: 1155
 Name: EXCHANGE_RESERVE_HISTORY_ERROR_INSUFFICIENT_FUNDS
 Description: Computing the reserve history resulted in a negative overall balance, which should be impossible.
 HttpStatus: 500
 
 Value: 1156
 Name: EXCHANGE_GET_RESERVE_HISTORY_ERROR_INSUFFICIENT_BALANCE
 Description: The reserve did not have sufficient funds in it to pay for a full reserve history statement.
 HttpStatus: 409
 
 Value: 1158
 Name: EXCHANGE_WITHDRAW_DENOMINATION_KEY_LOST
 Description: Withdraw period of the coin to be withdrawn is in the past.
 HttpStatus: 410
 
 Value: 1159
 Name: EXCHANGE_WITHDRAW_UNBLIND_FAILURE
 Description: The client failed to unblind the blind signature.
 HttpStatus: 0
 
 Value: 1160
 Name: EXCHANGE_WITHDRAW_NONCE_REUSE
 Description: The client reused a withdraw nonce, which is not allowed.
 HttpStatus: 409
 
 Value: 1161
 Name: EXCHANGE_WITHDRAW_COMMITMENT_UNKNOWN
 Description: The client provided an unknown commitment for an age-withdraw request.
 HttpStatus: 400
 
 Value: 1162
 Name: EXCHANGE_WITHDRAW_AMOUNT_OVERFLOW
 Description: The total sum of amounts from the denominations did overflow.
 HttpStatus: 400
 
 Value: 1163
 Name: EXCHANGE_AGE_WITHDRAW_AMOUNT_INCORRECT
 Description: The total sum of value and fees from the denominations differs from the committed amount with fees.
 HttpStatus: 400
 
 Value: 1164
 Name: EXCHANGE_WITHDRAW_REVEAL_INVALID_HASH
 Description: The original commitment differs from the calculated hash.
 HttpStatus: 400
 
 Value: 1165
 Name: EXCHANGE_WITHDRAW_MAXIMUM_AGE_TOO_LARGE
 Description: The maximum age in the commitment is too large for the reserve.
 HttpStatus: 409
 
 Value: 1175
 Name: EXCHANGE_WITHDRAW_IDEMPOTENT_PLANCHET
 Description: The withdraw operation included the same planchet more than once. This is not allowed.
 HttpStatus: 400
 
 Value: 1205
 Name: EXCHANGE_DEPOSIT_COIN_SIGNATURE_INVALID
 Description: The signature made by the coin over the deposit permission is not valid.
 HttpStatus: 403
 
 Value: 1206
 Name: EXCHANGE_DEPOSIT_CONFLICTING_CONTRACT
 Description: The same coin was already deposited for the same merchant and contract with other details.
 HttpStatus: 409
 
 Value: 1207
 Name: EXCHANGE_DEPOSIT_NEGATIVE_VALUE_AFTER_FEE
 Description: The stated value of the coin after the deposit fee is subtracted would be negative.
 HttpStatus: 400
 
 Value: 1208
 Name: EXCHANGE_DEPOSIT_REFUND_DEADLINE_AFTER_WIRE_DEADLINE
 Description: The stated refund deadline is after the wire deadline.
 HttpStatus: 400
 
 Value: 1209
 Name: EXCHANGE_DEPOSIT_WIRE_DEADLINE_IS_NEVER
 Description: The stated wire deadline is `never`, which is not allowed.
 HttpStatus: 400
 
 Value: 1210
 Name: EXCHANGE_DEPOSIT_INVALID_WIRE_FORMAT_JSON
 Description: The exchange failed to canonicalize and hash the given wire format. For example, the merchant failed to provide the `salt` or a valid `payto://` URI in the wire details. Note that the exchange performs only basic sanity checking on the wire details; it cannot guarantee that the banking system can route funds to the specified address, even if this check succeeds.
 HttpStatus: 400
 
 Value: 1211
 Name: EXCHANGE_DEPOSIT_INVALID_WIRE_FORMAT_CONTRACT_HASH_CONFLICT
 Description: The hash of the given wire address does not match the wire hash specified in the proposal data.
 HttpStatus: 400
 
 Value: 1221
 Name: EXCHANGE_DEPOSIT_INVALID_SIGNATURE_BY_EXCHANGE
 Description: The signature provided by the exchange is not valid.
 HttpStatus: 0
 
 Value: 1222
 Name: EXCHANGE_DEPOSIT_FEE_ABOVE_AMOUNT
 Description: The deposited amount is smaller than the deposit fee, which would result in a negative contribution.
 HttpStatus: 400
 
 
 Value: 1240
 Name: EXCHANGE_EXTENSIONS_INVALID_FULFILLMENT
 Description: The proof of policy fulfillment was invalid.
 HttpStatus: 400
 
 
 Value: 1251
 Name: EXCHANGE_COIN_HISTORY_BAD_SIGNATURE
 Description: The coin history was requested with a bad signature.
 HttpStatus: 403
 
 Value: 1252
 Name: EXCHANGE_RESERVE_HISTORY_BAD_SIGNATURE
 Description: The reserve history was requested with a bad signature.
 HttpStatus: 403
 
 
 Value: 1302
 Name: EXCHANGE_MELT_FEES_EXCEED_CONTRIBUTION
 Description: The exchange encountered melt fees exceeding the melted coin's contribution.
 HttpStatus: 400
 
 Value: 1303
 Name: EXCHANGE_MELT_COIN_SIGNATURE_INVALID
 Description: The signature made with the coin to be melted is invalid.
 HttpStatus: 403
 
 Value: 1305
 Name: EXCHANGE_MELT_COIN_EXPIRED_NO_ZOMBIE
 Description: The denomination of the given coin has passed its expiration date and is not a valid zombie (that is, it was not refreshed with the fresh coin being subjected to recoup).
 HttpStatus: 400
 
 Value: 1306
 Name: EXCHANGE_MELT_INVALID_SIGNATURE_BY_EXCHANGE
 Description: The signature returned by the exchange in a melt request was malformed.
 HttpStatus: 0
 
 
 Value: 1353
 Name: EXCHANGE_REFRESHES_REVEAL_COMMITMENT_VIOLATION
 Description: The provided transfer keys do not match up with the original commitment.  Information about the original commitment is included in the response.
 HttpStatus: 409
 
 Value: 1354
 Name: EXCHANGE_REFRESHES_REVEAL_SIGNING_ERROR
 Description: Failed to produce the blinded signatures over the coins to be returned.
 HttpStatus: 500
 
 Value: 1355
 Name: EXCHANGE_REFRESHES_REVEAL_SESSION_UNKNOWN
 Description: The exchange is unaware of the refresh session specified in the request.
 HttpStatus: 404
 
 Value: 1356
 Name: EXCHANGE_REFRESHES_REVEAL_CNC_TRANSFER_ARRAY_SIZE_INVALID
 Description: The size of the cut-and-choose dimension of the private transfer keys request does not match #TALER_CNC_KAPPA - 1.
 HttpStatus: 400
 
 Value: 1358
 Name: EXCHANGE_REFRESHES_REVEAL_NEW_DENOMS_ARRAY_SIZE_MISMATCH
 Description: The number of envelopes given does not match the number of denomination keys given.
 HttpStatus: 400
 
 Value: 1359
 Name: EXCHANGE_REFRESHES_REVEAL_COST_CALCULATION_OVERFLOW
 Description: The exchange encountered a numeric overflow totaling up the cost for the refresh operation.
 HttpStatus: 500
 
 Value: 1360
 Name: EXCHANGE_REFRESHES_REVEAL_AMOUNT_INSUFFICIENT
 Description: The exchange's cost calculation shows that the melt amount is below the costs of the transaction.
 HttpStatus: 400
 
 Value: 1361
 Name: EXCHANGE_REFRESHES_REVEAL_LINK_SIGNATURE_INVALID
 Description: The signature made with the coin over the link data is invalid.
 HttpStatus: 403
 
 Value: 1362
 Name: EXCHANGE_REFRESHES_REVEAL_INVALID_RCH
 Description: The refresh session hash given to the `/refreshes/` handler was malformed.
 HttpStatus: 400
 
 Value: 1363
 Name: EXCHANGE_REFRESHES_REVEAL_OPERATION_INVALID
 Description: The specified operation is invalid for this endpoint.
 HttpStatus: 400
 
 Value: 1364
 Name: EXCHANGE_REFRESHES_REVEAL_AGE_RESTRICTION_NOT_SUPPORTED
 Description: The client provided age commitment data, but age restriction is not supported on this server.
 HttpStatus: 400
 
 Value: 1365
 Name: EXCHANGE_REFRESHES_REVEAL_AGE_RESTRICTION_COMMITMENT_INVALID
 Description: The client provided invalid age commitment data: missing, not an array, or  array of invalid size.
 HttpStatus: 400
 
 
 Value: 1400
 Name: EXCHANGE_LINK_COIN_UNKNOWN
 Description: The coin specified in the link request is unknown to the exchange.
 HttpStatus: 404
 
 Value: 1450
 Name: EXCHANGE_TRANSFERS_GET_WTID_MALFORMED
 Description: The public key given to the `/transfers/` handler was malformed.
 HttpStatus: 400
 
 Value: 1451
 Name: EXCHANGE_TRANSFERS_GET_WTID_NOT_FOUND
 Description: The exchange did not find information about the specified wire transfer identifier in the database.
 HttpStatus: 404
 
 Value: 1452
 Name: EXCHANGE_TRANSFERS_GET_WIRE_FEE_NOT_FOUND
 Description: The exchange did not find information about the wire transfer fees it charged.
 HttpStatus: 500
 
 Value: 1453
 Name: EXCHANGE_TRANSFERS_GET_WIRE_FEE_INCONSISTENT
 Description: The exchange found a wire fee that was above the total transfer value (and thus could not have been charged).
 HttpStatus: 500
 
 Value: 1475
 Name: EXCHANGE_PURSES_INVALID_WAIT_TARGET
 Description: The wait target of the URL was not in the set of expected values.
 HttpStatus: 400
 
 Value: 1476
 Name: EXCHANGE_PURSES_GET_INVALID_SIGNATURE_BY_EXCHANGE
 Description: The signature on the purse status returned by the exchange was invalid.
 HttpStatus: 0
 
 
 Value: 1500
 Name: EXCHANGE_REFUND_COIN_NOT_FOUND
 Description: The exchange has no information about the coin to be refunded. Without a transaction history, it cannot issue a refund. This is acceptable; the owner should refresh the coin directly without executing the refund.
 HttpStatus: 404
 
 Value: 1501
 Name: EXCHANGE_REFUND_CONFLICT_DEPOSIT_INSUFFICIENT
 Description: The refund request could not be processed because the coin's transaction history does not permit it: the refunds would exceed the deposit amount. The `history` in the response demonstrates this.
 HttpStatus: 409
 
 Value: 1502
 Name: EXCHANGE_REFUND_DEPOSIT_NOT_FOUND
 Description: The exchange knows about the coin to be refunded, but not about the specific `/deposit` operation. Therefore, it cannot issue a refund because it does not know whether this merchant public key is authorized to issue one.
 HttpStatus: 404
 
 Value: 1503
 Name: EXCHANGE_REFUND_MERCHANT_ALREADY_PAID
 Description: The exchange can no longer refund the customer or coin because the money was already transferred to the merchant. The refund deadline has passed.
 HttpStatus: 410
 
 Value: 1504
 Name: EXCHANGE_REFUND_FEE_TOO_LOW
 Description: The refund fee specified for the request is lower than the refund fee charged by the exchange for the given denomination key of the refunded coin.
 HttpStatus: 400
 
 Value: 1505
 Name: EXCHANGE_REFUND_FEE_ABOVE_AMOUNT
 Description: The refunded amount is smaller than the refund fee, which would result in a negative refund.
 HttpStatus: 400
 
 Value: 1506
 Name: EXCHANGE_REFUND_MERCHANT_SIGNATURE_INVALID
 Description: The signature of the merchant is invalid.
 HttpStatus: 403
 
 Value: 1507
 Name: EXCHANGE_REFUND_MERCHANT_SIGNING_FAILED
 Description: Merchant backend failed to create the refund confirmation signature.
 HttpStatus: 500
 
 Value: 1508
 Name: EXCHANGE_REFUND_INVALID_SIGNATURE_BY_EXCHANGE
 Description: The signature returned by the exchange in a refund request was malformed.
 HttpStatus: 0
 
 Value: 1509
 Name: EXCHANGE_REFUND_INVALID_FAILURE_PROOF_BY_EXCHANGE
 Description: The failure proof returned by the exchange is incorrect.
 HttpStatus: 0
 
 Value: 1510
 Name: EXCHANGE_REFUND_INCONSISTENT_AMOUNT
 Description: Conflicting refund granted before with different amount but same refund transaction ID.
 HttpStatus: 424
 
 Value: 1550
 Name: EXCHANGE_RECOUP_SIGNATURE_INVALID
 Description: The given coin signature is invalid for the request.
 HttpStatus: 403
 
 Value: 1551
 Name: EXCHANGE_RECOUP_WITHDRAW_NOT_FOUND
 Description: The exchange could not find the corresponding withdraw operation. The request is denied.
 HttpStatus: 404
 
 Value: 1552
 Name: EXCHANGE_RECOUP_COIN_BALANCE_ZERO
 Description: The coin's remaining balance is zero.  The request is denied.
 HttpStatus: 403
 Note: dead in latest cde
 
 Value: 1553
 Name: EXCHANGE_RECOUP_BLINDING_FAILED
 Description: The exchange failed to reproduce the coin's blinding.
 HttpStatus: 500
 
 Value: 1554
 Name: EXCHANGE_RECOUP_COIN_BALANCE_NEGATIVE
 Description: The coin's remaining balance is zero.  The request is denied.
 HttpStatus: 500
 Note: dead in latest cde
 
 Value: 1555
 Name: EXCHANGE_RECOUP_NOT_ELIGIBLE
 Description: The coin's denomination has not been revoked yet.
 HttpStatus: 404
 
 Value: 1575
 Name: EXCHANGE_RECOUP_REFRESH_SIGNATURE_INVALID
 Description: The given coin signature is invalid for the request.
 HttpStatus: 403
 
 Value: 1576
 Name: EXCHANGE_RECOUP_REFRESH_MELT_NOT_FOUND
 Description: The exchange could not find the corresponding melt operation. The request is denied.
 HttpStatus: 404
 
 Value: 1578
 Name: EXCHANGE_RECOUP_REFRESH_BLINDING_FAILED
 Description: The exchange failed to reproduce the coin's blinding.
 HttpStatus: 500
 
 Value: 1580
 Name: EXCHANGE_RECOUP_REFRESH_NOT_ELIGIBLE
 Description: The coin's denomination has not been revoked yet.
 HttpStatus: 404
 
 
 Value: 1600
 Name: EXCHANGE_KEYS_TIMETRAVEL_FORBIDDEN
 Description: This exchange does not allow clients to request `/keys` for times other than the current exchange time.
 HttpStatus: 403
 
 Value: 1650
 Name: EXCHANGE_WIRE_SIGNATURE_INVALID
 Description: A signature in the server's response was malformed.
 HttpStatus: 0
 
 Value: 1651
 Name: EXCHANGE_WIRE_NO_ACCOUNTS_CONFIGURED
 Description: No bank accounts are enabled for the exchange. The administrator should enable an account using the `taler-exchange-offline` tool.
 HttpStatus: 500
 
 Value: 1652
 Name: EXCHANGE_WIRE_INVALID_PAYTO_CONFIGURED
 Description: The payto:// URI stored in the exchange database for its bank account is malformed.
 HttpStatus: 500
 
 Value: 1653
 Name: EXCHANGE_WIRE_FEES_NOT_CONFIGURED
 Description: No wire fees are configured for an enabled wire method of the exchange. The administrator must set the wire-fee using the taler-exchange-offline tool.
 HttpStatus: 500
 
 
 Value: 1675
 Name: EXCHANGE_RESERVES_PURSE_CREATE_CONFLICTING_META_DATA
 Description: This purse was previously created with different metadata.
 HttpStatus: 409
 
 Value: 1676
 Name: EXCHANGE_RESERVES_PURSE_MERGE_CONFLICTING_META_DATA
 Description: This purse was previously merged with different metadata.
 HttpStatus: 409
 
 Value: 1677
 Name: EXCHANGE_RESERVES_PURSE_CREATE_INSUFFICIENT_FUNDS
 Description: The reserve has insufficient funds to create another purse.
 HttpStatus: 409
 
 Value: 1678
 Name: EXCHANGE_RESERVES_PURSE_FEE_TOO_LOW
 Description: The purse fee specified for the request is lower than the purse fee charged by the exchange at this time.
 HttpStatus: 400
 
 Value: 1679
 Name: EXCHANGE_PURSE_DELETE_ALREADY_DECIDED
 Description: The payment request cannot be deleted anymore, as it either already completed or timed out.
 HttpStatus: 409
 
 Value: 1680
 Name: EXCHANGE_PURSE_DELETE_SIGNATURE_INVALID
 Description: The signature affirming the purse deletion is invalid.
 HttpStatus: 403
 
 Value: 1681
 Name: EXCHANGE_RESERVES_AGE_RESTRICTION_REQUIRED
 Description: Withdrawal from the reserve requires age restriction to be set.
 HttpStatus: 403
 
 Value: 1700
 Name: EXCHANGE_DENOMINATION_HELPER_UNAVAILABLE
 Description: The exchange failed to talk to the process responsible for its private denomination keys or the helpers had no denominations (properly) configured.
 HttpStatus: 502
 
 Value: 1701
 Name: EXCHANGE_DENOMINATION_HELPER_BUG
 Description: The response from the denomination key helper process was malformed.
 HttpStatus: 500
 
 Value: 1702
 Name: EXCHANGE_DENOMINATION_HELPER_TOO_EARLY
 Description: The helper refuses to sign with the key, because it is too early: the validity period has not yet started.
 HttpStatus: 400
 
 Value: 1725
 Name: EXCHANGE_PURSE_DEPOSIT_EXCHANGE_SIGNATURE_INVALID
 Description: The exchange's signature on the response was invalid.
 HttpStatus: 0
 
 
 Value: 1750
 Name: EXCHANGE_SIGNKEY_HELPER_UNAVAILABLE
 Description: The exchange failed to talk to the process responsible for its private signing keys.
 HttpStatus: 502
 
 Value: 1751
 Name: EXCHANGE_SIGNKEY_HELPER_BUG
 Description: The response from the online signing key helper process was malformed.
 HttpStatus: 500
 
 Value: 1752
 Name: EXCHANGE_SIGNKEY_HELPER_TOO_EARLY
 Description: The helper refuses to sign with the key, because it is too early: the validity period has not yet started.
 HttpStatus: 400
 
 Value: 1753
 Name: EXCHANGE_SIGNKEY_HELPER_OFFLINE_MISSING
 Description: The signatures from the master exchange public key are missing, thus the exchange cannot currently sign its API responses. The exchange operator must use taler-exchange-offline to sign the current key material.
 HttpStatus: 500
 
 
 
 Value: 1775
 Name: EXCHANGE_RESERVES_PURSE_EXPIRATION_BEFORE_NOW
 Description: The purse expiration time is in the past at the time of its creation.
 HttpStatus: 400
 
 Value: 1776
 Name: EXCHANGE_RESERVES_PURSE_EXPIRATION_IS_NEVER
 Description: The purse expiration time is set to never, which is not allowed.
 HttpStatus: 400
 
 Value: 1777
 Name: EXCHANGE_RESERVES_PURSE_MERGE_SIGNATURE_INVALID
 Description: The signature affirming the merge of the purse is invalid.
 HttpStatus: 403
 
 Value: 1778
 Name: EXCHANGE_RESERVES_RESERVE_MERGE_SIGNATURE_INVALID
 Description: The signature by the reserve affirming the merge is invalid.
 HttpStatus: 403
 
 Value: 1785
 Name: EXCHANGE_RESERVES_OPEN_BAD_SIGNATURE
 Description: The signature by the reserve affirming the open operation is invalid.
 HttpStatus: 403
 
 Value: 1786
 Name: EXCHANGE_RESERVES_CLOSE_BAD_SIGNATURE
 Description: The signature by the reserve affirming the close operation is invalid.
 HttpStatus: 403
 
 Value: 1787
 Name: EXCHANGE_RESERVES_ATTEST_BAD_SIGNATURE
 Description: The signature by the reserve affirming the attestation request is invalid.
 HttpStatus: 403
 
 Value: 1788
 Name: EXCHANGE_RESERVES_CLOSE_NO_TARGET_ACCOUNT
 Description: The exchange does not know an origin account to which the remaining reserve balance could be wired to, and the wallet failed to provide one.
 HttpStatus: 409
 
 Value: 1789
 Name: EXCHANGE_RESERVES_OPEN_INSUFFICIENT_FUNDS
 Description: The reserve balance is insufficient to pay for the open operation.
 HttpStatus: 409
 
 Value: 1790
 Name: EXCHANGE_RESERVES_OPEN_COIN_SIGNATURE_INVALID
 Description: A coin signature for a deposit to pay to open the reserve is invalid.
 HttpStatus: 403
 
 Value: 1800
 Name: EXCHANGE_MANAGEMENT_AUDITOR_NOT_FOUND
 Description: The auditor that was supposed to be disabled is unknown to this exchange.
 HttpStatus: 404
 
 Value: 1801
 Name: EXCHANGE_MANAGEMENT_AUDITOR_MORE_RECENT_PRESENT
 Description: The exchange has a more recently signed conflicting instruction and is thus refusing the current change (replay detected).
 HttpStatus: 409
 
 Value: 1802
 Name: EXCHANGE_MANAGEMENT_AUDITOR_ADD_SIGNATURE_INVALID
 Description: The signature to add or enable the auditor does not validate.
 HttpStatus: 403
 
 Value: 1803
 Name: EXCHANGE_MANAGEMENT_AUDITOR_DEL_SIGNATURE_INVALID
 Description: The signature to disable the auditor does not validate.
 HttpStatus: 403
 
 Value: 1804
 Name: EXCHANGE_MANAGEMENT_DENOMINATION_REVOKE_SIGNATURE_INVALID
 Description: The signature to revoke the denomination does not validate.
 HttpStatus: 403
 
 Value: 1805
 Name: EXCHANGE_MANAGEMENT_SIGNKEY_REVOKE_SIGNATURE_INVALID
 Description: The signature to revoke the online signing key does not validate.
 HttpStatus: 403
 
 Value: 1806
 Name: EXCHANGE_MANAGEMENT_WIRE_MORE_RECENT_PRESENT
 Description: The exchange has a more recently signed conflicting instruction and is thus refusing the current change (replay detected).
 HttpStatus: 409
 
 Value: 1807
 Name: EXCHANGE_MANAGEMENT_KEYS_SIGNKEY_UNKNOWN
 Description: The signingkey specified is unknown to the exchange.
 HttpStatus: 404
 
 Value: 1808
 Name: EXCHANGE_MANAGEMENT_WIRE_DETAILS_SIGNATURE_INVALID
 Description: The signature to publish wire account does not validate.
 HttpStatus: 403
 
 Value: 1809
 Name: EXCHANGE_MANAGEMENT_WIRE_ADD_SIGNATURE_INVALID
 Description: The signature to add the wire account does not validate.
 HttpStatus: 403
 
 Value: 1810
 Name: EXCHANGE_MANAGEMENT_WIRE_DEL_SIGNATURE_INVALID
 Description: The signature to disable the wire account does not validate.
 HttpStatus: 403
 
 Value: 1811
 Name: EXCHANGE_MANAGEMENT_WIRE_NOT_FOUND
 Description: The wire account to be disabled is unknown to the exchange.
 HttpStatus: 404
 
 Value: 1812
 Name: EXCHANGE_MANAGEMENT_WIRE_FEE_SIGNATURE_INVALID
 Description: The signature to affirm wire fees does not validate.
 HttpStatus: 403
 
 Value: 1813
 Name: EXCHANGE_MANAGEMENT_WIRE_FEE_MISMATCH
 Description: The signature conflicts with a previous signature affirming different fees.
 HttpStatus: 409
 
 Value: 1814
 Name: EXCHANGE_MANAGEMENT_KEYS_DENOMKEY_ADD_SIGNATURE_INVALID
 Description: The signature affirming the denomination key is invalid.
 HttpStatus: 403
 
 Value: 1815
 Name: EXCHANGE_MANAGEMENT_KEYS_SIGNKEY_ADD_SIGNATURE_INVALID
 Description: The signature affirming the signing key is invalid.
 HttpStatus: 403
 
 Value: 1816
 Name: EXCHANGE_MANAGEMENT_GLOBAL_FEE_MISMATCH
 Description: The signature conflicts with a previous signature affirming different fees.
 HttpStatus: 409
 
 Value: 1817
 Name: EXCHANGE_MANAGEMENT_GLOBAL_FEE_SIGNATURE_INVALID
 Description: The signature affirming the fee structure is invalid.
 HttpStatus: 403
 
 Value: 1818
 Name: EXCHANGE_MANAGEMENT_DRAIN_PROFITS_SIGNATURE_INVALID
 Description: The signature affirming the profit drain is invalid.
 HttpStatus: 403
 
 Value: 1825
 Name: EXCHANGE_AML_DECISION_ADD_SIGNATURE_INVALID
 Description: The signature affirming the AML decision is invalid.
 HttpStatus: 403
 
 Value: 1826
 Name: EXCHANGE_AML_DECISION_INVALID_OFFICER
 Description: The AML officer specified is not allowed to make AML decisions right now.
 HttpStatus: 403
 
 Value: 1827
 Name: EXCHANGE_AML_DECISION_MORE_RECENT_PRESENT
 Description: There is a more recent AML decision on file. The decision was rejected as timestamps of AML decisions must be monotonically increasing.
 HttpStatus: 409
 
 Value: 1828
 Name: EXCHANGE_AML_DECISION_UNKNOWN_CHECK
 Description: The AML decision would impose an AML check of a type that is not provided by any KYC provider known to the exchange.
 HttpStatus: 400
 
 Value: 1830
 Name: EXCHANGE_MANAGEMENT_UPDATE_AML_OFFICER_SIGNATURE_INVALID
 Description: The signature affirming the change in the AML officer status is invalid.
 HttpStatus: 403
 
 Value: 1831
 Name: EXCHANGE_MANAGEMENT_AML_OFFICERS_MORE_RECENT_PRESENT
 Description: A more recent decision about the AML officer status is known to the exchange.
 HttpStatus: 409
 
 Value: 1832
 Name: EXCHANGE_MANAGEMENT_CONFLICTING_DENOMINATION_META_DATA
 Description: The exchange already has this denomination key configured, but with different metadata. This should not be possible; contact the developers for support.
 HttpStatus: 409
 
 Value: 1833
 Name: EXCHANGE_MANAGEMENT_CONFLICTING_SIGNKEY_META_DATA
 Description: The exchange already has this signing key configured, but with different metadata. This should not be possible; contact the developers for support.
 HttpStatus: 409
 
 
 
 Value: 1850
 Name: EXCHANGE_PURSE_CREATE_CONFLICTING_META_DATA
 Description: The purse was previously created with different metadata.
 HttpStatus: 409
 
 Value: 1851
 Name: EXCHANGE_PURSE_CREATE_CONFLICTING_CONTRACT_STORED
 Description: The purse was previously created with a different contract.
 HttpStatus: 409
 
 Value: 1852
 Name: EXCHANGE_PURSE_CREATE_COIN_SIGNATURE_INVALID
 Description: A coin signature for a deposit into the purse is invalid.
 HttpStatus: 403
 
 Value: 1853
 Name: EXCHANGE_PURSE_CREATE_EXPIRATION_BEFORE_NOW
 Description: The purse expiration time is in the past.
 HttpStatus: 400
 
 Value: 1854
 Name: EXCHANGE_PURSE_CREATE_EXPIRATION_IS_NEVER
 Description: The purse expiration time is `never`.
 HttpStatus: 400
 
 Value: 1855
 Name: EXCHANGE_PURSE_CREATE_SIGNATURE_INVALID
 Description: The purse signature over the purse metadata is invalid.
 HttpStatus: 403
 
 Value: 1856
 Name: EXCHANGE_PURSE_ECONTRACT_SIGNATURE_INVALID
 Description: The signature over the encrypted contract is invalid.
 HttpStatus: 403
 
 Value: 1857
 Name: EXCHANGE_PURSE_CREATE_EXCHANGE_SIGNATURE_INVALID
 Description: The signature from the exchange over the confirmation is invalid.
 HttpStatus: 0
 
 Value: 1858
 Name: EXCHANGE_PURSE_DEPOSIT_CONFLICTING_META_DATA
 Description: The coin was previously deposited with different metadata.
 HttpStatus: 409
 
 Value: 1859
 Name: EXCHANGE_PURSE_ECONTRACT_CONFLICTING_META_DATA
 Description: The encrypted contract was previously uploaded with different metadata.
 HttpStatus: 409
 
 Value: 1860
 Name: EXCHANGE_CREATE_PURSE_NEGATIVE_VALUE_AFTER_FEE
 Description: The deposited amount is less than the purse fee.
 HttpStatus: 400
 
 Value: 1876
 Name: EXCHANGE_PURSE_MERGE_INVALID_MERGE_SIGNATURE
 Description: The signature using the merge key is invalid.
 HttpStatus: 403
 
 Value: 1877
 Name: EXCHANGE_PURSE_MERGE_INVALID_RESERVE_SIGNATURE
 Description: The signature using the reserve key is invalid.
 HttpStatus: 403
 
 Value: 1878
 Name: EXCHANGE_PURSE_NOT_FULL
 Description: The targeted purse is not yet full and thus cannot be merged. Retrying the request later may succeed.
 HttpStatus: 409
 
 Value: 1879
 Name: EXCHANGE_PURSE_MERGE_EXCHANGE_SIGNATURE_INVALID
 Description: The signature from the exchange over the confirmation is invalid.
 HttpStatus: 0
 
 Value: 1880
 Name: EXCHANGE_MERGE_PURSE_PARTNER_UNKNOWN
 Description: The exchange of the target account is not a partner of this exchange.
 HttpStatus: 404
 
 Value: 1890
 Name: EXCHANGE_MANAGEMENT_ADD_PARTNER_SIGNATURE_INVALID
 Description: The signature affirming the new partner is invalid.
 HttpStatus: 403
 
 Value: 1891
 Name: EXCHANGE_MANAGEMENT_ADD_PARTNER_DATA_CONFLICT
 Description: Conflicting data for the partner already exists with the exchange.
 HttpStatus: 409
 
 
 Value: 1900
 Name: EXCHANGE_AUDITORS_AUDITOR_SIGNATURE_INVALID
 Description: The auditor signature over the denomination metadata is invalid.
 HttpStatus: 403
 
 Value: 1901
 Name: EXCHANGE_AUDITORS_AUDITOR_UNKNOWN
 Description: The auditor that was specified is unknown to this exchange.
 HttpStatus: 412
 
 Value: 1902
 Name: EXCHANGE_AUDITORS_AUDITOR_INACTIVE
 Description: The auditor that was specified is no longer used by this exchange.
 HttpStatus: 410
 
 Value: 1917
 Name: EXCHANGE_KYC_INVALID_FORM_SUBMITTED
 Description: The client submitted the wrong form for the request. This is some invalid use of the API. Please contact technical support.
 HttpStatus: 409
 
 Value: 1918
 Name: EXCHANGE_KYC_GENERIC_AML_PROGRAM_TIMEOUT
 Description: The exchange tried to run an AML program, but that program did not terminate on time. Contact the exchange operator to address the AML program bug or performance issue. If it is not a performance issue, the timeout might have to be increased (requires changes to the source code).
 HttpStatus: 500
 
 Value: 1919
 Name: EXCHANGE_KYC_INFO_AUTHORIZATION_FAILED
 Description: The KYC info access token is not recognized. Hence the request was denied.
 HttpStatus: 403
 
 Value: 1920
 Name: EXCHANGE_KYC_RECURSIVE_RULE_DETECTED
 Description: The exchange got stuck in a long series of likely recursive KYC rules without user input, preventing a timely conclusion. This is a configuration failure. The administrator should investigate.
 HttpStatus: 500
 
 Value: 1921
 Name: EXCHANGE_KYC_AML_FORM_INCOMPLETE
 Description: The submitted KYC data lacks an attribute that is required by the KYC form. Please submit the complete form.
 HttpStatus: 400
 
 Value: 1922
 Name: EXCHANGE_KYC_GENERIC_AML_PROGRAM_GONE
 Description: The request requires an AML program which is no longer configured at the exchange. Contact the exchange operator to address the configuration issue.
 HttpStatus: 500
 
 Value: 1923
 Name: EXCHANGE_KYC_NOT_A_FORM
 Description: The given check is not of type 'form' and thus using this handler for form submission is incorrect.
 HttpStatus: 400
 
 Value: 1924
 Name: EXCHANGE_KYC_GENERIC_CHECK_GONE
 Description: The request requires a check which is no longer configured at the exchange. Contact the exchange operator to address the configuration issue.
 HttpStatus: 500
 
 Value: 1925
 Name: EXCHANGE_KYC_WALLET_SIGNATURE_INVALID
 Description: The signature affirming the wallet's KYC request was invalid.
 HttpStatus: 403
 
 Value: 1926
 Name: EXCHANGE_KYC_PROOF_BACKEND_INVALID_RESPONSE
 Description: The exchange received an unexpected malformed response from its KYC backend.
 HttpStatus: 502
 
 Value: 1927
 Name: EXCHANGE_KYC_PROOF_BACKEND_ERROR
 Description: The backend signaled an unexpected failure.
 HttpStatus: 502
 
 Value: 1928
 Name: EXCHANGE_KYC_PROOF_BACKEND_AUTHORIZATION_FAILED
 Description: The backend signaled an authorization failure.
 HttpStatus: 403
 
 Value: 1929
 Name: EXCHANGE_KYC_PROOF_REQUEST_UNKNOWN
 Description: The exchange is unaware of having made the authorization request.
 HttpStatus: 404
 
 Value: 1930
 Name: EXCHANGE_KYC_CHECK_AUTHORIZATION_FAILED
 Description: The KYC authorization signature was invalid. Hence the request was denied.
 HttpStatus: 403
 
 Value: 1931
 Name: EXCHANGE_KYC_GENERIC_LOGIC_UNKNOWN
 Description: The request used a logic specifier that is not known to the exchange.
 HttpStatus: 404
 
 Value: 1932
 Name: EXCHANGE_KYC_GENERIC_LOGIC_GONE
 Description: The request requires a logic which is no longer configured at the exchange.
 HttpStatus: 500
 
 Value: 1933
 Name: EXCHANGE_KYC_GENERIC_LOGIC_BUG
 Description: The logic plugin had a bug in its interaction with the KYC provider.
 HttpStatus: 500
 
 Value: 1934
 Name: EXCHANGE_KYC_GENERIC_PROVIDER_ACCESS_REFUSED
 Description: The exchange could not process the request with its KYC provider because the provider refused access to the service. This indicates some configuration issue at the Taler exchange operator.
 HttpStatus: 511
 
 Value: 1935
 Name: EXCHANGE_KYC_GENERIC_PROVIDER_TIMEOUT
 Description: There was a timeout in the interaction between the exchange and the KYC provider. The most likely cause is some networking problem. Trying again later might succeed.
 HttpStatus: 504
 
 Value: 1936
 Name: EXCHANGE_KYC_GENERIC_PROVIDER_UNEXPECTED_REPLY
 Description: The KYC provider responded with a status that was completely unexpected by the KYC logic of the exchange.
 HttpStatus: 502
 
 Value: 1937
 Name: EXCHANGE_KYC_GENERIC_PROVIDER_RATE_LIMIT_EXCEEDED
 Description: The rate limit of the exchange at the KYC provider has been exceeded. Trying much later might work.
 HttpStatus: 503
 
 Value: 1938
 Name: EXCHANGE_KYC_WEBHOOK_UNAUTHORIZED
 Description: The request to the webhook lacked proper authorization or authentication data.
 HttpStatus: 401
 
 Value: 1939
 Name: EXCHANGE_KYC_CHECK_REQUEST_UNKNOWN
 Description: The exchange is unaware of the requested payto URI with respect to the KYC status.
 HttpStatus: 404
 
 Value: 1940
 Name: EXCHANGE_KYC_CHECK_AUTHORIZATION_KEY_UNKNOWN
 Description: The exchange has no account public key to check the KYC authorization signature against. Hence the request was denied. The user should do a wire transfer to the exchange with the KYC authorization key in the subject.
 HttpStatus: 409
 
 Value: 1941
 Name: EXCHANGE_KYC_FORM_ALREADY_UPLOADED
 Description: The form was previously uploaded and may only be submitted once. The user should be redirected to the main KYC page to determine whether further steps are required.
 HttpStatus: 409
 
 Value: 1942
 Name: EXCHANGE_KYC_MEASURES_MALFORMED
 Description: The internal state of the exchange specifying KYC measures is malformed. Please contact technical support.
 HttpStatus: 500
 
 Value: 1943
 Name: EXCHANGE_KYC_MEASURE_INDEX_INVALID
 Description: The specified index does not refer to a valid KYC measure. Please check the URL.
 HttpStatus: 404
 
 Value: 1944
 Name: EXCHANGE_KYC_INVALID_LOGIC_TO_CHECK
 Description: The operation is not supported by the selected KYC logic. This is either caused by a configuration change or some invalid use of the API. Please contact technical support.
 HttpStatus: 409
 
 Value: 1945
 Name: EXCHANGE_KYC_AML_PROGRAM_FAILURE
 Description: The AML program failed. This is either caused by a configuration change or a bug. Please contact technical support.
 HttpStatus: 500
 
 Value: 1946
 Name: EXCHANGE_KYC_AML_PROGRAM_MALFORMED_RESULT
 Description: The AML program returned a malformed result. This is a bug. Please contact technical support.
 HttpStatus: 500
 
 Value: 1947
 Name: EXCHANGE_KYC_GENERIC_PROVIDER_INCOMPLETE_REPLY
 Description: The response from the KYC provider lacked required attributes. Please contact technical support.
 HttpStatus: 502
 
 Value: 1948
 Name: EXCHANGE_KYC_GENERIC_PROVIDER_INCOMPLETE_CONTEXT
 Description: The context of the KYC check lacked required fields. This is a bug. Please contact technical support.
 HttpStatus: 500
 
 Value: 1949
 Name: EXCHANGE_KYC_GENERIC_AML_LOGIC_BUG
 Description: The logic plugin had a bug in its AML processing. This is a bug. Please contact technical support.
 HttpStatus: 500
 
 Value: 1950
 Name: EXCHANGE_CONTRACTS_UNKNOWN
 Description: The exchange does not know a contract under the given contract public key.
 HttpStatus: 404
 
 Value: 1951
 Name: EXCHANGE_CONTRACTS_INVALID_CONTRACT_PUB
 Description: The URL does not encode a valid exchange public key in its path.
 HttpStatus: 400
 
 Value: 1952
 Name: EXCHANGE_CONTRACTS_DECRYPTION_FAILED
 Description: The returned encrypted contract did not decrypt.
 HttpStatus: 0
 
 Value: 1953
 Name: EXCHANGE_CONTRACTS_SIGNATURE_INVALID
 Description: The signature on the encrypted contract did not validate.
 HttpStatus: 0
 
 Value: 1954
 Name: EXCHANGE_CONTRACTS_DECODING_FAILED
 Description: The decrypted contract was malformed.
 HttpStatus: 0
 
 Value: 1975
 Name: EXCHANGE_PURSE_DEPOSIT_COIN_SIGNATURE_INVALID
 Description: A coin signature for a deposit into the purse is invalid.
 HttpStatus: 403
 
 Value: 1976
 Name: EXCHANGE_PURSE_DEPOSIT_DECIDED_ALREADY
 Description: It is too late to deposit coins into the purse.
 HttpStatus: 410
 
 Value: 1977
 Name: EXCHANGE_KYC_INFO_BUSY
 Description: The exchange is currently processing the KYC status and is not able to return a response yet.
 HttpStatus: 202
 
 
 Value: 1980
 Name: EXCHANGE_TOTP_KEY_INVALID
 Description: TOTP key is not valid.
 HttpStatus: 0
 
 
 
 
 # 2000 - 2999: Reserved for merchant
 # 2000 - 2099: Reserved for MERCHANT_GENERIC
 
 Value: 2000
 Name: MERCHANT_GENERIC_INSTANCE_UNKNOWN
 Description: The backend could not find the merchant instance specified in the request.
 HttpStatus: 404
 
 Value: 2001
 Name: MERCHANT_GENERIC_HOLE_IN_WIRE_FEE_STRUCTURE
 Description: The start and end-times in the wire fee structure leave a hole. This is not allowed.
 HttpStatus: 0
 
 Value: 2002
 Name: MERCHANT_GENERIC_EXCHANGE_MASTER_KEY_MISMATCH
 Description: The master key of the exchange does not match the one configured for this merchant. As a result, the merchant refuses to do business with this exchange. The administrator should check whether the exchange is configured correctly in the merchant backend.
 HttpStatus: 502
 
 Value: 2003
 Name: MERCHANT_GENERIC_CATEGORY_UNKNOWN
 Description: The product category is not known to the backend.
 HttpStatus: 404
 
 Value: 2004
 Name: MERCHANT_GENERIC_UNIT_UNKNOWN
 Description: The unit referenced in the request is not known to the backend.
 HttpStatus: 404
 
 Value: 2005
 Name: MERCHANT_GENERIC_ORDER_UNKNOWN
 Description: The proposal is not known to the backend.
 HttpStatus: 404
 
 Value: 2006
 Name: MERCHANT_GENERIC_PRODUCT_UNKNOWN
 Description: The order provided to the backend could not be completed because a product specified through inventory data is not in the inventory.
 HttpStatus: 404
 
 Value: 2007
 Name: MERCHANT_GENERIC_REWARD_ID_UNKNOWN
 Description: The reward ID is unknown.  This could happen if the reward has expired.
 HttpStatus: 404
 
 Value: 2008
 Name: MERCHANT_GENERIC_DB_CONTRACT_CONTENT_INVALID
 Description: The contract obtained from the merchant backend was malformed.
 HttpStatus: 500
 
 Value: 2009
 Name: MERCHANT_GENERIC_CONTRACT_HASH_DOES_NOT_MATCH_ORDER
 Description: The order we found does not match the provided contract hash.
 HttpStatus: 403
 
 Value: 2010
 Name: MERCHANT_GENERIC_EXCHANGE_KEYS_FAILURE
 Description: The exchange failed to provide a valid response to the merchant's /keys request.
 HttpStatus: 502
 
 Value: 2011
 Name: MERCHANT_GENERIC_EXCHANGE_TIMEOUT
 Description: The exchange failed to respond to the merchant on time.
 HttpStatus: 504
 
 Value: 2012
 Name: MERCHANT_GENERIC_EXCHANGE_CONNECT_FAILURE
 Description: The merchant failed to talk to the exchange.
 HttpStatus: 500
 
 Value: 2013
 Name: MERCHANT_GENERIC_EXCHANGE_REPLY_MALFORMED
 Description: The exchange returned a malformed response.
 HttpStatus: 502
 
 Value: 2014
 Name: MERCHANT_GENERIC_EXCHANGE_UNEXPECTED_STATUS
 Description: The exchange returned an unexpected response status.
 HttpStatus: 502
 
 Value: 2015
 Name: MERCHANT_GENERIC_UNAUTHORIZED
 Description: The merchant refused the request due to lack of authorization.
 HttpStatus: 401
 
 Value: 2016
 Name: MERCHANT_GENERIC_INSTANCE_DELETED
 Description: The merchant instance specified in the request was deleted.
 HttpStatus: 404
 
 Value: 2017
 Name: MERCHANT_GENERIC_TRANSFER_UNKNOWN
 Description: The backend could not find the inbound wire transfer specified in the request.
 HttpStatus: 404
 
 Value: 2018
 Name: MERCHANT_GENERIC_TEMPLATE_UNKNOWN
 Description: The backend could not find the template with the specified ID because it does not exist.
 HttpStatus: 404
 
 Value: 2019
 Name: MERCHANT_GENERIC_WEBHOOK_UNKNOWN
 Description: The backend could not find the webhook with the specified ID because it does not exist.
 HttpStatus: 404
 
 Value: 2020
 Name: MERCHANT_GENERIC_PENDING_WEBHOOK_UNKNOWN
 Description: The backend could not find the webhook with the specified serial because it does not exist.
 HttpStatus: 404
 
 Value: 2021
 Name: MERCHANT_GENERIC_OTP_DEVICE_UNKNOWN
 Description: The backend could not find the OTP device with the specified ID because it does not exist.
 HttpStatus: 404
 
 Value: 2022
 Name: MERCHANT_GENERIC_ACCOUNT_UNKNOWN
 Description: The account is not known to the backend.
 HttpStatus: 404
 
 Value: 2023
 Name: MERCHANT_GENERIC_H_WIRE_MALFORMED
 Description: The wire hash was malformed.
 HttpStatus: 400
 
 Value: 2024
 Name: MERCHANT_GENERIC_CURRENCY_MISMATCH
 Description: The currency specified in the operation does not work with the current state of the given resource.
 HttpStatus: 409
 
 Value: 2025
 Name: MERCHANT_GENERIC_EXCHANGE_UNTRUSTED
 Description: The exchange specified in the operation is not trusted by this exchange. The client should limit its operation to exchanges enabled by the merchant, or ask the merchant to enable additional exchanges in the configuration.
 HttpStatus: 400
 
 Value: 2026
 Name: MERCHANT_GENERIC_TOKEN_FAMILY_UNKNOWN
 Description: The token family is not known to the backend.
 HttpStatus: 404
 
 Value: 2027
 Name: MERCHANT_GENERIC_TOKEN_KEY_UNKNOWN
 Description: The token family key is not known to the backend. Check the local system time on the client, maybe an expired (or not yet valid) token was used.
 HttpStatus: 404
 
 Value: 2028
 Name: MERCHANT_GENERIC_DONAU_NOT_CONFIGURED
 Description: The merchant backend is not configured to support the DONAU protocol.
 HttpStatus: 501
 
 Value: 2029
 Name: MERCHANT_EXCHANGE_SIGN_PUB_UNKNOWN
 Description: The public signing key given in the exchange response is not in the current keys response.  It is possible that the operation will succeed later after the merchant has downloaded an updated keys response.
 HttpStatus: 0
 
 Value: 2030
 Name: MERCHANT_GENERIC_FEATURE_NOT_AVAILABLE
 Description: The merchant backend does not support the requested feature.
 HttpStatus: 501
 
 Value: 2031
 Name: MERCHANT_GENERIC_MFA_MISSING
 Description: This operation requires multi-factor authorization, but the instance does not have enough configured factors that can be validated. The system administrator must perform this operation.
 HttpStatus: 403
 
 Value: 2032
 Name: MERCHANT_GENERIC_DONAU_INVALID_RESPONSE
 Description: A donation authority (Donau) provided an invalid response. This should be analyzed by the administrator. Trying again later may help.
 HttpStatus: 502
 
 Value: 2033
 Name: MERCHANT_GENERIC_UNIT_BUILTIN
 Description: The unit referenced in the request is built-in and cannot be modified or deleted.
 HttpStatus: 409
 
 Value: 2034
 Name: MERCHANT_GENERIC_REPORT_UNKNOWN
 Description: The report ID provided to the backend is not known to the backend.
 HttpStatus: 404
 
 Value: 2035
 Name: MERCHANT_GENERIC_REPORT_GENERATOR_UNCONFIGURED
 Description: The report ID provided to the backend is not known to the backend.
 HttpStatus: 501
 
 Value: 2036
 Name: MERCHANT_GENERIC_PRODUCT_GROUP_UNKNOWN
 Description: The product group ID provided to the backend is not known to the backend.
 HttpStatus: 404
 
 Value: 2037
 Name: MERCHANT_GENERIC_MONEY_POT_UNKNOWN
 Description: The money pod ID provided to the backend is not known to the backend.
 HttpStatus: 404
 
 Value: 2038
 Name: MERCHANT_GENERIC_SESSION_UNKNOWN
 Description: The session ID provided to the backend is not known to the backend.
 HttpStatus: 404
 
 Value: 2039
 Name: MERCHANT_GENERIC_DONAU_CHARITY_UNKNOWN
 Description: The merchant does not have a charity associated with the selected Donau. As a result, it cannot generate the requested donation receipt. This could happen if the charity was removed from the backend between order creation and payment.
 HttpStatus: 404
 
 Value: 2040
 Name: MERCHANT_GENERIC_EXPECTED_TRANSFER_UNKNOWN
 Description: The merchant does not expect a transfer with the given ID and therefore cannot return any details about it.
 HttpStatus: 404
 
 Value: 2041
 Name: MERCHANT_GENERIC_DONAU_UNKNOWN
 Description: The Donau is not known to the backend.
 HttpStatus: 404
 
 Value: 2042
 Name: MERCHANT_GENERIC_ACCESS_TOKEN_UNKNOWN
 Description: The access token is not known to the backend.
 HttpStatus: 404
 
 Value: 2043
 Name: MERCHANT_GENERIC_FOUNTAIN_UNKNOWN
 Description: The fountain is not known to the backend.
 HttpStatus: 404
 
 Value: 2048
 Name: MERCHANT_GENERIC_NO_TYPST_OR_PDFTK
 Description: One of the binaries needed to generate the PDF is not installed. If this feature is required, the system administrator should make sure Typst and pdftk are both installed.
 HttpStatus: 501
 
 
 
 
 # 2100-2499: public API
 # 2100-2124: get orders endpoint
 
 Value: 2100
 Name: MERCHANT_GET_ORDERS_EXCHANGE_TRACKING_FAILURE
 Description: The exchange failed to provide a valid answer to the tracking request, thus those details are not in the response.
 HttpStatus: 200
 
 Value: 2103
 Name: MERCHANT_GET_ORDERS_ID_EXCHANGE_REQUEST_FAILURE
 Description: The merchant backend failed to construct the request for tracking to the exchange, thus tracking details are not in the response.
 HttpStatus: 500
 
 Value: 2104
 Name: MERCHANT_GET_ORDERS_ID_EXCHANGE_LOOKUP_START_FAILURE
 Description: The merchant backend failed trying to contact the exchange for tracking details, thus those details are not in the response.
 HttpStatus: 500
 
 Value: 2105
 Name: MERCHANT_GET_ORDERS_ID_INVALID_TOKEN
 Description: The claim token used to authenticate the client is invalid for this order.
 HttpStatus: 403
 
 Value: 2106
 Name: MERCHANT_GET_ORDERS_ID_INVALID_CONTRACT_HASH
 Description: The contract terms hash used to authenticate the client is invalid for this order.
 HttpStatus: 403
 
 Value: 2107
 Name: MERCHANT_GET_ORDERS_ID_INVALID_CONTRACT_VERSION
 Description: The contract terms version is not understood by the merchant backend. Most likely the merchant backend was downgraded to a version incompatible with the content of the database.
 HttpStatus: 500
 
 
 # 2125-2149: multi-factor authentication
 
 Value: 2125
 Name: MERCHANT_TAN_CHALLENGE_FAILED
 Description: The provided TAN code is invalid for this challenge.
 HttpStatus: 409
 
 Value: 2126
 Name: MERCHANT_TAN_CHALLENGE_UNKNOWN
 Description: The backend is not aware of the specified MFA challenge.
 HttpStatus: 404
 
 Value: 2127
 Name: MERCHANT_TAN_TOO_MANY_ATTEMPTS
 Description: There have been too many attempts to solve the challenge. A new TAN must be requested.
 HttpStatus: 429
 
 Value: 2128
 Name: MERCHANT_TAN_MFA_HELPER_EXEC_FAILED
 Description: The backend failed to launch a helper process required for the multi-factor authentication step. The backend operator should check the logs and fix the Taler merchant backend configuration.
 HttpStatus: 502
 
 Value: 2129
 Name: MERCHANT_TAN_CHALLENGE_SOLVED
 Description: The challenge was already solved. Therefore, the service refuses to send it again.
 HttpStatus: 410
 
 Value: 2130
 Name: MERCHANT_TAN_TOO_EARLY
 Description: It is too early to request another transmission of the challenge. The client should wait and see if they received the previous challenge.
 HttpStatus: 429
 
 Value: 2131
 Name: MERCHANT_MFA_FORBIDDEN
 Description: There have been too many attempts to solve MFA. The client may attempt again in the future.
 HttpStatus: 403
 
 Value: 2132
 Name: MERCHANT_TAN_ADDRESS_UNUSABLE
 Description: The transmission helper rejected the address configured for this multi-factor authentication step: it is malformed, of the wrong length, not a mobile subscription, unallocated, or blocked. The address should be corrected.
 HttpStatus: 400
 
 Value: 2133
 Name: MERCHANT_TAN_ADDRESS_UNREACHABLE
 Description: The address is valid but the recipient could not be reached: the handset is switched off or out of coverage, or the message expired before delivery. Retrying later may succeed.
 HttpStatus: 503
 
 Value: 2134
 Name: MERCHANT_TAN_HELPER_MISCONFIGURED
 Description: The transmission helper is misconfigured: a required credential is absent, the configured credentials were refused by the provider, or the provider account has insufficient balance. The backend operator should check the logs and fix the Taler merchant backend configuration.
 HttpStatus: 500
 
 # 2150-2199: post orders ID pay endpoint
 
 Value: 2150
 Name: MERCHANT_POST_ORDERS_ID_PAY_INSUFFICIENT_FUNDS
 Description: The exchange responded saying that funds were insufficient (for example, due to double-spending).
 HttpStatus: 409
 
 Value: 2151
 Name: MERCHANT_POST_ORDERS_ID_PAY_DENOMINATION_KEY_NOT_FOUND
 Description: The denomination key used for payment is not listed among the denomination keys of the exchange.
 HttpStatus: 400
 
 Value: 2152
 Name: MERCHANT_POST_ORDERS_ID_PAY_DENOMINATION_KEY_AUDITOR_FAILURE
 Description: The denomination key used for payment is not audited by an auditor approved by the merchant.
 HttpStatus: 400
 
 Value: 2153
 Name: MERCHANT_POST_ORDERS_ID_PAY_AMOUNT_OVERFLOW
 Description: There was an integer overflow totaling up the amounts or deposit fees in the payment.
 HttpStatus: 500
 
 Value: 2154
 Name: MERCHANT_POST_ORDERS_ID_PAY_FEES_EXCEED_PAYMENT
 Description: The deposit fees exceed the total value of the payment.
 HttpStatus: 400
 
 Value: 2155
 Name: MERCHANT_POST_ORDERS_ID_PAY_INSUFFICIENT_DUE_TO_FEES
 Description: After considering deposit and wire fees, the payment is insufficient to satisfy the required amount for the contract.  The client should revisit the logic used to calculate fees it must cover.
 HttpStatus: 400
 
 Value: 2156
 Name: MERCHANT_POST_ORDERS_ID_PAY_PAYMENT_INSUFFICIENT
 Description: Even without considering deposit and wire fees, the payment is insufficient to satisfy the required amount for the contract.
 HttpStatus: 400
 
 Value: 2157
 Name: MERCHANT_POST_ORDERS_ID_PAY_COIN_SIGNATURE_INVALID
 Description: The signature over the contract of one of the coins was invalid.
 HttpStatus: 403
 
 Value: 2158
 Name: MERCHANT_POST_ORDERS_ID_PAY_EXCHANGE_LOOKUP_FAILED
 Description: The merchant backend failed to find information about the exchange to issue the deposit. This usually happens when the merchant backend's HTTP client logic is not working.
 HttpStatus: 500
 
 Value: 2159
 Name: MERCHANT_POST_ORDERS_ID_PAY_REFUND_DEADLINE_PAST_WIRE_TRANSFER_DEADLINE
 Description: The refund deadline in the contract is after the transfer deadline.
 HttpStatus: 500
 
 Value: 2160
 Name: MERCHANT_POST_ORDERS_ID_PAY_ALREADY_PAID
 Description: The order was already paid (maybe by another wallet).
 HttpStatus: 409
 
 Value: 2161
 Name: MERCHANT_POST_ORDERS_ID_PAY_OFFER_EXPIRED
 Description: The payment is too late, the offer has expired.
 HttpStatus: 410
 
 Value: 2162
 Name: MERCHANT_POST_ORDERS_ID_PAY_MERCHANT_FIELD_MISSING
 Description: The `merchant` field is missing from the proposal data. This is an internal error because the proposal comes from the merchant's own database at this point.
 HttpStatus: 500
 
 Value: 2163
 Name: MERCHANT_POST_ORDERS_ID_PAY_WIRE_HASH_UNKNOWN
 Description: Failed to locate merchant's account information matching the wire hash given in the proposal.
 HttpStatus: 500
 
 Value: 2165
 Name: MERCHANT_POST_ORDERS_ID_PAY_DENOMINATION_DEPOSIT_EXPIRED
 Description: The deposit time for the denomination has expired.
 HttpStatus: 410
 
 Value: 2166
 Name: MERCHANT_POST_ORDERS_ID_PAY_EXCHANGE_WIRE_FEE_ADDITION_FAILED
 Description: The exchange of the deposited coin charges a wire fee that could not be added to the total (total amount too high).
 HttpStatus: 500
 
 Value: 2167
 Name: MERCHANT_POST_ORDERS_ID_PAY_REFUNDED
 Description: The contract was not fully paid because of refunds. Clients may treat it as paid if, for example, the contract must be executed despite refunds.
 HttpStatus: 402
 
 Value: 2168
 Name: MERCHANT_POST_ORDERS_ID_PAY_REFUNDS_EXCEED_PAYMENTS
 Description: The database indicates that more was refunded than was paid, which should not be possible.
 HttpStatus: 500
 
 Value: 2169
 Name: MERCHANT_PRIVATE_POST_REFUND_AFTER_WIRE_DEADLINE
 Description: The refund request is too late because it is past the wire transfer deadline of the order. The merchant must find a different way to pay back the money to the customer.
 HttpStatus: 410
 
 Value: 2170
 Name: MERCHANT_POST_ORDERS_ID_PAY_EXCHANGE_FAILED
 Description: The payment failed at the exchange.
 HttpStatus: 502
 
 Value: 2171
 Name: MERCHANT_POST_ORDERS_ID_PAY_AGE_COMMITMENT_MISSING
 Description: The payment required a minimum age but one of the coins (of a denomination with support for age restriction) did not provide any age_commitment.
 HttpStatus: 400
 
 Value: 2172
 Name: MERCHANT_POST_ORDERS_ID_PAY_AGE_COMMITMENT_SIZE_MISMATCH
 Description: The payment required a minimum age but one of the coins provided an age_commitment that contained a wrong number of public keys compared to the number of age groups defined in the denomination of the coin.
 HttpStatus: 400
 
 Value: 2173
 Name: MERCHANT_POST_ORDERS_ID_PAY_AGE_VERIFICATION_FAILED
 Description: The payment required a minimum age, but one of the coins provided a `minimum_age_sig` that could not be verified with the given `age_commitment` for that minimum age.
 HttpStatus: 400
 
 Value: 2174
 Name: MERCHANT_POST_ORDERS_ID_PAY_AGE_COMMITMENT_HASH_MISSING
 Description: The payment required no minimum age but one of the coins (of a denomination with support for age restriction) did not provide the required h_age_commitment.
 HttpStatus: 400
 
 Value: 2175
 Name: MERCHANT_POST_ORDERS_ID_PAY_WIRE_METHOD_UNSUPPORTED
 Description: The exchange does not support the selected bank account of the merchant. Likely the merchant had stale data on the bank accounts of the exchange and thus selected an inappropriate exchange when making the offer.
 HttpStatus: 409
 
 Value: 2176
 Name: MERCHANT_POST_ORDERS_ID_PAY_CHOICE_INDEX_MISSING
 Description: The payment requires the wallet to select a choice from the choices array and pass it in the 'choice_index' field of the request.
 HttpStatus: 400
 
 Value: 2177
 Name: MERCHANT_POST_ORDERS_ID_PAY_CHOICE_INDEX_OUT_OF_BOUNDS
 Description: The 'choice_index' field is invalid.
 HttpStatus: 400
 
 Value: 2178
 Name: MERCHANT_POST_ORDERS_ID_PAY_INPUT_TOKENS_MISMATCH
 Description: The provided 'tokens' array does not match with the required input tokens of the order.
 HttpStatus: 400
 
 Value: 2179
 Name: MERCHANT_POST_ORDERS_ID_PAY_TOKEN_ISSUE_SIG_INVALID
 Description: Invalid token issue signature (blindly signed by merchant) for provided token.
 HttpStatus: 400
 
 Value: 2180
 Name: MERCHANT_POST_ORDERS_ID_PAY_TOKEN_USE_SIG_INVALID
 Description: Invalid token use signature (EdDSA, signed by wallet) for provided token.
 HttpStatus: 400
 
 Value: 2181
 Name: MERCHANT_POST_ORDERS_ID_PAY_TOKEN_COUNT_MISMATCH
 Description: The provided number of tokens does not match the required number.
 HttpStatus: 400
 
 Value: 2182
 Name: MERCHANT_POST_ORDERS_ID_PAY_TOKEN_ENVELOPE_COUNT_MISMATCH
 Description: The provided number of token envelopes does not match the specified number.
 HttpStatus: 400
 
 Value: 2183
 Name: MERCHANT_POST_ORDERS_ID_PAY_TOKEN_INVALID
 Description: Invalid token because it was already used, is expired or not yet valid.
 HttpStatus: 409
 
 Value: 2184
 Name: MERCHANT_POST_ORDERS_ID_PAY_EXCHANGE_TRANSACTION_LIMIT_VIOLATION
 Description: The payment violates a transaction limit configured at the given exchange. The wallet failed to check exchange limits during coin selection. The wallet developer should investigate.
 HttpStatus: 400
 
 Value: 2185
 Name: MERCHANT_POST_ORDERS_ID_PAY_DONATION_AMOUNT_MISMATCH
 Description: The donation amount provided in the BKPS does not match the amount of the order choice.
 HttpStatus: 409
 
 Value: 2186
 Name: MERCHANT_POST_ORDERS_ID_PAY_EXCHANGE_LEGALLY_REFUSED
 Description: Some of the exchanges involved refused the request for reasons related to legitimization. The wallet should try with coins of different exchanges. The merchant should check if they have some legitimization process pending at the exchange.
 HttpStatus: 451
 
 Value: 2187
 Name: MERCHANT_POST_ORDERS_ID_PAY_CHOICE_INDEX_MISMATCH
 Description: The order was already paid, but the request specified a different choice. The client should use the choice with which the order was actually paid.
 HttpStatus: 409
 
 # 2200-2224: post orders ID paid endpoint
 
 Value: 2200
 Name: MERCHANT_POST_ORDERS_ID_PAID_CONTRACT_HASH_MISMATCH
 Description: The contract hash does not match the given order ID.
 HttpStatus: 400
 
 Value: 2201
 Name: MERCHANT_POST_ORDERS_ID_PAID_COIN_SIGNATURE_INVALID
 Description: The signature of the merchant is not valid for the given contract hash.
 HttpStatus: 403
 
 # 2225-2249: token families endpoints
 
 Value: 2225
 Name: MERCHANT_POST_TOKEN_FAMILY_CONFLICT
 Description: A token family with this ID but conflicting data exists.
 HttpStatus: 409
 
 Value: 2226
 Name: MERCHANT_PATCH_TOKEN_FAMILY_NOT_FOUND
 Description: The backend is unaware of a token family with the given ID.
 HttpStatus: 404
 
 
 # 2250-2256: post orders ID abort endpoint
 
 Value: 2251
 Name: MERCHANT_POST_ORDERS_ID_ABORT_EXCHANGE_REFUND_FAILED
 Description: The merchant failed to send the exchange the refund request.
 HttpStatus: 500
 
 Value: 2252
 Name: MERCHANT_POST_ORDERS_ID_ABORT_EXCHANGE_LOOKUP_FAILED
 Description: The merchant failed to find the exchange to process the lookup.
 HttpStatus: 500
 
 Value: 2253
 Name: MERCHANT_POST_ORDERS_ID_ABORT_CONTRACT_NOT_FOUND
 Description: The merchant could not find the contract.
 HttpStatus: 404
 
 Value: 2254
 Name: MERCHANT_POST_ORDERS_ID_ABORT_REFUND_REFUSED_PAYMENT_COMPLETE
 Description: The payment was already completed and thus cannot be aborted anymore.
 HttpStatus: 412
 
 Value: 2255
 Name: MERCHANT_POST_ORDERS_ID_ABORT_CONTRACT_HASH_MISSMATCH
 Description: The hash provided by the wallet does not match the order.
 HttpStatus: 403
 
 Value: 2256
 Name: MERCHANT_POST_ORDERS_ID_ABORT_COINS_ARRAY_EMPTY
 Description: The array of coins cannot be empty.
 HttpStatus: 400
 
 
 Value: 2258
 Name: MERCHANT_EXCHANGE_TRANSFERS_AWAITING_KEYS
 Description: The merchant is waiting for the exchange to provide key material before checking the wire transfer.
 HttpStatus: 202
 
 Value: 2259
 Name: MERCHANT_EXCHANGE_TRANSFERS_AWAITING_LIST
 Description: The merchant is waiting for the exchange to provide the list of aggregated transactions.
 HttpStatus: 202
 
 Value: 2260
 Name: MERCHANT_EXCHANGE_TRANSFERS_FATAL_NO_EXCHANGE
 Description: The endpoint indicated in the wire transfer does not belong to a GNU Taler exchange.
 HttpStatus: 200
 
 Value: 2261
 Name: MERCHANT_EXCHANGE_TRANSFERS_FATAL_NOT_FOUND
 Description: The exchange indicated in the wire transfer claims to know nothing about the wire transfer.
 HttpStatus: 0
 
 Value: 2262
 Name: MERCHANT_EXCHANGE_TRANSFERS_RATE_LIMITED
 Description: The interaction with the exchange is delayed due to rate limiting.
 HttpStatus: 202
 
 Value: 2263
 Name: MERCHANT_EXCHANGE_TRANSFERS_TRANSIENT_FAILURE
 Description: The merchant experienced a transient failure while interacting with the exchange.
 HttpStatus: 202
 
 Value: 2264
 Name: MERCHANT_EXCHANGE_TRANSFERS_HARD_FAILURE
 Description: The response from the exchange was unacceptable and should be reviewed with an auditor.
 HttpStatus: 200
 
 
 # 2275-2299: post accounts KYCAUTH endpoint
 
 Value: 2275
 Name: MERCHANT_POST_ACCOUNTS_KYCAUTH_BANK_GATEWAY_UNREACHABLE
 Description: The merchant backend failed to reach the banking gateway to shorten the wire transfer subject. This probably means that the banking gateway of the exchange is currently down. Contact the exchange operator or simply retry again later.
 HttpStatus: 502
 
 Value: 2276
 Name: MERCHANT_POST_ACCOUNTS_EXCHANGE_TOO_OLD
 Description: The merchant backend failed to reach the banking gateway to shorten the wire transfer subject. This probably means that the banking gateway of the exchange is currently down. Contact the exchange operator or simply retry again later.
 HttpStatus: 502
 
 Value: 2277
 Name: MERCHANT_POST_ACCOUNTS_KYCAUTH_EXCHANGE_UNREACHABLE
 Description: The merchant backend failed to reach the specified exchange. This probably means that the exchange is currently down. Contact the exchange operator or simply retry again later.
 HttpStatus: 502
 
 
 
 # 2300-2349: post orders ID claim endpoint
 
 Value: 2300
 Name: MERCHANT_POST_ORDERS_ID_CLAIM_NOT_FOUND
 Description: The order could not be claimed because the backend is unaware of it.
 HttpStatus: 404
 
 Value: 2301
 Name: MERCHANT_POST_ORDERS_ID_CLAIM_ALREADY_CLAIMED
 Description: The order could not be claimed because another client claimed it first.
 HttpStatus: 409
 
 Value: 2302
 Name: MERCHANT_POST_ORDERS_ID_CLAIM_CLIENT_INTERNAL_FAILURE
 Description: The client experienced an internal failure.
 HttpStatus: 0
 
 Value: 2303
 Name: MERCHANT_POST_ORDERS_UNCLAIM_SIGNATURE_INVALID
 Description: The unclaim signature of the wallet is not valid for the given contract hash.
 HttpStatus: 403
 
 
 # 2350-2399: post orders ID refund endpoint
 
 Value: 2350
 Name: MERCHANT_POST_ORDERS_ID_REFUND_SIGNATURE_FAILED
 Description: The backend failed to sign the refund request.
 HttpStatus: 0
 
 
 
 # 2400-2449: reward pickup endpoint
 
 Value: 2400
 Name: MERCHANT_REWARD_PICKUP_UNBLIND_FAILURE
 Description: The client failed to unblind the signature returned by the merchant.
 HttpStatus: 0
 
 
 
 Value: 2403
 Name: MERCHANT_REWARD_PICKUP_EXCHANGE_ERROR
 Description: The exchange returned a failure code for the withdraw operation.
 HttpStatus: 502
 
 
 Value: 2404
 Name: MERCHANT_REWARD_PICKUP_SUMMATION_FAILED
 Description: The merchant failed to add up the amounts to compute the pick up value.
 HttpStatus: 500
 
 Value: 2405
 Name: MERCHANT_REWARD_PICKUP_HAS_EXPIRED
 Description: The reward expired.
 HttpStatus: 410
 
 Value: 2406
 Name: MERCHANT_REWARD_PICKUP_AMOUNT_EXCEEDS_REWARD_REMAINING
 Description: The requested withdraw amount exceeds the amount remaining to be picked up.
 HttpStatus: 400
 
 Value: 2407
 Name: MERCHANT_REWARD_PICKUP_DENOMINATION_UNKNOWN
 Description: The merchant did not find the specified denomination key in the exchange's key set.
 HttpStatus: 409
 
 # 2450-2499: available for future public endpoint
 
 # 2500-2999: private API
 # 2500-2549: order operations
 
 Value: 2500
 Name: MERCHANT_PRIVATE_POST_ORDERS_INSTANCE_CONFIGURATION_LACKS_WIRE
 Description: The merchant instance has no active bank accounts configured. However, at least one bank account must be available to create new orders.
 HttpStatus: 404
 
 Value: 2501
 Name: MERCHANT_PRIVATE_POST_ORDERS_NO_LOCALTIME
 Description: The proposal had no timestamp and the merchant backend failed to obtain the current local time.
 HttpStatus: 500
 
 Value: 2502
 Name: MERCHANT_PRIVATE_POST_ORDERS_PROPOSAL_PARSE_ERROR
 Description: The order provided to the backend could not be parsed; likely some required fields were missing or ill-formed.
 HttpStatus: 400
 
 Value: 2503
 Name: MERCHANT_PRIVATE_POST_ORDERS_ALREADY_EXISTS
 Description: A conflicting order (sharing the same order identifier) already exists at this merchant backend instance.
 HttpStatus: 409
 
 Value: 2504
 Name: MERCHANT_PRIVATE_POST_ORDERS_REFUND_AFTER_WIRE_DEADLINE
 Description: The order creation request is invalid because the given wire deadline is before the refund deadline.
 HttpStatus: 400
 
 Value: 2505
 Name: MERCHANT_PRIVATE_POST_ORDERS_DELIVERY_DATE_IN_PAST
 Description: The order creation request is invalid because the delivery date given is in the past.
 HttpStatus: 400
 
 Value: 2506
 Name: MERCHANT_PRIVATE_POST_ORDERS_WIRE_DEADLINE_IS_NEVER
 Description: The order creation request is invalid because a wire deadline of `never` is not allowed.
 HttpStatus: 400
 
 Value: 2507
 Name: MERCHANT_PRIVATE_POST_ORDERS_PAY_DEADLINE_IN_PAST
 Description: The order creation request is invalid because the given payment deadline is in the past.
 HttpStatus: 400
 
 Value: 2508
 Name: MERCHANT_PRIVATE_POST_ORDERS_REFUND_DEADLINE_IN_PAST
 Description: The order creation request is invalid because the given refund deadline is in the past.
 HttpStatus: 400
 
 Value: 2509
 Name: MERCHANT_PRIVATE_POST_ORDERS_NO_EXCHANGES_FOR_WIRE_METHOD
 Description: The backend does not trust any exchange that would allow funds to be wired to a bank account of this instance using the wire method specified with the order. Exchange bank accounts with mandatory currency conversion are not currently supported. A likely cause is that the `taler-merchant-exchangekeyupdate` process is not running.
 HttpStatus: 409
 
 Value: 2510
 Name: MERCHANT_PRIVATE_PATCH_ORDERS_ID_FORGET_PATH_SYNTAX_INCORRECT
 Description: One of the paths to forget is malformed.
 HttpStatus: 400
 
 Value: 2511
 Name: MERCHANT_PRIVATE_PATCH_ORDERS_ID_FORGET_PATH_NOT_FORGETTABLE
 Description: One of the paths to forget was not marked as forgettable.
 HttpStatus: 409
 
 Value: 2512
 Name: MERCHANT_POST_ORDERS_ID_REFUND_EXCHANGE_TRANSACTION_LIMIT_VIOLATION
 Description: The refund amount would violate a refund transaction limit configured at the given exchange. The merchant should use another way to refund the customer and consult the exchange operator about the applicable regulations.
 HttpStatus: 451
 
 Value: 2513
 Name: MERCHANT_PRIVATE_POST_ORDERS_AMOUNT_EXCEEDS_LEGAL_LIMITS
 Description: The total order amount exceeds the legal transaction limits of the available exchanges, so a customer could not legally make this payment. The merchant may increase its limits by completing legitimization checks with exchange operators.
 HttpStatus: 451
 
 Value: 2514
 Name: MERCHANT_PRIVATE_POST_ORDERS_NO_EXCHANGE_FOR_CURRENCY
 Description: A currency specified to be paid in the contract is not supported by any exchange that this instance can currently use. Possible solutions include (1) specifying a different currency, (2) adding suitable exchange operators to the merchant backend configuration, or (3) satisfying the compliance rules of a configured exchange to begin using that provider's service.
 HttpStatus: 409
 
 
 # 2200-2224: post orders ID paid endpoint
 Value: 2520
 Name: MERCHANT_PRIVATE_DELETE_ORDERS_AWAITING_PAYMENT
 Description: The order provided to the backend could not be deleted because the offer is still valid and awaiting payment. Deletion may work after the offer expires if it remains unpaid.
 HttpStatus: 409
 
 Value: 2521
 Name: MERCHANT_PRIVATE_DELETE_ORDERS_ALREADY_PAID
 Description: The order provided to the backend could not be deleted as the order was already paid.
 HttpStatus: 409
 
 Value: 2525
 Name: MERCHANT_PRIVATE_GET_STATISTICS_REPORT_GRANULARITY_UNAVAILABLE
 Description: The client requested a report granularity that is not available at the backend. Possible solutions include extending the backend code and/or the database statistic triggers to support the desired data granularity. Alternatively, the client could request a different granularity.
 HttpStatus: 410
 
 Value: 2530
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_REFUND_INCONSISTENT_AMOUNT
 Description: The requested cumulative Taler refund is inconsistent: it is lower than the amount already awarded, exceeds the amount paid through Taler, or would make the combined Taler and external refunds exceed the full order total.
 HttpStatus: 409
 
 Value: 2531
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_REFUND_ORDER_UNPAID
 Description: Only paid orders can be refunded, and the frontend specified an unpaid order to issue a refund for.
 HttpStatus: 409
 
 Value: 2532
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_REFUND_NOT_ALLOWED_BY_CONTRACT
 Description: The refund delay was set to 0 and thus no refunds are ever allowed for this order.
 HttpStatus: 403
 
 Value: 2533
 Name: MERCHANT_PRIVATE_POST_ORDERS_TOKEN_FAMILY_SLUG_UNKNOWN
 Description: The token family slug provided in this order could not be found in the merchant database.
 HttpStatus: 404
 
 Value: 2534
 Name: MERCHANT_PRIVATE_POST_ORDERS_TOKEN_FAMILY_NOT_VALID
 Description: A token family referenced in this order is either expired or not valid yet.
 HttpStatus: 409
 
 Value: 2535
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_COLLECT_NOT_FREE
 Description: The order cannot be collected by the backend as it is not a genuinely free Taler payment: the Taler amount is not zero, or the selected choice has token inputs or outputs and thus requires a customer wallet.
 HttpStatus: 409
 
 Value: 2536
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_COLLECT_ALREADY_CLAIMED
 Description: The order cannot be collected by the backend as it was already claimed by a customer wallet. The wallet owns the order and must execute the free payment itself.
 HttpStatus: 409
 
 Value: 2537
 Name: MERCHANT_PRIVATE_DELETE_ORDERS_EXTERNALLY_PAID
 Description: The order provided to the backend could not be deleted as it has payments that were settled outside of Taler. Deletion requires an explicit force operation.
 HttpStatus: 409
 
 Value: 2538
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_REFUND_EXTERNAL_INCONSISTENT_AMOUNT
 Description: The external refund could not be recorded as the cumulative externally refunded amount would exceed the full order total minus the amount already refunded through Taler.
 HttpStatus: 409
 
 Value: 2539
 Name: MERCHANT_PRIVATE_POST_ORDERS_ID_REFUND_EXTERNAL_ALREADY_EXISTS
 Description: An external refund with the same identifier was already recorded for this order, but with different details.
 HttpStatus: 409
 
 # 2550-2569: transfer operations
 
 Value: 2550
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_EXCHANGE_UNKNOWN
 Description: The exchange says it does not know this transfer.
 HttpStatus: 502
 
 Value: 2551
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_REQUEST_ERROR
 Description: The backend failed to execute the `/track/transfer` request internally.
 HttpStatus: 502
 
 Value: 2552
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_CONFLICTING_TRANSFERS
 Description: The amount transferred differs between what was submitted and what the exchange claimed.
 HttpStatus: 409
 
 Value: 2553
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_CONFLICTING_REPORTS
 Description: The exchange gave conflicting information about a coin which has been wire transferred.
 HttpStatus: 409
 
 Value: 2554
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_BAD_WIRE_FEE
 Description: The exchange charged a different wire fee than what it originally advertised, and it is higher.
 HttpStatus: 502
 
 Value: 2555
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_ACCOUNT_NOT_FOUND
 Description: The backend did not find the account to which the transfer was made.
 HttpStatus: 404
 
 Value: 2556
 Name: MERCHANT_PRIVATE_DELETE_TRANSFERS_ALREADY_CONFIRMED
 Description: The backend could not delete the transfer because the exchange already responded to the inquiry and the result was integrated.
 HttpStatus: 409
 
 Value: 2557
 Name: MERCHANT_PRIVATE_POST_TRANSFERS_CONFLICTING_SUBMISSION
 Description: The backend could not persist the wire transfer due to the state of the backend. This usually means that a wire transfer with the same wire transfer subject but a different amount was previously submitted to the backend.
 HttpStatus: 409
 
 Value: 2558
 Name: MERCHANT_EXCHANGE_TRANSFERS_TARGET_ACCOUNT_UNKNOWN
 Description: The target bank account given by the exchange is not (or no longer) known at the merchant instance.
 HttpStatus: 0
 
 Value: 2563
 Name: MERCHANT_EXCHANGE_TRANSFERS_CONFLICTING_TRANSFERS
 Description: The amount transferred differs between what was submitted and what the exchange claimed.
 HttpStatus: 0
 
 
 Value: 2570
 Name: MERCHANT_REPORT_GENERATOR_FAILED
 Description: The report ID provided to the backend is not known to the backend.
 HttpStatus: 501
 
 Value: 2571
 Name: MERCHANT_REPORT_FETCH_FAILED
 Description: Failed to fetch the data for the report from the backend.
 HttpStatus: 502
 
 
 # 2600-2649: instance operations
 
 Value: 2600
 Name: MERCHANT_PRIVATE_POST_INSTANCES_ALREADY_EXISTS
 Description: The merchant backend cannot create an instance under the given identifier as one already exists. Use PATCH to modify the existing entry.
 HttpStatus: 409
 
 Value: 2601
 Name: MERCHANT_PRIVATE_POST_INSTANCES_BAD_AUTH
 Description: The merchant backend cannot create an instance because the authentication configuration field is malformed.
 HttpStatus: 400
 
 Value: 2602
 Name: MERCHANT_PRIVATE_POST_INSTANCE_AUTH_BAD_AUTH
 Description: The merchant backend cannot update an instance's authentication settings because the provided authentication settings are malformed.
 HttpStatus: 400
 
 Value: 2603
 Name: MERCHANT_PRIVATE_POST_INSTANCES_PURGE_REQUIRED
 Description: The merchant backend cannot create an instance under the given identifier, the previous one was deleted but must be purged first.
 HttpStatus: 409
 
 Value: 2604
 Name: MERCHANT_PRIVATE_POST_INSTANCE_AUTH_BAD_OLD_PASSWORD
 Description: The merchant backend cannot update an instance's authentication settings because the required current password was missing or did not match.
 HttpStatus: 401
 
 Value: 2625
 Name: MERCHANT_PRIVATE_PATCH_INSTANCES_PURGE_REQUIRED
 Description: The merchant backend cannot update an instance under the given identifier, the previous one was deleted but must be purged first.
 HttpStatus: 409
 
 Value: 2626
 Name: MERCHANT_PRIVATE_ACCOUNT_DELETE_UNKNOWN_ACCOUNT
 Description: The bank account referenced in the requested operation was not found.
 HttpStatus: 404
 
 Value: 2627
 Name: MERCHANT_PRIVATE_ACCOUNT_EXISTS
 Description: The bank account specified in the request already exists at the merchant.
 HttpStatus: 409
 
 Value: 2628
 Name: MERCHANT_PRIVATE_ACCOUNT_NOT_ELIGIBLE_FOR_EXCHANGE
 Description: The bank account specified is not acceptable for this exchange. The exchange either does not support the wire method or does not support another property of the account. Check the exchange account constraints and specify a different bank account if necessary.
 HttpStatus: 409
 
 
 # 2650-2699: product operations
 
 Value: 2650
 Name: MERCHANT_PRIVATE_POST_PRODUCTS_CONFLICT_PRODUCT_EXISTS
 Description: The product ID exists.
 HttpStatus: 409
 
 Value: 2651
 Name: MERCHANT_PRIVATE_POST_CATEGORIES_CONFLICT_CATEGORY_EXISTS
 Description: A category with the same name exists already.
 HttpStatus: 409
 
 Value: 2660
 Name: MERCHANT_PRIVATE_PATCH_PRODUCTS_TOTAL_LOST_REDUCED
 Description: The update would have reduced the total amount of product lost, which is not allowed.
 HttpStatus: 409
 
 Value: 2661
 Name: MERCHANT_PRIVATE_PATCH_PRODUCTS_TOTAL_LOST_EXCEEDS_STOCKS
 Description: The update would have mean that more stocks were lost than what remains from total inventory after sales, which is not allowed.
 HttpStatus: 400
 
 Value: 2662
 Name: MERCHANT_PRIVATE_PATCH_PRODUCTS_TOTAL_STOCKED_REDUCED
 Description: The update would have reduced the total amount of product in stock, which is not allowed.
 HttpStatus: 409
 
 Value: 2663
 Name: MERCHANT_PRIVATE_PATCH_PRODUCTS_TOTAL_SOLD_REDUCED
 Description: The update would have reduced the total amount of product sold, which is not allowed.
 HttpStatus: 409
 
 Value: 2670
 Name: MERCHANT_PRIVATE_POST_PRODUCTS_LOCK_INSUFFICIENT_STOCKS
 Description: The lock request is for more products than we have left (unlocked) in stock.
 HttpStatus: 410
 
 Value: 2680
 Name: MERCHANT_PRIVATE_DELETE_PRODUCTS_CONFLICTING_LOCK
 Description: The deletion request is for a locked product. The product cannot be deleted until the existing offer expires.
 HttpStatus: 409
 
 Value: 2690
 Name: MERCHANT_PRIVATE_PRODUCT_GROUP_CONFLICTING_NAME
 Description: The proposed name for the product group is already in use. The client should select a different name.
 HttpStatus: 409
 
 Value: 2691
 Name: MERCHANT_PRIVATE_MONEY_POT_CONFLICTING_NAME
 Description: The proposed name for the money pot is already in use. The client should select a different name.
 HttpStatus: 409
 
 Value: 2692
 Name: MERCHANT_PRIVATE_MONEY_POT_CONFLICTING_TOTAL
 Description: The total amount in the money pot is different from the amount required by the request. The client should fetch the current pot total and retry with the latest amount to succeed.
 HttpStatus: 409
 
 # 2700-2749: reserve operations
 
 Value: 2700
 Name: MERCHANT_PRIVATE_POST_RESERVES_UNSUPPORTED_WIRE_METHOD
 Description: The requested wire method is not supported by the exchange.
 HttpStatus: 409
 
 Value: 2701
 Name: MERCHANT_PRIVATE_POST_RESERVES_REWARDS_NOT_ALLOWED
 Description: The requested exchange does not allow rewards.
 HttpStatus: 409
 
 Value: 2710
 Name: MERCHANT_PRIVATE_DELETE_RESERVES_NO_SUCH_RESERVE
 Description: The reserve could not be deleted because it is unknown.
 HttpStatus: 404
 
 # 2750-2799: reward authorization
 
 Value: 2750
 Name: MERCHANT_PRIVATE_POST_REWARD_AUTHORIZE_RESERVE_EXPIRED
 Description: The reserve that was used to fund the rewards has expired.
 HttpStatus: 410
 
 Value: 2751
 Name: MERCHANT_PRIVATE_POST_REWARD_AUTHORIZE_RESERVE_UNKNOWN
 Description: The reserve that was used to fund the rewards was not found in the DB.
 HttpStatus: 503
 
 Value: 2752
 Name: MERCHANT_PRIVATE_POST_REWARD_AUTHORIZE_INSUFFICIENT_FUNDS
 Description: The backend knows the instance that was supposed to support the reward, and it was configured for rewardping. However, the funds remaining are insufficient to cover the reward, and the merchant should top up the reserve.
 HttpStatus: 0
 
 Value: 2753
 Name: MERCHANT_PRIVATE_POST_REWARD_AUTHORIZE_RESERVE_NOT_FOUND
 Description: The backend failed to find a reserve needed to authorize the reward.
 HttpStatus: 503
 
 Value: 2800
 Name: MERCHANT_PRIVATE_GET_ORDERS_ID_AMOUNT_ARITHMETIC_FAILURE
 Description: The merchant backend encountered a failure in computing the deposit total.
 HttpStatus: 200
 
 # 2850-2899: template and OTP device operations
 
 Value: 2850
 Name: MERCHANT_PRIVATE_POST_TEMPLATES_CONFLICT_TEMPLATE_EXISTS
 Description: The template ID already exists.
 HttpStatus: 409
 
 Value: 2851
 Name: MERCHANT_PRIVATE_POST_OTP_DEVICES_CONFLICT_OTP_DEVICE_EXISTS
 Description: The OTP device ID already exists.
 HttpStatus: 409
 
 Value: 2860
 Name: MERCHANT_POST_USING_TEMPLATES_AMOUNT_CONFLICT_TEMPLATES_CONTRACT_AMOUNT
 Description: Amount given in the using template and in the template contract. There is a conflict.
 HttpStatus: 409
 
 Value: 2861
 Name: MERCHANT_POST_USING_TEMPLATES_SUMMARY_CONFLICT_TEMPLATES_CONTRACT_SUBJECT
 Description: Subject given in the using template and in the template contract. There is a conflict.
 HttpStatus: 409
 
 Value: 2862
 Name: MERCHANT_POST_USING_TEMPLATES_NO_AMOUNT
 Description: Amount not given in the using template and in the template contract. There is a conflict.
 HttpStatus: 409
 
 Value: 2863
 Name: MERCHANT_POST_USING_TEMPLATES_NO_SUMMARY
 Description: Subject not given in the using template and in the template contract. There is a conflict.
 HttpStatus: 409
 
 Value: 2864
 Name: MERCHANT_POST_USING_TEMPLATES_WRONG_TYPE
 Description: The selected template has a different type from the one specified in the client request. This may happen if the template was updated since the client last fetched it. The client should refetch the current template and send a request with the correct type.
 HttpStatus: 409
 
 Value: 2865
 Name: MERCHANT_POST_USING_TEMPLATES_WRONG_PRODUCT
 Description: The selected template does not allow one of the specified products to be included in the order. This may happen if the template was updated since the client last fetched it. The client should refetch the current template and send a request with the correct type.
 HttpStatus: 409
 
 Value: 2866
 Name: MERCHANT_POST_USING_TEMPLATES_NO_CURRENCY
 Description: The selected combination of products does not allow the backend to compute a price for the order in any of the supported currencies. This may happen if the template was updated since the last time the client fetched it or if the wallet assembled an unsupported combination of products. The site administrator might want to specify additional prices for products, while the client should re-fetch the current template and send a request with a combination of products for which prices exist in the same currency.
 HttpStatus: 409
 
 
 # 2900-2949: webhook operations
 
 Value: 2900
 Name: MERCHANT_PRIVATE_POST_WEBHOOKS_CONFLICT_WEBHOOK_EXISTS
 Description: The webhook ID elready exists.
 HttpStatus: 409
 
 Value: 2910
 Name: MERCHANT_PRIVATE_POST_PENDING_WEBHOOKS_CONFLICT_PENDING_WEBHOOK_EXISTS
 Description: The webhook serial elready exists.
 HttpStatus: 409
 
 
 # 2950-2999: fountain operations (DD 98)
 
 Value: 2950
 Name: MERCHANT_POST_FOUNTAIN_WITHDRAW_GRANT_UNKNOWN
 Description: A withdrawal entry refers to a token family without a matching grant in the fountain.
 HttpStatus: 409
 
 Value: 2951
 Name: MERCHANT_POST_FOUNTAIN_WITHDRAW_SLOT_OUTSIDE_WINDOW
 Description: The desired token validity time selects an issue key slot outside of the grant's key window.
 HttpStatus: 409
 
 Value: 2952
 Name: MERCHANT_POST_FOUNTAIN_WITHDRAW_LIMIT_EXCEEDED
 Description: The grant's per-period withdrawal limit is exhausted for the requested issue key slot.
 HttpStatus: 429
 
 
 
 
 
 # 3000 - 3999: Reserved for auditor
 # 3000 - 3099: Reserved for AUDITOR_GENERIC
 
 Value: 3001
 Name: AUDITOR_GENERIC_UNAUTHORIZED
 Description: The auditor refused the connection due to a lack of authorization.
 HttpStatus: 401
 
 Value: 3002
 Name: AUDITOR_GENERIC_METHOD_NOT_ALLOWED
 Description: This method is not allowed here.
 HttpStatus: 405
 
 Value: 3100
 Name: AUDITOR_DEPOSIT_CONFIRMATION_SIGNATURE_INVALID
 Description: The signature from the exchange on the deposit confirmation is invalid.
 HttpStatus: 403
 
 Value: 3101
 Name: AUDITOR_EXCHANGE_SIGNING_KEY_REVOKED
 Description: The exchange key used for the signature on the deposit confirmation was revoked.
 HttpStatus: 410
 
 Value: 3102
 Name: AUDITOR_RESOURCE_NOT_FOUND
 Description: The requested resource could not be found.
 HttpStatus: 404
 
 Value: 3103
 Name: AUDITOR_URI_MISSING_PATH_COMPONENT
 Description: The URI is missing a path component.
 HttpStatus: 400
 
 
 # 5000 - 5999: Reserved for bank
 # 5000 - 5099: Reserved for BANK_GENERIC
 
 Value: 5101
 Name: BANK_SAME_ACCOUNT
 Description: Wire transfer attempted with credit and debit party being the same bank account.
 HttpStatus: 400
 
 Value: 5102
 Name: BANK_UNALLOWED_DEBIT
 Description: Wire transfer impossible, due to financial limitation of the party that attempted the payment.
 HttpStatus: 409
 
 Value: 5103
 Name: BANK_NEGATIVE_NUMBER_AMOUNT
 Description: Negative numbers are not allowed (as value and/or fraction) to instantiate an amount object.
 HttpStatus: 400
 
 Value: 5104
 Name: BANK_NUMBER_TOO_BIG
 Description: A too big number was used (as value and/or fraction) to instantiate an amount object.
 HttpStatus: 400
 
 Value: 5106
 Name: BANK_UNKNOWN_ACCOUNT
 Description: The bank account referenced in the requested operation was not found.
 HttpStatus: 404
 
 Value: 5107
 Name: BANK_TRANSACTION_NOT_FOUND
 Description: The transaction referenced in the requested operation (typically a reject operation), was not found.
 HttpStatus: 404
 
 Value: 5108
 Name: BANK_BAD_FORMAT_AMOUNT
 Description: Bank received a malformed amount string.
 HttpStatus: 400
 
 Value: 5109
 Name: BANK_REJECT_NO_RIGHTS
 Description: The client does not own the account credited by the transaction which is to be rejected, so it has no rights do reject it.
 HttpStatus: 403
 
 Value: 5110
 Name: BANK_UNMANAGED_EXCEPTION
 Description: This error code is returned when no known exception types captured the exception.
 HttpStatus: 500
 
 Value: 5111
 Name: BANK_SOFT_EXCEPTION
 Description: This error code is used for all those exceptions that do not really need a specific error code to return to the client. Used for example when a client is trying to register with a unavailable username.
 HttpStatus: 500
 
 Value: 5112
 Name: BANK_TRANSFER_REQUEST_UID_REUSED
 Description: The request UID for a request to transfer funds has already been used, but with different details for the transfer.
 HttpStatus: 409
 
 Value: 5113
 Name: BANK_WITHDRAWAL_OPERATION_RESERVE_SELECTION_CONFLICT
 Description: The withdrawal operation already has a reserve selected.  The current request conflicts with the existing selection.
 HttpStatus: 409
 
 Value: 5114
 Name: BANK_DUPLICATE_RESERVE_PUB_SUBJECT
 Description: The wire transfer subject duplicates an existing reserve public key. But wire transfer subjects must be unique.
 HttpStatus: 409
 
 Value: 5115
 Name: BANK_ANCIENT_TRANSACTION_GONE
 Description: The client requested a transaction that is so far in the past, that it has been forgotten by the bank.
 HttpStatus: 410
 
 Value: 5116
 Name: BANK_ABORT_CONFIRM_CONFLICT
 Description: The client attempted to abort a transaction that was already confirmed.
 HttpStatus: 409
 
 Value: 5117
 Name: BANK_CONFIRM_ABORT_CONFLICT
 Description: The client attempted to confirm a transaction that was already aborted.
 HttpStatus: 409
 
 Value: 5118
 Name: BANK_REGISTER_CONFLICT
 Description: The client attempted to register an account with the same name.
 HttpStatus: 409
 
 Value: 5119
 Name: BANK_POST_WITHDRAWAL_OPERATION_REQUIRED
 Description: The client attempted to confirm a withdrawal operation before the wallet posted the required details.
 HttpStatus: 400
 
 Value: 5120
 Name: BANK_RESERVED_USERNAME_CONFLICT
 Description: The client tried to register a new account under a reserved username (like 'admin' for example).
 HttpStatus: 409
 
 Value: 5121
 Name: BANK_REGISTER_USERNAME_REUSE
 Description: The client tried to register a new account with an username already in use.
 HttpStatus: 409
 
 Value: 5122
 Name: BANK_REGISTER_PAYTO_URI_REUSE
 Description: The client tried to register a new account with a payto:// URI already in use.
 HttpStatus: 409
 
 Value: 5123
 Name: BANK_ACCOUNT_BALANCE_NOT_ZERO
 Description: The client tried to delete an account with a non null balance.
 HttpStatus: 409
 
 Value: 5124
 Name: BANK_UNKNOWN_CREDITOR
 Description: The client tried to create a transaction or an operation that credit an unknown account.
 HttpStatus: 409
 
 Value: 5125
 Name: BANK_UNKNOWN_DEBTOR
 Description: The client tried to create a transaction or an operation that debit an unknown account.
 HttpStatus: 409
 
 Value: 5126
 Name: BANK_ACCOUNT_IS_EXCHANGE
 Description: The client tried to perform an action prohibited for exchange accounts.
 HttpStatus: 409
 
 Value: 5127
 Name: BANK_ACCOUNT_IS_NOT_EXCHANGE
 Description: The client tried to perform an action reserved for exchange accounts.
 HttpStatus: 409
 
 Value: 5128
 Name: BANK_BAD_CONVERSION
 Description: Received currency conversion is wrong.
 HttpStatus: 409
 
 Value: 5129
 Name: BANK_MISSING_TAN_INFO
 Description: The account referenced in this operation is missing tan info for the chosen channel.
 HttpStatus: 409
 
 Value: 5130
 Name: BANK_CONFIRM_INCOMPLETE
 Description: The client attempted to confirm a transaction with incomplete info.
 HttpStatus: 409
 
 Value: 5131
 Name: BANK_TAN_RATE_LIMITED
 Description: The request rate is too high. The server is refusing requests to guard against brute-force attacks.
 HttpStatus: 429
 
 Value: 5132
 Name: BANK_TAN_CHANNEL_NOT_SUPPORTED
 Description: This TAN channel is not supported.
 HttpStatus: 501
 
 Value: 5133
 Name: BANK_TAN_CHANNEL_SCRIPT_FAILED
 Description: Failed to send TAN using the helper script. Either script is not found, or script timeout, or script terminated with a non-successful result.
 HttpStatus: 500
 
 Value: 5134
 Name: BANK_TAN_CHALLENGE_FAILED
 Description: The client's response to the challenge was invalid.
 HttpStatus: 403
 
 Value: 5135
 Name: BANK_NON_ADMIN_PATCH_LEGAL_NAME
 Description: A non-admin user has tried to change their legal name.
 HttpStatus: 409
 
 Value: 5136
 Name: BANK_NON_ADMIN_PATCH_DEBT_LIMIT
 Description: A non-admin user has tried to change their debt limit.
 HttpStatus: 409
 
 Value: 5137
 Name: BANK_NON_ADMIN_PATCH_MISSING_OLD_PASSWORD
 Description: A non-admin user tried to change their password without providing the current password.
 HttpStatus: 409
 
 Value: 5138
 Name: BANK_PATCH_BAD_OLD_PASSWORD
 Description: Provided old password does not match current password.
 HttpStatus: 409
 
 Value: 5139
 Name: BANK_PATCH_ADMIN_EXCHANGE
 Description: An admin user has tried to become an exchange.
 HttpStatus: 409
 
 Value: 5140
 Name: BANK_NON_ADMIN_PATCH_CASHOUT
 Description: A non-admin user has tried to change their cashout account.
 HttpStatus: 409
 
 Value: 5141
 Name: BANK_NON_ADMIN_PATCH_CONTACT
 Description: A non-admin user has tried to change their contact info.
 HttpStatus: 409
 
 Value: 5142
 Name: BANK_ADMIN_CREDITOR
 Description: The client tried to create a transaction that credits the administrator's account.
 HttpStatus: 409
 
 Value: 5143
 Name: BANK_CHALLENGE_NOT_FOUND
 Description: The referenced challenge was not found.
 HttpStatus: 404
 
 Value: 5144
 Name: BANK_TAN_CHALLENGE_EXPIRED
 Description: The referenced challenge has expired.
 HttpStatus: 409
 
 Value: 5145
 Name: BANK_NON_ADMIN_SET_TAN_CHANNEL
 Description: A non-admin user has tried to create an account with 2fa.
 HttpStatus: 409
 
 Value: 5146
 Name: BANK_NON_ADMIN_SET_MIN_CASHOUT
 Description: A non-admin user has tried to set their minimum cashout amount.
 HttpStatus: 409
 
 Value: 5147
 Name: BANK_CONVERSION_AMOUNT_TO_SMALL
 Description: The amount of the currency conversion is less than the minimum allowed.
 HttpStatus: 409
 
 Value: 5148
 Name: BANK_AMOUNT_DIFFERS
 Description: Specified amount will not work for this withdrawal.
 HttpStatus: 409
 
 Value: 5149
 Name: BANK_AMOUNT_REQUIRED
 Description: The backend requires an amount to be specified.
 HttpStatus: 409
 
 Value: 5150
 Name: BANK_PASSWORD_TOO_SHORT
 Description: Provided password is too short.
 HttpStatus: 409
 
 Value: 5151
 Name: BANK_PASSWORD_TOO_LONG
 Description: Provided password is too long.
 HttpStatus: 409
 
 Value: 5152
 Name: BANK_ACCOUNT_LOCKED
 Description: The bank account is locked, and the user cannot authenticate with their password.
 HttpStatus: 403
 
 Value: 5153
 Name: BANK_UPDATE_ABORT_CONFLICT
 Description: The client attempted to update the details of a transaction that was already aborted.
 HttpStatus: 409
 
 Value: 5154
 Name: BANK_TRANSFER_WTID_REUSED
 Description: The wtid for a request to transfer funds has already been used, but with a different request unpaid.
 HttpStatus: 409
 
 Value: 5155
 Name: BANK_NON_ADMIN_SET_CONVERSION_RATE_CLASS
 Description: A non-admin user tried to set their conversion rate class.
 HttpStatus: 409
 
 Value: 5156
 Name: BANK_CONVERSION_RATE_CLASS_UNKNOWN
 Description: The referenced conversion rate class was not found.
 HttpStatus: 409
 
 Value: 5157
 Name: BANK_NAME_REUSE
 Description: The client tried to use an already taken name.
 HttpStatus: 409
 
 Value: 5158
 Name: BANK_UNSUPPORTED_SUBJECT_FORMAT
 Description: This subject format is not supported.
 HttpStatus: 409
 
 Value: 5159
 Name: BANK_DERIVATION_REUSE
 Description: The derived subject is already used.
 HttpStatus: 409
 
 Value: 5160
 Name: BANK_BAD_SIGNATURE
 Description: The provided signature is invalid.
 HttpStatus: 403
 
 Value: 5161
 Name: BANK_OLD_TIMESTAMP
 Description: The provided timestamp is too old.
 HttpStatus: 409
 
 Value: 5162
 Name: BANK_TRANSFER_MAPPING_REUSED
 Description: The `authorization_pub` for a request to transfer funds has already been used for another non-recurring transfer.
 HttpStatus: 409
 
 Value: 5163
 Name: BANK_TRANSFER_MAPPING_UNKNOWN
 Description: The authorization_pub for a request to transfer funds is not currently registered.
 HttpStatus: 409
 
 # 6000 - 6999: Reserved for sync
 # 6000 - 6099: Reserved for SYNC_GENERIC
 
 Value: 6100
 Name: SYNC_ACCOUNT_UNKNOWN
 Description: The sync service failed to find the account in its database.
 HttpStatus: 404
 
 Value: 6101
 Name: SYNC_BAD_IF_NONE_MATCH
 Description: The SHA-512 hash provided in the If-None-Match header is malformed.
 HttpStatus: 400
 
 Value: 6102
 Name: SYNC_BAD_IF_MATCH
 Description: The SHA-512 hash provided in the If-Match header is malformed or missing.
 HttpStatus: 400
 
 Value: 6103
 Name: SYNC_BAD_SYNC_SIGNATURE
 Description: The signature provided in the "Sync-Signature" header is malformed or missing.
 HttpStatus: 400
 
 Value: 6104
 Name: SYNC_INVALID_SIGNATURE
 Description: The signature provided in the "Sync-Signature" header does not match the account, old or new Etags.
 HttpStatus: 403
 
 Value: 6105
 Name: SYNC_MALFORMED_CONTENT_LENGTH
 Description: The "Content-length" field for the upload is not a number.
 HttpStatus: 400
 
 Value: 6106
 Name: SYNC_EXCESSIVE_CONTENT_LENGTH
 Description: The "Content-length" field for the upload is too big based on the server's terms of service.
 HttpStatus: 413
 
 Value: 6107
 Name: SYNC_OUT_OF_MEMORY_ON_CONTENT_LENGTH
 Description: The server is out of memory to handle the upload. Trying again later may succeed.
 HttpStatus: 413
 
 Value: 6108
 Name: SYNC_INVALID_UPLOAD
 Description: The uploaded data does not match the Etag.
 HttpStatus: 400
 
 Value: 6109
 Name: SYNC_PAYMENT_GENERIC_TIMEOUT
 Description: HTTP server experienced a timeout while awaiting promised payment.
 HttpStatus: 408
 
 Value: 6110
 Name: SYNC_PAYMENT_CREATE_BACKEND_ERROR
 Description: The sync service could not set up the payment request with its own backend.
 HttpStatus: 500
 
 Value: 6111
 Name: SYNC_PREVIOUS_BACKUP_UNKNOWN
 Description: The sync service failed to find the backup to be updated in its database.
 HttpStatus: 404
 
 Value: 6112
 Name: SYNC_MISSING_CONTENT_LENGTH
 Description: The "Content-length" field for the upload is missing.
 HttpStatus: 400
 
 Value: 6113
 Name: SYNC_GENERIC_BACKEND_ERROR
 Description: Sync had problems communicating with its payment backend.
 HttpStatus: 502
 
 Value: 6114
 Name: SYNC_GENERIC_BACKEND_TIMEOUT
 Description: Sync experienced a timeout communicating with its payment backend.
 HttpStatus: 504
 
 Value: 6115
 Name: SYNC_CONFLICTING_WRITE
 Description: The provided new content is based on an outdated backup: the previous write was overwritten in the meantime.
 HttpStatus: 409
 
 Value: 6116
 Name: SYNC_INCONSISTENT_BACKUP
 Description: The backup does not form a consistent linked list (e.g. the previous block does not match the given hash).
 HttpStatus: 409
 
 
 
 # 7000 - 7999: Reserved for wallet
 
 Value: 7000
 Name: WALLET_EXCHANGE_PROTOCOL_VERSION_INCOMPATIBLE
 Description: The wallet does not implement a version of the exchange protocol that is compatible with the protocol version of the exchange.
 HttpStatus: 501
 
 Value: 7001
 Name: WALLET_UNEXPECTED_EXCEPTION
 Description: The wallet encountered an unexpected exception.  This is likely a bug in the wallet implementation.
 HttpStatus: 500
 
 Value: 7002
 Name: WALLET_RECEIVED_MALFORMED_RESPONSE
 Description: The wallet received a response from a server, but the response cannot be parsed.
 HttpStatus: 0
 
 Value: 7003
 Name: WALLET_NETWORK_ERROR
 Description: The wallet tried to make a network request, but it received no response.
 HttpStatus: 0
 
 Value: 7004
 Name: WALLET_HTTP_REQUEST_THROTTLED
 Description: The wallet tried to make a network request, but it was throttled.
 HttpStatus: 0
 
 Value: 7005
 Name: WALLET_UNEXPECTED_REQUEST_ERROR
 Description: The wallet made a request to a service, but received an error response it does not know how to handle.
 HttpStatus: 0
 
 Value: 7006
 Name: WALLET_EXCHANGE_DENOMINATIONS_INSUFFICIENT
 Description: The denominations offered by the exchange are insufficient.  Likely the exchange is badly configured or not maintained.
 HttpStatus: 0
 
 Value: 7007
 Name: WALLET_CORE_API_OPERATION_UNKNOWN
 Description: The wallet does not support the operation requested by a client.
 HttpStatus: 0
 
 Value: 7008
 Name: WALLET_INVALID_TALER_PAY_URI
 Description: The given taler://pay URI is invalid.
 HttpStatus: 0
 
 Value: 7009
 Name: WALLET_EXCHANGE_COIN_SIGNATURE_INVALID
 Description: The signature on a coin by the exchange's denomination key is invalid after unblinding it.
 HttpStatus: 0
 
 Value: 7011
 Name: WALLET_CORE_NOT_AVAILABLE
 Description: The wallet core service is not available.
 HttpStatus: 0
 
 Value: 7012
 Name: WALLET_WITHDRAWAL_OPERATION_ABORTED_BY_BANK
 Description: The bank aborted a withdrawal operation, so the withdrawal cannot complete.
 HttpStatus: 0
 
 Value: 7013
 Name: WALLET_HTTP_REQUEST_GENERIC_TIMEOUT
 Description: An HTTP request made by the wallet timed out.
 HttpStatus: 0
 
 Value: 7014
 Name: WALLET_ORDER_ALREADY_CLAIMED
 Description: The order has already been claimed by another wallet.
 HttpStatus: 0
 
 Value: 7015
 Name: WALLET_WITHDRAWAL_GROUP_INCOMPLETE
 Description: A group of withdrawal operations (typically for the same reserve at the same exchange) has errors and will be tried again later.
 HttpStatus: 0
 
 Value: 7016
 Name: WALLET_REWARD_COIN_SIGNATURE_INVALID
 Description: The signature on a coin by the exchange's denomination key (obtained through the merchant via a reward) is invalid after unblinding it.
 HttpStatus: 0
 
 Value: 7017
 Name: WALLET_BANK_INTEGRATION_PROTOCOL_VERSION_INCOMPATIBLE
 Description: The wallet does not implement a version of the bank integration API that is compatible with the version offered by the bank.
 HttpStatus: 0
 
 Value: 7018
 Name: WALLET_CONTRACT_TERMS_BASE_URL_MISMATCH
 Description: The wallet processed a taler://pay URI, but the merchant base URL in the downloaded contract terms does not match the merchant base URL derived from the URI.
 HttpStatus: 0
 
 Value: 7019
 Name: WALLET_CONTRACT_TERMS_SIGNATURE_INVALID
 Description: The merchant's signature on the contract terms is invalid.
 HttpStatus: 0
 
 Value: 7020
 Name: WALLET_CONTRACT_TERMS_MALFORMED
 Description: The contract terms given by the merchant are malformed.
 HttpStatus: 0
 
 Value: 7021
 Name: WALLET_PENDING_OPERATION_FAILED
 Description: A pending operation failed, so the request cannot be completed.
 HttpStatus: 0
 
 Value: 7022
 Name: WALLET_PAY_MERCHANT_SERVER_ERROR
 Description: A payment was attempted, but the merchant had an internal server error (5xx).
 HttpStatus: 0
 
 Value: 7023
 Name: WALLET_CRYPTO_WORKER_ERROR
 Description: The crypto worker failed.
 HttpStatus: 0
 
 Value: 7024
 Name: WALLET_CRYPTO_WORKER_BAD_REQUEST
 Description: The crypto worker received a bad request.
 HttpStatus: 0
 
 Value: 7025
 Name: WALLET_WITHDRAWAL_KYC_REQUIRED
 Description: A KYC step is required before withdrawal can proceed.
 HttpStatus: 0
 
 Value: 7026
 Name: WALLET_DEPOSIT_GROUP_INSUFFICIENT_BALANCE
 Description: The wallet does not have sufficient balance to create a deposit group.
 HttpStatus: 0
 
 Value: 7027
 Name: WALLET_PEER_PUSH_PAYMENT_INSUFFICIENT_BALANCE
 Description: The wallet does not have sufficient balance to create a peer push payment.
 HttpStatus: 0
 
 Value: 7028
 Name: WALLET_PEER_PULL_PAYMENT_INSUFFICIENT_BALANCE
 Description: The wallet does not have sufficient balance to pay for an invoice.
 HttpStatus: 0
 
 Value: 7029
 Name: WALLET_REFRESH_GROUP_INCOMPLETE
 Description: A group of refresh operations has errors and will be tried again later.
 HttpStatus: 0
 
 Value: 7030
 Name: WALLET_EXCHANGE_BASE_URL_MISMATCH
 Description: The exchange's self-reported base URL does not match the one that the wallet is using.
 HttpStatus: 0
 
 Value: 7031
 Name: WALLET_ORDER_ALREADY_PAID
 Description: The order has already been paid by another wallet.
 HttpStatus: 0
 
 Value: 7032
 Name: WALLET_EXCHANGE_UNAVAILABLE
 Description: An exchange that is required for some request is currently not available.
 HttpStatus: 0
 
 Value: 7033
 Name: WALLET_EXCHANGE_ENTRY_USED
 Description: An exchange entry is still used by the exchange, so it cannot be deleted without purging.
 HttpStatus: 0
 
 Value: 7034
 Name: WALLET_DB_UNAVAILABLE
 Description: The wallet database is unavailable and the wallet thus is not operational.
 HttpStatus: 0
 
 Value: 7035
 Name: WALLET_TALER_URI_MALFORMED
 Description: A `taler://` URI is malformed and cannot be parsed.
 HttpStatus: 0
 
 Value: 7036
 Name: WALLET_CORE_REQUEST_CANCELLED
 Description: A wallet-core request was cancelled and therefore cannot provide a response.
 HttpStatus: 0
 
 Value: 7037
 Name: WALLET_EXCHANGE_TOS_NOT_ACCEPTED
 Description: A wallet-core request failed because the user needs to first accept the exchange's terms of service.
 HttpStatus: 0
 
 Value: 7038
 Name: WALLET_EXCHANGE_ENTRY_UPDATE_CONFLICT
 Description: An exchange entry could not be updated, as the exchange's new details conflict with the new details.
 HttpStatus: 0
 
 Value: 7039
 Name: WALLET_EXCHANGE_ENTRY_OUTDATED
 Description: The wallet's information about the exchange is outdated.
 HttpStatus: 0
 
 Value: 7040
 Name: WALLET_PAY_MERCHANT_KYC_MISSING
 Description: The merchant needs to do KYC first, the payment could not be completed.
 HttpStatus: 0
 
 Value: 7041
 Name: WALLET_PEER_PULL_DEBIT_PURSE_GONE
 Description: A peer-pull-debit transaction was aborted because the exchange reported the purse as gone.
 HttpStatus: 0
 
 Value: 7042
 Name: WALLET_TRANSACTION_ABORTED_BY_USER
 Description: A transaction was aborted on explicit request by the user.
 HttpStatus: 0
 
 Value: 7043
 Name: WALLET_TRANSACTION_ABANDONED_BY_USER
 Description: A transaction was abandoned on explicit request by the user.
 HttpStatus: 0
 
 Value: 7044
 Name: WALLET_PAY_MERCHANT_ORDER_GONE
 Description: A payment was attempted, but the merchant claims the order is gone (likely expired).
 HttpStatus: 0
 
 Value: 7045
 Name: WALLET_EXCHANGE_ENTRY_NOT_FOUND
 Description: The wallet does not have an entry for the requested exchange.
 HttpStatus: 0
 
 Value: 7046
 Name: WALLET_REQUEST_TRANSACTION_STATE_UNSUPPORTED
 Description: The wallet is not able to process the request due to the transaction's state.
 HttpStatus: 0
 
 Value: 7047
 Name: WALLET_TRANSACTION_PROTOCOL_VIOLATION
 Description: A transaction could not be processed due to an unrecoverable protocol violation.
 HttpStatus: 0
 
 Value: 7048
 Name: WALLET_CORE_API_BAD_REQUEST
 Description: A parameter in the request is malformed or missing.
 HttpStatus: 0
 
 Value: 7049
 Name: WALLET_MERCHANT_ORDER_NOT_FOUND
 Description: The order could not be found. Maybe the merchant deleted it.
 HttpStatus: 0
 
 Value: 7050
 Name: WALLET_PAY_MERCHANT_INSUFFICIENT_BALANCE
 Description: The wallet's balance for paying a merchant is insufficient.
 HttpStatus: 0
 
 Value: 7051
 Name: WALLET_PURCHASE_NOT_FOUND
 Description: The wallet does not have a purchase for the requested order.
 HttpStatus: 0
 
 Value: 7052
 Name: WALLET_TRANSACTION_NOT_FOUND
 Description: The wallet does not have a transaction with the requested transaction identifier.
 HttpStatus: 0
 
 Value: 7053
 Name: WALLET_TRANSACTION_ACTION_UNSUPPORTED
 Description: The requested action is not supported for this type of transaction.
 HttpStatus: 0
 
 Value: 7054
 Name: WALLET_KYC_LIMIT_EXCEEDED
 Description: The operation would exceed a limit imposed by the exchange that the user cannot raise by completing a KYC process.
 HttpStatus: 0
 
 Value: 7055
 Name: WALLET_NO_SUITABLE_EXCHANGE
 Description: The wallet does not know an exchange that can be used for this operation. Check that an exchange for the requested currency has been added to the wallet.
 HttpStatus: 0
 
 Value: 7056
 Name: WALLET_BANK_ACCOUNT_NOT_FOUND
 Description: The wallet does not have a known bank account with the requested identifier.
 HttpStatus: 0
 
 Value: 7057
 Name: WALLET_PEER_CONTRACT_NOT_FOUND
 Description: The exchange does not know the contract of this peer-to-peer payment. It may have expired.
 HttpStatus: 0
 
 Value: 7058
 Name: WALLET_PEER_PUSH_CREDIT_PURSE_GONE
 Description: The purse of this peer-to-peer push payment is gone. The sender likely aborted the payment.
 HttpStatus: 0
 
 Value: 7059
 Name: WALLET_PEER_PULL_DEBIT_ALREADY_PAID
 Description: This invoice has already been paid, possibly by another wallet.
 HttpStatus: 0
 
 Value: 7060
 Name: WALLET_TOKENS_IN_USE
 Description: The tokens can not be deleted, as at least one of them is currently being used in a transaction.
 HttpStatus: 0
 
 Value: 7061
 Name: WALLET_DB_BACKEND_UNSUPPORTED
 Description: The operation is not supported by the database backend that the wallet is currently running on.
 HttpStatus: 0
 
 Value: 7062
 Name: WALLET_MAILBOX_UNAVAILABLE
 Description: The wallet could not use the mailbox service.
 HttpStatus: 0
 
 Value: 7063
 Name: WALLET_ALIAS_REGISTRATION_FAILED
 Description: The wallet could not register an alias with the directory service.
 HttpStatus: 0
 
 Value: 7064
 Name: WALLET_CONTRACT_TERMS_UNSUPPORTED
 Description: The contract terms use a feature that this version of the wallet does not support. Updating the wallet may help.
 HttpStatus: 0
 
 Value: 7065
 Name: WALLET_EXCHANGE_SIGNATURE_INVALID
 Description: The exchange served data that is not correctly signed by its master key. The wallet refuses to use this exchange.
 HttpStatus: 0
 
 Value: 7066
 Name: WALLET_EXCHANGE_KEYS_NOT_ACCEPTED
 Description: The exchange presents a master public key or currency that the user has not accepted yet. The operation was refused.
 HttpStatus: 0
 
 Value: 7067
 Name: WALLET_EXCHANGE_NO_KEY_CHANGE_PENDING
 Description: The wallet was asked to accept or reject a change of the exchange's keys, but the exchange does not present a new key set.
 HttpStatus: 0
 
 Value: 7068
 Name: WALLET_EXCHANGE_KEY_CHANGE_MISMATCH
 Description: The key set that was confirmed is not the one that the exchange currently presents.
 HttpStatus: 0
 
 Value: 7069
 Name: WALLET_PEER_PUSH_PAYMENT_QUOTE_CHANGED
 Description: The values of a reviewed peer push payment changed before confirmation. The caller must prepare and show the payment again.
 HttpStatus: 0
 
 # 8000 - 8499: Reserved for Anastasis
 
 Value: 8000
 Name: ANASTASIS_GENERIC_BACKEND_TIMEOUT
 Description: The service encountered a timeout with its payment backend.
 HttpStatus: 504
 
 Value: 8001
 Name: ANASTASIS_GENERIC_INVALID_PAYMENT_REQUEST
 Description: The backend requested payment, but the request is malformed.
 HttpStatus: 0
 
 Value: 8002
 Name: ANASTASIS_GENERIC_BACKEND_ERROR
 Description: The backend received an unexpected response from the payment processor.
 HttpStatus: 502
 
 Value: 8003
 Name: ANASTASIS_GENERIC_MISSING_CONTENT_LENGTH
 Description: The "Content-length" field for the upload is missing.
 HttpStatus: 400
 
 Value: 8004
 Name: ANASTASIS_GENERIC_MALFORMED_CONTENT_LENGTH
 Description: The "Content-length" field for the upload is malformed.
 HttpStatus: 400
 
 Value: 8005
 Name: ANASTASIS_GENERIC_ORDER_CREATE_BACKEND_ERROR
 Description: The backend failed to setup an order with the payment processor.
 HttpStatus: 502
 
 Value: 8006
 Name: ANASTASIS_GENERIC_PAYMENT_CHECK_UNAUTHORIZED
 Description: The backend was not authorized to check for payment with the payment processor.
 HttpStatus: 500
 
 Value: 8007
 Name: ANASTASIS_GENERIC_PAYMENT_CHECK_START_FAILED
 Description: The backend could not check payment status with the payment processor.
 HttpStatus: 500
 
 Value: 8008
 Name: ANASTASIS_GENERIC_PROVIDER_UNREACHABLE
 Description: The Anastasis provider could not be reached.
 HttpStatus: 0
 
 Value: 8009
 Name: ANASTASIS_PAYMENT_GENERIC_TIMEOUT
 Description: HTTP server experienced a timeout while awaiting promised payment.
 HttpStatus: 408
 
 
 Value: 8108
 Name: ANASTASIS_TRUTH_UNKNOWN
 Description: The key share is unknown to the provider.
 HttpStatus: 404
 
 Value: 8109
 Name: ANASTASIS_TRUTH_AUTHORIZATION_METHOD_NO_LONGER_SUPPORTED
 Description: The authorization method used for the key share is no longer supported by the provider.
 HttpStatus: 500
 
 Value: 8110
 Name: ANASTASIS_TRUTH_CHALLENGE_RESPONSE_REQUIRED
 Description: The client needs to respond to the challenge.
 HttpStatus: 403
 
 Value: 8111
 Name: ANASTASIS_TRUTH_CHALLENGE_FAILED
 Description: The client's response to the challenge was invalid.
 HttpStatus: 403
 
 Value: 8112
 Name: ANASTASIS_TRUTH_CHALLENGE_UNKNOWN
 Description: The backend is not aware of having issued the provided challenge code. Either this is the wrong code, or it has expired.
 HttpStatus: 404
 
 Value: 8114
 Name: ANASTASIS_TRUTH_AUTHORIZATION_START_FAILED
 Description: The backend failed to initiate the authorization process.
 HttpStatus: 500
 
 Value: 8115
 Name: ANASTASIS_TRUTH_KEY_SHARE_GONE
 Description: The authorization succeeded, but the key share is no longer available.
 HttpStatus: 404
 
 Value: 8116
 Name: ANASTASIS_TRUTH_ORDER_DISAPPEARED
 Description: The backend no longer knows about the order that the client was asked to pay for.
 HttpStatus: 502
 
 Value: 8117
 Name: ANASTASIS_TRUTH_BACKEND_EXCHANGE_BAD
 Description: The backend itself reported a bad exchange interaction.
 HttpStatus: 502
 
 Value: 8118
 Name: ANASTASIS_TRUTH_UNEXPECTED_PAYMENT_STATUS
 Description: The backend reported an unexpected payment status.
 HttpStatus: 500
 
 Value: 8119
 Name: ANASTASIS_TRUTH_PAYMENT_CREATE_BACKEND_ERROR
 Description: The backend failed to setup the order for payment.
 HttpStatus: 502
 
 Value: 8120
 Name: ANASTASIS_TRUTH_DECRYPTION_FAILED
 Description: The decryption of the key share failed with the provided key.
 HttpStatus: 400
 
 Value: 8121
 Name: ANASTASIS_TRUTH_RATE_LIMITED
 Description: The request rate is too high. The server is refusing requests to guard against brute-force attacks.
 HttpStatus: 429
 
 Value: 8123
 Name: ANASTASIS_TRUTH_CHALLENGE_WRONG_METHOD
 Description: A request to issue a challenge is not valid for this authentication method.
 HttpStatus: 400
 
 Value: 8150
 Name: ANASTASIS_TRUTH_UPLOAD_UUID_EXISTS
 Description: The backend failed to store the key share because the UUID is already in use.
 HttpStatus: 409
 
 Value: 8151
 Name: ANASTASIS_TRUTH_UPLOAD_METHOD_NOT_SUPPORTED
 Description: The backend failed to store the key share because the authorization method is not supported.
 HttpStatus: 400
 
 
 
 Value: 8200
 Name: ANASTASIS_SMS_PHONE_INVALID
 Description: The provided phone number is not an acceptable number.
 HttpStatus: 409
 
 Value: 8201
 Name: ANASTASIS_SMS_HELPER_EXEC_FAILED
 Description: Failed to run the SMS transmission helper process.
 HttpStatus: 500
 
 Value: 8202
 Name: ANASTASIS_SMS_HELPER_COMMAND_FAILED
 Description: Provider failed to send SMS. Helper terminated with a non-successful result.
 HttpStatus: 500
 
 
 Value: 8210
 Name: ANASTASIS_EMAIL_INVALID
 Description: The provided email address is not an acceptable address.
 HttpStatus: 409
 
 Value: 8211
 Name: ANASTASIS_EMAIL_HELPER_EXEC_FAILED
 Description: Failed to run the email transmission helper process.
 HttpStatus: 500
 
 Value: 8212
 Name: ANASTASIS_EMAIL_HELPER_COMMAND_FAILED
 Description: The provider failed to send email. The helper terminated with a non-successful result.
 HttpStatus: 500
 
 
 Value: 8220
 Name: ANASTASIS_POST_INVALID
 Description: The provided postal address is not an acceptable address.
 HttpStatus: 409
 
 Value: 8221
 Name: ANASTASIS_POST_HELPER_EXEC_FAILED
 Description: Failed to run the mail transmission helper process.
 HttpStatus: 500
 
 Value: 8222
 Name: ANASTASIS_POST_HELPER_COMMAND_FAILED
 Description: Provider failed to send mail. Helper terminated with a non-successful result.
 HttpStatus: 500
 
 
 Value: 8230
 Name: ANASTASIS_IBAN_INVALID
 Description: The provided IBAN address is not an acceptable IBAN.
 HttpStatus: 409
 
 Value: 8231
 Name: ANASTASIS_IBAN_MISSING_TRANSFER
 Description: The provider has not yet received the IBAN wire transfer authorizing the disclosure of the key share.
 HttpStatus: 403
 
 
 Value: 8240
 Name: ANASTASIS_TOTP_KEY_MISSING
 Description: The backend did not find a TOTP key in the data provided.
 HttpStatus: 409
 
 Value: 8241
 Name: ANASTASIS_TOTP_KEY_INVALID
 Description: The key provided does not satisfy the format restrictions for an Anastasis TOTP key.
 HttpStatus: 409
 
 Value: 8250
 Name: ANASTASIS_ADDRESS_UNREACHABLE
 Description: The address is valid but the recipient could not be reached: the handset is switched off or out of coverage, or the message expired before delivery. Retrying later may succeed. Used by all authorization methods that transmit a challenge via an external helper.
 HttpStatus: 503
 
 Value: 8251
 Name: ANASTASIS_HELPER_MISCONFIGURED
 Description: The transmission helper is misconfigured: a required credential is absent, the configured credentials were refused by the provider, or the provider account has insufficient balance. The provider operator should check the logs and the service configuration. Used by all authorization methods that transmit a challenge via an external helper.
 HttpStatus: 500
 
 
 Value: 8301
 Name: ANASTASIS_POLICY_BAD_IF_NONE_MATCH
 Description: The given if-none-match header is malformed.
 HttpStatus: 400
 
 Value: 8304
 Name: ANASTASIS_POLICY_OUT_OF_MEMORY_ON_CONTENT_LENGTH
 Description: The server is out of memory to handle the upload. Trying again later may succeed.
 HttpStatus: 413
 
 Value: 8305
 Name: ANASTASIS_POLICY_BAD_SIGNATURE
 Description: The signature provided in the "Anastasis-Policy-Signature" header is malformed or missing.
 HttpStatus: 400
 
 Value: 8306
 Name: ANASTASIS_POLICY_BAD_IF_MATCH
 Description: The given if-match header is malformed.
 HttpStatus: 400
 
 Value: 8307
 Name: ANASTASIS_POLICY_INVALID_UPLOAD
 Description: The uploaded data does not match the Etag.
 HttpStatus: 400
 
 Value: 8350
 Name: ANASTASIS_POLICY_NOT_FOUND
 Description: The provider is unaware of the requested policy.
 HttpStatus: 404
 
 
 
 Value: 8400
 Name: ANASTASIS_REDUCER_ACTION_INVALID
 Description: The given action is invalid for the current state of the reducer.
 HttpStatus: 0
 
 Value: 8401
 Name: ANASTASIS_REDUCER_STATE_INVALID
 Description: The given state of the reducer is invalid.
 HttpStatus: 0
 
 Value: 8402
 Name: ANASTASIS_REDUCER_INPUT_INVALID
 Description: The given input to the reducer is invalid.
 HttpStatus: 0
 
 Value: 8403
 Name: ANASTASIS_REDUCER_AUTHENTICATION_METHOD_NOT_SUPPORTED
 Description: The selected authentication method does not work for the Anastasis provider.
 HttpStatus: 0
 
 Value: 8404
 Name: ANASTASIS_REDUCER_INPUT_INVALID_FOR_STATE
 Description: The given input and action do not work for the current state.
 HttpStatus: 0
 
 Value: 8405
 Name: ANASTASIS_REDUCER_BACKEND_FAILURE
 Description: The service experienced an unexpected failure while interacting with the backend.
 HttpStatus: 0
 
 Value: 8406
 Name: ANASTASIS_REDUCER_RESOURCE_MALFORMED
 Description: The contents of a resource file did not match the expected format.
 HttpStatus: 0
 
 Value: 8407
 Name: ANASTASIS_REDUCER_RESOURCE_MISSING
 Description: A required resource file is missing.
 HttpStatus: 0
 
 Value: 8408
 Name: ANASTASIS_REDUCER_INPUT_REGEX_FAILED
 Description: An input did not match the regular expression.
 HttpStatus: 0
 
 Value: 8409
 Name: ANASTASIS_REDUCER_INPUT_VALIDATION_FAILED
 Description: An input did not match the custom validation logic.
 HttpStatus: 0
 
 Value: 8410
 Name: ANASTASIS_REDUCER_POLICY_LOOKUP_FAILED
 Description: Attempts to download the recovery document failed with all providers. The personal information may differ from the information provided during the backup process. Alternatively, the backup may use a provider that is unknown to this application and must be added manually.
 HttpStatus: 0
 
 Value: 8411
 Name: ANASTASIS_REDUCER_BACKUP_PROVIDER_FAILED
 Description: Anastasis provider reported a fatal failure.
 HttpStatus: 0
 
 Value: 8412
 Name: ANASTASIS_REDUCER_PROVIDER_CONFIG_FAILED
 Description: Anastasis provider failed to respond to the configuration request.
 HttpStatus: 0
 
 Value: 8413
 Name: ANASTASIS_REDUCER_POLICY_MALFORMED
 Description: The downloaded policy is malformed. This was likely caused by a client error while creating the backup.
 HttpStatus: 0
 
 Value: 8414
 Name: ANASTASIS_REDUCER_NETWORK_FAILED
 Description: The policy could not be obtained, likely due to a network issue.
 HttpStatus: 0
 
 Value: 8415
 Name: ANASTASIS_REDUCER_SECRET_MALFORMED
 Description: The recovered secret did not match the required syntax.
 HttpStatus: 0
 
 Value: 8416
 Name: ANASTASIS_REDUCER_CHALLENGE_DATA_TOO_BIG
 Description: The challenge data provided is too large for the available providers.
 HttpStatus: 0
 
 Value: 8417
 Name: ANASTASIS_REDUCER_SECRET_TOO_BIG
 Description: The provided core secret is too large for some of the providers.
 HttpStatus: 0
 
 Value: 8418
 Name: ANASTASIS_REDUCER_PROVIDER_INVALID_CONFIG
 Description: The provider returned an invalid configuration.
 HttpStatus: 0
 
 Value: 8419
 Name: ANASTASIS_REDUCER_INTERNAL_ERROR
 Description: The reducer encountered an internal error, likely a bug that needs to be reported.
 HttpStatus: 0
 
 Value: 8420
 Name: ANASTASIS_REDUCER_PROVIDERS_ALREADY_SYNCED
 Description: The reducer already synchronized with all providers.
 HttpStatus: 0
 
 # 8500 - 8600: Frosix
 
 # 8600 - 8700: Donau
 
 Value: 8606
 Name: DONAU_GENERIC_INVALID_DENOMINATION_CIPHER_FOR_OPERATION
 Description: The requested operation is not valid for the cipher used by the selected denomination.
 HttpStatus: 400
 
 Value: 8607
 Name: DONAU_GENERIC_KEYS_MISSING
 Description: The Donau failed to perform the operation as it could not find the private keys. This is a problem with the Donau setup, not with the client's request.
 HttpStatus: 503
 
 Value: 8608
 Name: DONAU_CHARITY_SIGNATURE_INVALID
 Description: The signature of the charity key is not valid.
 HttpStatus: 403
 
 Value: 8609
 Name: DONAU_CHARITY_NOT_FOUND
 Description: The charity is unknown.
 HttpStatus: 404
 
 Value: 8610
 Name: DONAU_EXCEEDING_DONATION_LIMIT
 Description: The donation amount specified in the request exceeds the limit of the charity.
 HttpStatus: 400
 
 Value: 8611
 Name: DONAU_GENERIC_DONATION_UNIT_UNKNOWN
 Description: The Donau is not aware of the donation unit requested for the operation.
 HttpStatus: 404
 
 Value: 8612
 Name: DONAU_DONATION_UNIT_HELPER_UNAVAILABLE
 Description: The Donau failed to talk to the process responsible for its private donation unit keys or the helpers had no donation units (properly) configured.
 HttpStatus: 502
 
 Value: 8613
 Name: DONAU_SIGNKEY_HELPER_UNAVAILABLE
 Description: The Donau failed to talk to the process responsible for its private signing keys.
 HttpStatus: 502
 
 Value: 8614
 Name: DONAU_SIGNKEY_HELPER_BUG
 Description: The response from the online signing key helper process was malformed.
 HttpStatus: 500
 
 Value: 8615
 Name: DONAU_GENERIC_WRONG_NUMBER_OF_SEGMENTS
 Description: The number of segments included in the URI does not match the number of segments expected by the endpoint.
 HttpStatus: 404
 
 Value: 8616
 Name: DONAU_DONATION_RECEIPT_SIGNATURE_INVALID
 Description: The signature of the donation receipt is not valid.
 HttpStatus: 403
 
 Value: 8617
 Name: DONAU_DONOR_IDENTIFIER_NONCE_REUSE
 Description: The client reused a unique donor identifier nonce, which is not allowed.
 HttpStatus: 409
 
 Value: 8618
 Name: DONAU_CHARITY_PUB_EXISTS
 Description: A charity with the same public key is already registered.
 HttpStatus: 404
 
 Value: 8619
 Name: DONAU_GENERIC_DONATION_UNIT_EXPIRED
 Description: The donation unit has expired and cannot be used any longer.
 HttpStatus: 410
 
 Value: 8620
 Name: DONAU_GENERIC_DONATION_UNIT_TOO_EARLY
 Description: The donation unit is not yet valid. The client should repeat the request in the future when it might succeed.
 HttpStatus: 425
 
 Value: 8621
 Name: DONAU_GENERIC_DONATION_UNIT_WRONG_YEAR
 Description: The donation unit is not valid for the year specified by the client.
 HttpStatus: 409
 
 
 # 9000 - 9599: LibEuFin.
 
 Value: 9000
 Name: LIBEUFIN_NEXUS_GENERIC_ERROR
 Description: A generic error occurred in the LibEuFin nexus. See the enclosed details JSON for more information.
 HttpStatus: 0
 
 Value: 9001
 Name: LIBEUFIN_NEXUS_UNCAUGHT_EXCEPTION
 Description: An uncaught exception happened in the LibEuFin nexus service.
 HttpStatus: 500
 
 Value: 9500
 Name: LIBEUFIN_SANDBOX_GENERIC_ERROR
 Description: A generic error occurred in the LibEuFin sandbox. See the enclosed details JSON for more information.
 HttpStatus: 0
 
 Value: 9501
 Name: LIBEUFIN_SANDBOX_UNCAUGHT_EXCEPTION
 Description: An uncaught exception happened in the LibEuFin sandbox service.
 HttpStatus: 500
 
 # 9600 - 9749: Taldir
 Value: 9600
 Name: TALDIR_METHOD_NOT_SUPPORTED
 Description: This validation method is not supported by the service.
 HttpStatus: 404
 
 Value: 9601
 Name: TALDIR_REGISTER_RATE_LIMITED
 Description: Number of allowed attempts for initiating a challenge exceeded.
 HttpStatus: 429
 
 # 9750-9800: Challenger
 Value: 9750
 Name: CHALLENGER_GENERIC_CLIENT_UNKNOWN
 Description: The service does not know a client with the given client identifier, or the given client secret does not match it. Used where no client has been authenticated yet.
 HttpStatus: 404
 
 Value: 9751
 Name: CHALLENGER_GENERIC_CLIENT_FORBIDDEN_BAD_REDIRECT_URI
 Description: The client is not authorized to use the given redirect URI.
 HttpStatus: 401
 
 Value: 9752
 Name: CHALLENGER_HELPER_EXEC_FAILED
 Description: The service failed to execute its helper process to send the challenge.
 HttpStatus: 502
 
 Value: 9753
 Name: CHALLENGER_GRANT_UNKNOWN
 Description: The authorization grant is unknown to the service (it could also have been redeemed already or have expired).
 HttpStatus: 400
 
 Value: 9754
 Name: CHALLENGER_CLIENT_FORBIDDEN_BAD_CODE
 Description: The code given is not even well-formed.
 HttpStatus: 400
 
 Value: 9755
 Name: CHALLENGER_GENERIC_VALIDATION_UNKNOWN
 Description: The service is not aware of the referenced validation process, or it has expired.
 HttpStatus: 404
 
 Value: 9756
 Name: CHALLENGER_CLIENT_FORBIDDEN_INVALID_CODE
 Description: Deprecated, no longer returned by any endpoint. The value stays reserved and must not be reused. Was: the code given is not valid.
 HttpStatus: 403
 
 Value: 9757
 Name: CHALLENGER_TOO_MANY_ATTEMPTS
 Description: Too many attempts have been made, validation is temporarily disabled for this address.
 HttpStatus: 429
 
 Value: 9758
 Name: CHALLENGER_INVALID_PIN
 Description: The TAN code provided is incorrect.
 HttpStatus: 403
 
 Value: 9759
 Name: CHALLENGER_MISSING_ADDRESS
 Description: Deprecated since protocol v8, no longer returned by any endpoint; see CHALLENGER_NO_CHALLENGE_TRANSMITTED. The value stays reserved and must not be reused. Was: the token cannot be valid as no address was ever provided by the client.
 HttpStatus: 409
 
 Value: 9760
 Name: CHALLENGER_CLIENT_FORBIDDEN_READ_ONLY
 Description: The client is not allowed to change the address being validated.
 HttpStatus: 403
 
 Value: 9761
 Name: CHALLENGER_NO_CHALLENGE_TRANSMITTED
 Description: No challenge was ever transmitted for this validation, so it cannot be solved yet. The user must provide their address first.
 HttpStatus: 409
 
 Value: 9762
 Name: CHALLENGER_ADDRESS_RESTRICTION_VIOLATED
 Description: An address field does not match the regular expression configured for it. The detail names the offending field.
 HttpStatus: 400
 
 Value: 9763
 Name: CHALLENGER_ADDRESS_RESTRICTION_MALFORMED
 Description: The address restriction configured for this field is missing its regular expression or the expression failed to compile. This is a server misconfiguration.
 HttpStatus: 500
 
 Value: 9764
 Name: CHALLENGER_TOO_MANY_ADDRESS_CHANGES
 Description: The number of times the address may be changed for this validation has been exhausted. The user must request a fresh nonce from the client.
 HttpStatus: 429
 
 Value: 9765
 Name: CHALLENGER_TOO_MANY_PIN_TRANSMISSIONS
 Description: The number of times the challenge may be transmitted for this validation has been exhausted. The user may still try a different address if changes remain.
 HttpStatus: 429
 
 Value: 9766
 Name: CHALLENGER_NO_PIN_ATTEMPTS_LEFT
 Description: The number of attempts to enter the TAN has been exhausted. The user may still request a retransmission or change the address.
 HttpStatus: 429
 
 Value: 9767
 Name: CHALLENGER_CLIENT_AUTHENTICATION_FAILED
 Description: Authentication of the client failed: the presented client identifier and client secret do not match a registered client. This response is returned when the endpoint authenticates the client, so it challenges the client for credentials.
 HttpStatus: 401
 
 Value: 9768
 Name: CHALLENGER_TOKEN_UNKNOWN
 Description: The access token presented is malformed, unknown or expired. Malformed and unknown tokens are deliberately not distinguished.
 HttpStatus: 401
 
 Value: 9769
 Name: CHALLENGER_ADDRESS_UNUSABLE
 Description: The transmission helper rejected the address the user provided: it is malformed, of the wrong length, not a mobile subscription, unallocated, or blocked. The user should correct the address and try again.
 HttpStatus: 400
 
 Value: 9770
 Name: CHALLENGER_ADDRESS_UNREACHABLE
 Description: The address is valid but the recipient could not be reached: the handset is switched off or out of coverage, or the message expired before delivery. Retrying later may succeed.
 HttpStatus: 503
 
 Value: 9771
 Name: CHALLENGER_HELPER_MISCONFIGURED
 Description: The transmission helper is misconfigured: a required credential is absent, the configured credentials were refused by the provider, or the provider account has insufficient balance. The operator should check the logs and the service configuration.
 HttpStatus: 500
 
 # 9800-9850: Paivana
 Value: 9800
 Name: PAIVANA_PAYMENT_MISSING
 Description: The request is invalid as the specified order is unpaid. The client should only call this endpoint after paying the order.
 HttpStatus: 409
 
 Value: 9801
 Name: PAIVANA_BACKEND_REFUSED
 Description: The merchant backend refused the request to check the payment status. The backend is either unavailable or Paivana is misconfigured. The system administrator should check the logs.
 HttpStatus: 502
 
 Value: 9802
 Name: PAIVANA_ORDER_UNKNOWN
 Description: The order specified in the request is unknown to the backend. The client must instantiate the Paivana template first and pay the order before calling this endpoint.
 HttpStatus: 404
 
 Value: 9803
 Name: PAIVANA_BACKEND_ERROR
 Description: The merchant backend returned an unexpected status code. This is probably a protocol incompatibility that should be reported to the developers.
 HttpStatus: 500
 
 Value: 9804
 Name: PAIVANA_GET_ORDER_FAILED
 Description: Paivana failed to initialize the request to check the payment status. This should never happen. The system administrator should consult the logs.
 HttpStatus: 500
 
 Value: 9805
 Name: PAIVANA_WRONG_ORDER
 Description: The specified order does not match the specified Website or nonce and thus the order is invalid for the given request. Clients should pay for the correct order for access to the resource.
 HttpStatus: 409
 
 Value: 9806
 Name: PAIVANA_TOO_LATE
 Description: The specified expiration time for the cookie is longer than what the purchase allows. The request may succeed with a shorter expiration time. Alternatively, the user may need to purchase access again.
 HttpStatus: 410
 
 Value: 9807
 Name: PAIVANA_TEMPLATE_UNKNOWN
 Description: The payment template specified in the request is unknown to the backend.
 HttpStatus: 404
 
 Value: 9808
 Name: PAIVANA_PAYWALL_DISABLED
 Description: The paywall functionality is currently disabled. Thus, proofs of payment are unnecessary and also not supported.
 HttpStatus: 501
 
 Value: 9809
 Name: PAIVANA_INVALID_TARGET
 Description: The website specified in the request is not acceptable for this backend. Somehow the client must have specified an invalid website which is not configured for this Paivana reverse proxy and thus not eligible as a target for the redirect. A developer should check how the client computed the fulfillment_url of the order and fix it.
 HttpStatus: 409
 
 
 
 # Some of our build systems expect the range to be < 10k, so let's keep it like this for now.
 Value: 9999
 Name: END
 Description: End of error code range.
 HttpStatus: 0