commit 8799feeb0be3494b727962d2061548c83f547bde
parent d7ac4af315814676a246437b091eb0d5ecf25ba1
Author: Florian Dold <dold@taler.net>
Date: Mon, 17 Aug 2026 18:45:12 +0200
gnu-taler-error-codes: grammar/spelling/phrasing pass
Diffstat:
1 file changed, 152 insertions(+), 152 deletions(-)
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec
@@ -10,7 +10,7 @@
%constraint: ( Value < 100 ) || ( Value > 999 )
%type: Value ValueRange_t
%mandatory: Value
-%typedef: Description_t regexp |^[abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_-][abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_\(\)\.,;!"':#\/ -]*$|
+%typedef: Description_t regexp |^[abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_-][abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_\(\)\.,;!"':#`\/ -]*$|
%type: Description Description_t
%mandatory: Description
%typedef: Name_t regexp /^[ABCDEFGHIJKLMNOPQRSTUVWXYZ_][ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789]*$/
@@ -38,7 +38,7 @@ HttpStatus: 0
Value: 2
Name: GENERIC_CLIENT_INTERNAL_ERROR
-Description: An internal failure happened on the client side. Details should be in the local logs. Check if you are using the latest available version or file a report with the developers.
+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
@@ -50,7 +50,7 @@ HttpStatus: 0
Value: 10
Name: GENERIC_INVALID_RESPONSE
-Description: The response we got from the server was not in the expected format. Most likely, the server does not speak the GNU Taler protocol. Check the URL and/or the network connection to the server.
+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
@@ -65,7 +65,7 @@ HttpStatus: 0
Value: 13
Name: GENERIC_REPLY_MALFORMED
-Description: The service responded with a reply that was in the right data format, but the content did not satisfy the protocol. Please file a bug report.
+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
@@ -88,37 +88,37 @@ HttpStatus: 403
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 if you are using the latest available version and/or file a report with the developers.
+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 if you used the correct URL and/or file a report with the developers of the client software.
+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 if you are using the latest available version and/or file a report with the developers.
+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 and caused the server to not be able to handle the request. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+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 you are using the correct syntax as of RFC 8905 and/or that you entered the bank account number correctly.
+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 if you are using the latest available version and/or file a report with the developers.
+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 if you are using the latest available version and/or file a report with the developers.
+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
@@ -129,12 +129,12 @@ 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 if you are using the latest available version and/or file a report with the developers.
+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 you are using the correct encoding for the URL.
+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)
@@ -142,22 +142,22 @@ HttpStatus: 400
Value: 30
Name: GENERIC_CURRENCY_MISMATCH
-Description: The currency involved in the operation is not acceptable for this server. Check your configuration and make sure the currency specified for a given service provider is one of the currencies supported by that provider.
+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 you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the limit.
+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 to be permissible for the endpoint. If you believe this was a legitimate request, contact the server administrators and/or the software developers to increase the 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 in the request was given that must not be present. This is likely a bug in the client implementation. Check if you are using the latest available version and/or file a report with the developers.
+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
@@ -168,34 +168,34 @@ HttpStatus: 401
Value: 41
Name: GENERIC_TOKEN_UNKNOWN
-Description: The service refused the request as the given authorization token is unknown. You should request a valid access token from the account owner.
+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 as the given authorization token expired. You should request a fresh authorization token from the account owner.
+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 as the given authorization token is invalid or malformed. You should check that you have the right credentials.
+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 due to lack of proper rights on the resource. You may need different credentials to be allowed to perform this operation.
+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 initialize its connection to the database. The system administrator should check that the service has permissions to access the database and that the database is running.
+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 event to just start the database transaction. The system administrator should check that the database is running.
+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
@@ -215,12 +215,12 @@ HttpStatus: 500
Value: 55
Name: GENERIC_DB_SOFT_FAILURE
-Description: The service encountered an error event to commit the database transaction, even after repeatedly retrying it there was always a conflicting transaction. This indicates a repeated serialization error; it should only happen if some client maliciously tries to create conflicting concurrent transactions. It could also be a sign of a missing index. Check if you are using the latest available version and/or file a report with the developers.
+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 if you are using the latest available version and/or file a report with the developers.
+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
@@ -228,17 +228,17 @@ HttpStatus: 500
Value: 60
Name: GENERIC_INTERNAL_INVARIANT_FAILURE
-Description: The HTTP server experienced an internal invariant failure (bug). Check if you are using the latest available version and/or file a report with the developers.
+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 some JSON value. Check if you are using the latest available version and/or file a report with the developers.
+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 if you are using the latest available version and/or file a report with the developers.
+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
@@ -256,7 +256,7 @@ HttpStatus: 500
Value: 72
Name: GENERIC_JSON_ALLOCATION_FAILURE
-Description: The HTTP server failed to allocate memory for building JSON reply. Restarting services periodically can help, especially if Postgres is using excessive amounts of memory. Check with the system administrator to investigate.
+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
@@ -266,12 +266,12 @@ HttpStatus: 500
Value: 74
Name: GENERIC_FAILED_TO_LOAD_TEMPLATE
-Description: The backend could not locate a required template to generate an HTML reply. The system administrator should check if the resource files are installed in the correct location and are readable to the service.
+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 reply. The system administrator should investigate the logs and check if the templates are well-formed.
+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
@@ -305,7 +305,7 @@ HttpStatus: 500
Value: 1001
Name: EXCHANGE_GENERIC_OPERATION_UNKNOWN
-Description: Operation specified unknown for this endpoint.
+Description: The specified operation is unknown for this endpoint.
HttpStatus: 404
Value: 1002
@@ -320,7 +320,7 @@ HttpStatus: 409
Value: 1004
Name: EXCHANGE_GENERIC_COINS_INVALID_COIN_PUB
-Description: The public key of given to a "/coins/" endpoint of the exchange was malformed.
+Description: The public key given to the `/coins/` endpoint of the exchange was malformed.
HttpStatus: 400
Value: 1005
@@ -345,7 +345,7 @@ HttpStatus: 412
Value: 1009
Name: EXCHANGE_GENERIC_DENOMINATION_EXPIRED
-Description: Denomination key of the coin is past its expiration time for the requested operation.
+Description: The denomination key of the coin has passed its expiration time for the requested operation.
HttpStatus: 410
Value: 1010
@@ -360,7 +360,7 @@ HttpStatus: 500
Value: 1012
Name: EXCHANGE_GENERIC_INSUFFICIENT_FUNDS
-Description: The respective coin did not have sufficient residual value for the operation. The "history" in this response provides the "residual_value" of the coin, which may be less than its "original_value".
+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
@@ -435,7 +435,7 @@ HttpStatus: 410
Value: 1027
Name: EXCHANGE_GENERIC_RESERVE_UNKNOWN
-Description: The exchange has no information about the "reserve_pub" that was given.
+Description: The exchange has no information about the `reserve_pub` that was provided.
HttpStatus: 404
Value: 1028
@@ -445,12 +445,12 @@ HttpStatus: 451
Value: 1029
Name: EXCHANGE_PURSE_DEPOSIT_COIN_CONFLICTING_ATTEST_VS_AGE_COMMITMENT
-Description: Inconsistency between provided age commitment and attest: either none or both must be provided
+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 couldn't be verified by the exchange.
+Description: The provided attestation for the minimum age could not be verified by the exchange.
HttpStatus: 400
Value: 1031
@@ -505,7 +505,7 @@ 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 select account is correct.
+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
@@ -515,7 +515,7 @@ HttpStatus: 500
Value: 1043
Name: EXCHANGE_GENERIC_KYC_SANCTION_LIST_CHECK_FAILED
-Description: A check against sanction lists failed. This is indicative of an internal error in the sanction list processing logic. This needs to be investigated by the exchange operator.
+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
@@ -560,27 +560,27 @@ HttpStatus: 404
Value: 1101
Name: EXCHANGE_DEPOSITS_GET_INVALID_H_WIRE
-Description: The wire hash of given to a "/deposits/" handler was malformed.
+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 of given to a "/deposits/" handler was malformed.
+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 a "/deposits/" handler was malformed.
+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 of given to a "/deposits/" handler was malformed.
+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.
+Description: The signature returned by the exchange in a `/deposits/` request was malformed.
HttpStatus: 0
Value: 1106
@@ -590,17 +590,17 @@ HttpStatus: 403
Value: 1107
Name: EXCHANGE_DEPOSITS_POLICY_NOT_ACCEPTED
-Description: The provided policy data was 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 withdraw operation at this time. The response includes the current "balance" of the reserve as well as the transaction "history" that lead to this balance.
+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-withdraw operation at this time. The response includes the current "balance" of the reserve as well as the transaction "history" that lead to this balance.
+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
@@ -620,7 +620,7 @@ HttpStatus: 403
Value: 1155
Name: EXCHANGE_RESERVE_HISTORY_ERROR_INSUFFICIENT_FUNDS
-Description: When computing the reserve history, we ended up with a negative overall balance, which should be impossible.
+Description: Computing the reserve history resulted in a negative overall balance, which should be impossible.
HttpStatus: 500
Value: 1156
@@ -660,12 +660,12 @@ HttpStatus: 400
Value: 1164
Name: EXCHANGE_WITHDRAW_REVEAL_INVALID_HASH
-Description: The original commitment differs from the calculated 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
+Description: The maximum age in the commitment is too large for the reserve.
HttpStatus: 409
Value: 1175
@@ -695,12 +695,12 @@ HttpStatus: 400
Value: 1209
Name: EXCHANGE_DEPOSIT_WIRE_DEADLINE_IS_NEVER
-Description: The stated wire deadline is "never", which makes no sense.
+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 while the exchange will do some basic sanity checking on the wire details, it cannot warrant that the banking system will ultimately be able to route to the specified address, even if this check passed.
+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
@@ -748,7 +748,7 @@ HttpStatus: 403
Value: 1305
Name: EXCHANGE_MELT_COIN_EXPIRED_NO_ZOMBIE
-Description: The denomination of the given coin has past its expiration date and it is also not a valid zombie (that is, was not refreshed with the fresh coin being subjected to recoup).
+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
@@ -799,12 +799,12 @@ HttpStatus: 403
Value: 1362
Name: EXCHANGE_REFRESHES_REVEAL_INVALID_RCH
-Description: The refresh session hash given to a /refreshes/ handler was malformed.
+Description: The refresh session hash given to the `/refreshes/` handler was malformed.
HttpStatus: 400
Value: 1363
Name: EXCHANGE_REFRESHES_REVEAL_OPERATION_INVALID
-Description: Operation specified invalid for this endpoint.
+Description: The specified operation is invalid for this endpoint.
HttpStatus: 400
Value: 1364
@@ -825,7 +825,7 @@ HttpStatus: 404
Value: 1450
Name: EXCHANGE_TRANSFERS_GET_WTID_MALFORMED
-Description: The public key of given to a /transfers/ handler was malformed.
+Description: The public key given to the `/transfers/` handler was malformed.
HttpStatus: 400
Value: 1451
@@ -856,22 +856,22 @@ HttpStatus: 0
Value: 1500
Name: EXCHANGE_REFUND_COIN_NOT_FOUND
-Description: The exchange knows literally nothing about the coin we were asked to refund. But without a transaction history, we cannot issue a refund. This is kind-of OK, the owner should just refresh it directly without executing the refund.
+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: We could not process the refund request as the coin's transaction history does not permit the requested refund because then refunds would exceed the deposit amount. The "history" in the response proves this.
+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 we were asked to refund, but not about the specific /deposit operation. Hence, we cannot issue a refund (as we do not know if this merchant public key is authorized to do a refund).
+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/coin as the money was already transferred (paid out) to the merchant. (It should be past the refund deadline.)
+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
@@ -964,7 +964,7 @@ 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.
+Description: This exchange does not allow clients to request `/keys` for times other than the current exchange time.
HttpStatus: 403
Value: 1650
@@ -974,7 +974,7 @@ HttpStatus: 0
Value: 1651
Name: EXCHANGE_WIRE_NO_ACCOUNTS_CONFIGURED
-Description: No bank accounts are enabled for the exchange. The administrator should enable-account using the taler-exchange-offline tool.
+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
@@ -990,12 +990,12 @@ HttpStatus: 500
Value: 1675
Name: EXCHANGE_RESERVES_PURSE_CREATE_CONFLICTING_META_DATA
-Description: This purse was previously created with different 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 meta data.
+Description: This purse was previously merged with different metadata.
HttpStatus: 409
Value: 1677
@@ -1040,7 +1040,7 @@ HttpStatus: 400
Value: 1725
Name: EXCHANGE_PURSE_DEPOSIT_EXCHANGE_SIGNATURE_INVALID
-Description: The signature of the exchange on the reply was invalid.
+Description: The exchange's signature on the response was invalid.
HttpStatus: 0
@@ -1098,7 +1098,7 @@ HttpStatus: 403
Value: 1787
Name: EXCHANGE_RESERVES_ATTEST_BAD_SIGNATURE
-Description: The signature by the reserve affirming the attestion request is invalid.
+Description: The signature by the reserve affirming the attestation request is invalid.
HttpStatus: 403
Value: 1788
@@ -1228,7 +1228,7 @@ HttpStatus: 409
Value: 1828
Name: EXCHANGE_AML_DECISION_UNKNOWN_CHECK
-Description: There AML decision would impose an AML check of a type that is not provided by any KYC provider known to the exchange.
+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
@@ -1243,19 +1243,19 @@ HttpStatus: 409
Value: 1832
Name: EXCHANGE_MANAGEMENT_CONFLICTING_DENOMINATION_META_DATA
-Description: The exchange already has this denomination key configured, but with different meta data. This should not be possible, contact the developers for support.
+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 meta data. This should not be possible, contact the developers for support.
+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 meta data.
+Description: The purse was previously created with different metadata.
HttpStatus: 409
Value: 1851
@@ -1275,12 +1275,12 @@ HttpStatus: 400
Value: 1854
Name: EXCHANGE_PURSE_CREATE_EXPIRATION_IS_NEVER
-Description: The purse expiration time 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 meta data is invalid.
+Description: The purse signature over the purse metadata is invalid.
HttpStatus: 403
Value: 1856
@@ -1295,12 +1295,12 @@ HttpStatus: 0
Value: 1858
Name: EXCHANGE_PURSE_DEPOSIT_CONFLICTING_META_DATA
-Description: The coin was previously deposited with different 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 meta data.
+Description: The encrypted contract was previously uploaded with different metadata.
HttpStatus: 409
Value: 1860
@@ -1346,7 +1346,7 @@ HttpStatus: 409
Value: 1900
Name: EXCHANGE_AUDITORS_AUDITOR_SIGNATURE_INVALID
-Description: The auditor signature over the denomination meta data is invalid.
+Description: The auditor signature over the denomination metadata is invalid.
HttpStatus: 403
Value: 1901
@@ -1376,7 +1376,7 @@ 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-inputs that did not result in a timely conclusion. This is a configuration failure. Please contact the administrator.
+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
@@ -1421,7 +1421,7 @@ HttpStatus: 403
Value: 1929
Name: EXCHANGE_KYC_PROOF_REQUEST_UNKNOWN
-Description: The exchange is unaware of having made an the authorization request.
+Description: The exchange is unaware of having made the authorization request.
HttpStatus: 404
Value: 1930
@@ -1481,7 +1481,7 @@ HttpStatus: 409
Value: 1941
Name: EXCHANGE_KYC_FORM_ALREADY_UPLOADED
-Description: The form has been previously uploaded, and may only be filed once. The user should be redirected to their main KYC page and see if any other steps need to be taken.
+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
@@ -1588,7 +1588,7 @@ 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, we refuse to do business with this exchange. The administrator should check if they configured the exchange correctly in the merchant backend.
+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
@@ -1608,7 +1608,7 @@ HttpStatus: 404
Value: 2006
Name: MERCHANT_GENERIC_PRODUCT_UNKNOWN
-Description: The order provided to the backend could not be completed, because a product to be completed via inventory data is not actually in our inventory.
+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
@@ -1643,7 +1643,7 @@ HttpStatus: 500
Value: 2013
Name: MERCHANT_GENERIC_EXCHANGE_REPLY_MALFORMED
-Description: The exchange returned a maformed response.
+Description: The exchange returned a malformed response.
HttpStatus: 502
Value: 2014
@@ -1668,22 +1668,22 @@ HttpStatus: 404
Value: 2018
Name: MERCHANT_GENERIC_TEMPLATE_UNKNOWN
-Description: The backend could not find the template(id) because it is not exist.
+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(id) because it is not exist.
+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(serial) because it is not exist.
+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(id) because it is not exist.
+Description: The backend could not find the OTP device with the specified ID because it does not exist.
HttpStatus: 404
Value: 2022
@@ -1733,7 +1733,7 @@ HttpStatus: 501
Value: 2031
Name: MERCHANT_GENERIC_MFA_MISSING
-Description: This operation requires multi-factor authorization and the respective instance does not have a sufficient number of factors that could be validated configured. You need to ask the system administrator to perform this operation.
+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
@@ -1743,7 +1743,7 @@ HttpStatus: 502
Value: 2033
Name: MERCHANT_GENERIC_UNIT_BUILTIN
-Description: The unit referenced in the request is builtin and cannot be modified or deleted.
+Description: The unit referenced in the request is built-in and cannot be modified or deleted.
HttpStatus: 409
Value: 2034
@@ -1778,7 +1778,7 @@ HttpStatus: 404
Value: 2040
Name: MERCHANT_GENERIC_EXPECTED_TRANSFER_UNKNOWN
-Description: The merchant does not expect any transfer with the given ID and can thus not return any details about it.
+Description: The merchant does not expect a transfer with the given ID and therefore cannot return any details about it.
HttpStatus: 404
Value: 2041
@@ -1857,7 +1857,7 @@ HttpStatus: 502
Value: 2129
Name: MERCHANT_TAN_CHALLENGE_SOLVED
-Description: The challenge was already solved. Thus, we refuse to send it again.
+Description: The challenge was already solved. Therefore, the service refuses to send it again.
HttpStatus: 410
Value: 2130
@@ -1919,7 +1919,7 @@ HttpStatus: 400
Value: 2156
Name: MERCHANT_POST_ORDERS_ID_PAY_PAYMENT_INSUFFICIENT
-Description: Even if we do not consider deposit and wire fees, the payment is insufficient to satisfy the required amount for the contract.
+Description: Even without considering deposit and wire fees, the payment is insufficient to satisfy the required amount for the contract.
HttpStatus: 400
Value: 2157
@@ -1929,7 +1929,7 @@ HttpStatus: 403
Value: 2158
Name: MERCHANT_POST_ORDERS_ID_PAY_EXCHANGE_LOOKUP_FAILED
-Description: When we tried to find information about the exchange to issue the deposit, we failed. This usually only happens if the merchant backend is somehow unable to get its own HTTP client logic to work.
+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
@@ -1949,7 +1949,7 @@ HttpStatus: 410
Value: 2162
Name: MERCHANT_POST_ORDERS_ID_PAY_MERCHANT_FIELD_MISSING
-Description: The "merchant" field is missing in the proposal data. This is an internal error as the proposal is from the merchant's own database at this point.
+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
@@ -1969,12 +1969,12 @@ HttpStatus: 500
Value: 2167
Name: MERCHANT_POST_ORDERS_ID_PAY_REFUNDED
-Description: The contract was not fully paid because of refunds. Note that clients MAY treat this as paid if, for example, contracts must be executed despite of refunds.
+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: According to our database, we have refunded more than we were paid (which should not be possible).
+Description: The database indicates that more was refunded than was paid, which should not be possible.
HttpStatus: 500
Value: 2169
@@ -1999,7 +1999,7 @@ 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 couldn't be verified with the given age_commitment for that particular minimum age.
+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
@@ -2054,7 +2054,7 @@ 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 has a bug in that it failed to check exchange limits during coin selection. Please report the bug to your wallet developer.
+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
@@ -2069,7 +2069,7 @@ HttpStatus: 451
Value: 2187
Name: MERCHANT_POST_ORDERS_ID_PAY_CHOICE_INDEX_MISMATCH
-Description: The order was already paid, but completing a different choice than the one given in this request. The client should use the choice the order was actually paid with.
+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
@@ -2132,12 +2132,12 @@ HttpStatus: 400
Value: 2258
Name: MERCHANT_EXCHANGE_TRANSFERS_AWAITING_KEYS
-Description: We are waiting for the exchange to provide us with key material before checking the wire transfer.
+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: We are waiting for the exchange to provide us with the list of aggregated transactions.
+Description: The merchant is waiting for the exchange to provide the list of aggregated transactions.
HttpStatus: 202
Value: 2260
@@ -2157,7 +2157,7 @@ HttpStatus: 202
Value: 2263
Name: MERCHANT_EXCHANGE_TRANSFERS_TRANSIENT_FAILURE
-Description: We experienced a transient failure in our interaction with the exchange.
+Description: The merchant experienced a transient failure while interacting with the exchange.
HttpStatus: 202
Value: 2264
@@ -2189,17 +2189,17 @@ HttpStatus: 502
Value: 2300
Name: MERCHANT_POST_ORDERS_ID_CLAIM_NOT_FOUND
-Description: We could not claim the order because the backend is unaware of it.
+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: We could not claim the order because someone else claimed it first.
+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-side experienced an internal failure.
+Description: The client experienced an internal failure.
HttpStatus: 0
Value: 2303
@@ -2289,7 +2289,7 @@ 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.
+Description: The order creation request is invalid because a wire deadline of `never` is not allowed.
HttpStatus: 400
Value: 2507
@@ -2304,7 +2304,7 @@ 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 any bank account of this instance using the wire method specified with the order. (Note that right now, we do not support the use of exchange bank accounts with mandatory currency conversion.) One likely cause for this is that the taler-merchant-exchangekeyupdate process is not running.
+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
@@ -2319,24 +2319,24 @@ 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. Please find another way to refund the customer, and inquire with your legislator why they make strange banking regulations.
+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 hard legal transaction limits from the available exchanges, thus a customer could never legally make this payment. You may try to increase your limits by passing legitimization checks with exchange operators. You could also inquire with your legislator why the limits are prohibitively low for your business.
+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 additional suitable exchange operators to the merchant backend configuration, or (3) satisfying compliance rules of an configured exchange to begin using the service of that provider.
+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, our offer is still valid and awaiting payment. Deletion may work later after the offer has expired if it remains unpaid.
+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
@@ -2408,7 +2408,7 @@ HttpStatus: 502
Value: 2551
Name: MERCHANT_PRIVATE_POST_TRANSFERS_REQUEST_ERROR
-Description: We internally failed to execute the /track/transfer request.
+Description: The backend failed to execute the `/track/transfer` request internally.
HttpStatus: 502
Value: 2552
@@ -2428,12 +2428,12 @@ HttpStatus: 502
Value: 2555
Name: MERCHANT_PRIVATE_POST_TRANSFERS_ACCOUNT_NOT_FOUND
-Description: We did not find the account that the transfer was made to.
+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 as the echange already replied to our inquiry about it and we have integrated the result.
+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
@@ -2502,7 +2502,7 @@ 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 something else about the specific account. Consult the exchange account constraints and specify a different bank account if you want to use this 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
@@ -2545,17 +2545,17 @@ HttpStatus: 410
Value: 2680
Name: MERCHANT_PRIVATE_DELETE_PRODUCTS_CONFLICTING_LOCK
-Description: The deletion request is for a product that is locked. The product cannot be deleted until the existing offer to expires.
+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. You should select a different 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. You should select a different name.
+Description: The proposed name for the money pot is already in use. The client should select a different name.
HttpStatus: 409
Value: 2692
@@ -2641,12 +2641,12 @@ HttpStatus: 409
Value: 2864
Name: MERCHANT_POST_USING_TEMPLATES_WRONG_TYPE
-Description: The selected template has a different type than the one specified in the request of the client. This may happen if the template was updated since the last time the client fetched it. The client should re-fetch the current template and send a request of the correct 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 last time the client fetched it. The client should re-fetch the current template and send a request of the correct type.
+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
@@ -2885,7 +2885,7 @@ HttpStatus: 409
Value: 5137
Name: BANK_NON_ADMIN_PATCH_MISSING_OLD_PASSWORD
-Description: A non-admin user has tried to change their password whihout providing the current one.
+Description: A non-admin user tried to change their password without providing the current password.
HttpStatus: 409
Value: 5138
@@ -2910,7 +2910,7 @@ HttpStatus: 409
Value: 5142
Name: BANK_ADMIN_CREDITOR
-Description: The client tried to create a transaction that credit the admin account.
+Description: The client tried to create a transaction that credits the administrator's account.
HttpStatus: 409
Value: 5143
@@ -2935,7 +2935,7 @@ HttpStatus: 409
Value: 5147
Name: BANK_CONVERSION_AMOUNT_TO_SMALL
-Description: Amount of currency conversion it less than the minimum allowed.
+Description: The amount of the currency conversion is less than the minimum allowed.
HttpStatus: 409
Value: 5148
@@ -2960,12 +2960,12 @@ HttpStatus: 409
Value: 5152
Name: BANK_ACCOUNT_LOCKED
-Description: Bank account is locked and cannot authenticate using his password.
+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 a transaction' details that was already aborted.
+Description: The client attempted to update the details of a transaction that was already aborted.
HttpStatus: 409
Value: 5154
@@ -2975,12 +2975,12 @@ HttpStatus: 409
Value: 5155
Name: BANK_NON_ADMIN_SET_CONVERSION_RATE_CLASS
-Description: A non-admin user has tried to set their 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
+Description: The referenced conversion rate class was not found.
HttpStatus: 409
Value: 5157
@@ -3010,7 +3010,7 @@ 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 recurrent transfer.
+Description: The `authorization_pub` for a request to transfer funds has already been used for another non-recurring transfer.
HttpStatus: 409
Value: 5163
@@ -3023,7 +3023,7 @@ HttpStatus: 409
Value: 6100
Name: SYNC_ACCOUNT_UNKNOWN
-Description: The sync service failed find the account in its database.
+Description: The sync service failed to find the account in its database.
HttpStatus: 404
Value: 6101
@@ -3073,12 +3073,12 @@ HttpStatus: 408
Value: 6110
Name: SYNC_PAYMENT_CREATE_BACKEND_ERROR
-Description: Sync could not setup the payment request with its own backend.
+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 find the backup to be updated in its database.
+Description: The sync service failed to find the backup to be updated in its database.
HttpStatus: 404
Value: 6112
@@ -3122,7 +3122,7 @@ HttpStatus: 500
Value: 7002
Name: WALLET_RECEIVED_MALFORMED_RESPONSE
-Description: The wallet received a response from a server, but the response can't be parsed.
+Description: The wallet received a response from a server, but the response cannot be parsed.
HttpStatus: 0
Value: 7003
@@ -3167,7 +3167,7 @@ HttpStatus: 0
Value: 7012
Name: WALLET_WITHDRAWAL_OPERATION_ABORTED_BY_BANK
-Description: The bank has aborted a withdrawal operation, and thus a withdrawal can't complete.
+Description: The bank aborted a withdrawal operation, so the withdrawal cannot complete.
HttpStatus: 0
Value: 7013
@@ -3212,7 +3212,7 @@ HttpStatus: 0
Value: 7021
Name: WALLET_PENDING_OPERATION_FAILED
-Description: A pending operation failed, and thus the request can't be completed.
+Description: A pending operation failed, so the request cannot be completed.
HttpStatus: 0
Value: 7022
@@ -3272,7 +3272,7 @@ HttpStatus: 0
Value: 7033
Name: WALLET_EXCHANGE_ENTRY_USED
-Description: An exchange entry is still used by the exchange, thus it can't be deleted without purging.
+Description: An exchange entry is still used by the exchange, so it cannot be deleted without purging.
HttpStatus: 0
Value: 7034
@@ -3282,12 +3282,12 @@ HttpStatus: 0
Value: 7035
Name: WALLET_TALER_URI_MALFORMED
-Description: A taler:// URI is malformed and can't be parsed.
+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 thus can't provide a response.
+Description: A wallet-core request was cancelled and therefore cannot provide a response.
HttpStatus: 0
Value: 7037
@@ -3454,7 +3454,7 @@ HttpStatus: 0
Value: 8000
Name: ANASTASIS_GENERIC_BACKEND_TIMEOUT
-Description: We encountered a timeout with our payment backend.
+Description: The service encountered a timeout with its payment backend.
HttpStatus: 504
Value: 8001
@@ -3464,7 +3464,7 @@ HttpStatus: 0
Value: 8002
Name: ANASTASIS_GENERIC_BACKEND_ERROR
-Description: The backend got an unexpected reply from the payment processor.
+Description: The backend received an unexpected response from the payment processor.
HttpStatus: 502
Value: 8003
@@ -3540,7 +3540,7 @@ HttpStatus: 404
Value: 8116
Name: ANASTASIS_TRUTH_ORDER_DISAPPEARED
-Description: The backend forgot the order we asked the client to pay for
+Description: The backend no longer knows about the order that the client was asked to pay for.
HttpStatus: 502
Value: 8117
@@ -3550,7 +3550,7 @@ HttpStatus: 502
Value: 8118
Name: ANASTASIS_TRUTH_UNEXPECTED_PAYMENT_STATUS
-Description: The backend reported a payment status we did not expect.
+Description: The backend reported an unexpected payment status.
HttpStatus: 500
Value: 8119
@@ -3608,12 +3608,12 @@ HttpStatus: 409
Value: 8211
Name: ANASTASIS_EMAIL_HELPER_EXEC_FAILED
-Description: Failed to run the E-mail transmission helper process.
+Description: Failed to run the email transmission helper process.
HttpStatus: 500
Value: 8212
Name: ANASTASIS_EMAIL_HELPER_COMMAND_FAILED
-Description: Provider failed to send E-mail. Helper terminated with a non-successful result.
+Description: The provider failed to send email. The helper terminated with a non-successful result.
HttpStatus: 500
@@ -3724,12 +3724,12 @@ HttpStatus: 0
Value: 8405
Name: ANASTASIS_REDUCER_BACKEND_FAILURE
-Description: We experienced an unexpected failure interacting with the backend.
+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 our expectations.
+Description: The contents of a resource file did not match the expected format.
HttpStatus: 0
Value: 8407
@@ -3749,7 +3749,7 @@ HttpStatus: 0
Value: 8410
Name: ANASTASIS_REDUCER_POLICY_LOOKUP_FAILED
-Description: Our attempts to download the recovery document failed with all providers. Most likely the personal information you entered differs from the information you provided during the backup process and you should go back to the previous step. Alternatively, if you used a backup provider that is unknown to this application, you should add that provider manually.
+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
@@ -3764,12 +3764,12 @@ HttpStatus: 0
Value: 8413
Name: ANASTASIS_REDUCER_POLICY_MALFORMED
-Description: The policy we downloaded is malformed. Must have been a client error while creating the backup.
+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: We failed to obtain the policy, likely due to a network issue.
+Description: The policy could not be obtained, likely due to a network issue.
HttpStatus: 0
Value: 8415
@@ -3789,7 +3789,7 @@ HttpStatus: 0
Value: 8418
Name: ANASTASIS_REDUCER_PROVIDER_INVALID_CONFIG
-Description: The provider returned in invalid configuration.
+Description: The provider returned an invalid configuration.
HttpStatus: 0
Value: 8419
@@ -3891,7 +3891,7 @@ HttpStatus: 409
Value: 9000
Name: LIBEUFIN_NEXUS_GENERIC_ERROR
-Description: A generic error happened in the LibEuFin nexus. See the enclose details JSON for more information.
+Description: A generic error occurred in the LibEuFin nexus. See the enclosed details JSON for more information.
HttpStatus: 0
Value: 9001
@@ -3901,7 +3901,7 @@ HttpStatus: 500
Value: 9500
Name: LIBEUFIN_SANDBOX_GENERIC_ERROR
-Description: A generic error happened in the LibEuFin sandbox. See the enclose details JSON for more information.
+Description: A generic error occurred in the LibEuFin sandbox. See the enclosed details JSON for more information.
HttpStatus: 0
Value: 9501
@@ -4008,7 +4008,7 @@ HttpStatus: 429
Value: 9767
Name: CHALLENGER_CLIENT_AUTHENTICATION_FAILED
-Description: Authentication of the client failed: the client identifier and client secret presented do not match a registered client. Returned where the endpoint authenticates the client, so the reply challenges for credentials.
+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
@@ -4039,7 +4039,7 @@ HttpStatus: 409
Value: 9801
Name: PAIVANA_BACKEND_REFUSED
-Description: The merchant backend refused our request to check the payment status. The backend is either down or Paivana is configured badly. The system administrator should check the logs.
+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
