aboutsummaryrefslogtreecommitdiff
path: root/gnu-taler-error-codes/registry.rec
diff options
context:
space:
mode:
Diffstat (limited to 'gnu-taler-error-codes/registry.rec')
-rw-r--r--gnu-taler-error-codes/registry.rec90
1 files changed, 76 insertions, 14 deletions
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec
index c0a4cac..36d1ee4 100644
--- a/gnu-taler-error-codes/registry.rec
+++ b/gnu-taler-error-codes/registry.rec
@@ -833,12 +833,9 @@ Description: The merchant failed to provide a meaningful response to a /pay requ
833HttpStatus: 0 833HttpStatus: 0
834 834
835Value: 2101 835Value: 2101
836Name: PAY_EXCHANGE_FAILED 836Name: PAY_INSUFFICIENT_FUNDS
837Description: The exchange failed to provide a meaningful response to a /deposit request. 837Description: The exchange responded saying that funds were insufficient (for example, due to double-spending).
838HttpStatus: 424 838HttpStatus: 409
839# This code has two associated HTTP status codes, but entering both in the registry
840# causes two conflicting definitions in the C header generated.
841# HttpStatus: 409
842 839
843Value: 2102 840Value: 2102
844Name: PAY_DB_STORE_PAY_ERROR 841Name: PAY_DB_STORE_PAY_ERROR
@@ -950,6 +947,11 @@ Name: PAY_WIRE_FEE_CURRENCY_MISMATCH
950Description: We got different currencies for the wire fee and the maximum wire fee. 947Description: We got different currencies for the wire fee and the maximum wire fee.
951HttpStatus: 500 948HttpStatus: 500
952 949
950Value: 2126
951Name: PAY_EXCHANGE_REPLY_MALFORMED
952Description: The exchange had a failure when trying to process the request, returning a malformed response.
953HttpStatus: 424
954
953Value: 2127 955Value: 2127
954Name: PAY_WRONG_INSTANCE 956Name: PAY_WRONG_INSTANCE
955Description: A unknown merchant public key was included in the payment. That happens typically when the wallet sends the payment to the wrong merchant instance. 957Description: A unknown merchant public key was included in the payment. That happens typically when the wallet sends the payment to the wrong merchant instance.
@@ -990,6 +992,11 @@ Name: PAY_ABORT_REFUND_REFUSED_PAYMENT_COMPLETE
990Description: Legacy stuff. Remove me with protocol v1. 992Description: Legacy stuff. Remove me with protocol v1.
991HttpStatus: 0 993HttpStatus: 0
992 994
995Value: 2135
996Name: PAY_EXCHANGE_FAILED
997Description: The payment failed at the exchange.
998HttpStatus: 424
999
993Value: 2150 1000Value: 2150
994Name: ABORT_EXCHANGE_KEYS_FAILURE 1001Name: ABORT_EXCHANGE_KEYS_FAILURE
995Description: The merchant failed to contact the exchange. 1002Description: The merchant failed to contact the exchange.
@@ -1764,36 +1771,91 @@ Description: We failed to find the contract terms from our merchant database.
1764HttpStatus: 404 1771HttpStatus: 404
1765 1772
1766Value: 2902 1773Value: 2902
1767Name: GET_ORDERS_WRONG_CONTRACT 1774Name: GET_ORDERS_EXCHANGE_TIMEOUT
1768Description: The contract hash provided by the wallet does not match the order. 1775Description: The merchant had a timeout contacting the exchange, thus not providing wire details in the response.
1769HttpStatus: 403 1776HttpStatus: 200
1777
1778Value: 2903
1779Name: GET_ORDERS_EXCHANGE_TRACKING_FAILURE
1780Description: The exchange failed to provide a valid answer to the tracking request, thus those details are not in the response.
1781HttpStatus: 200
1782
1783Value: 2904
1784Name: GET_ORDERS_DB_STORE_TRACKING_FAILURE
1785Description: The merchant backend failed to persist tracking details in its database, thus those details are not in the response.
1786HttpStatus: 200
1787
1788Value: 2905
1789Name: GET_ORDERS_AMOUNT_ARITHMETIC_FAILURE
1790Description: The merchant backend encountered a failure in computing the deposit total.
1791HttpStatus: 200
1792
1793Value: 2906
1794Name: GET_ORDERS_EXCHANGE_LOOKUP_FAILURE
1795Description: The merchant backend failed trying to contact the exchange for tracking details, thus those details are not in the response.
1796HttpStatus: 200
1797
1798Value: 2907
1799Name: GET_ORDERS_EXCHANGE_REQUEST_FAILURE
1800Description: The merchant backend failed to construct the request for tracking to the exchange, thus tracking details are not in the response.
1801HttpStatus: 200
1802
1803Value: 2908
1804Name: GET_ORDERS_DB_FETCH_CONTRACT_TERMS_ERROR
1805Description: The merchant backend had a database failure trying to find information about the contract of the order.
1806HttpStatus: 500
1807
1808Value: 2909
1809Name: GET_ORDERS_ORDER_NOT_FOUND
1810Description: The merchant backend could not find an order with the given identifier.
1811HttpStatus: 404
1812
1813Value: 2910
1814Name: GET_ORDERS_FAILED_COMPUTE_PROPOSAL_HASH
1815Description: The merchant backend could not compute the hash of the proposal.
1816HttpStatus: 500
1770 1817
1771Value: 2911 1818Value: 2911
1819Name: GET_ORDERS_DB_FETCH_PAYMENT_STATUS
1820Description: The merchant backend could not fetch the payment status from its database.
1821HttpStatus: 500
1822
1823Value: 2912
1824Name: GET_ORDERS_DB_FETCH_TRANSACTION_ERROR
1825Description: The merchant backend had an error looking up information in its database.
1826HttpStatus: 500
1827
1828Value: 2913
1829Name: GET_ORDERS_CONTRACT_CONTENT_INVALID
1830Description: The contract obtained from the merchant backend was malformed.
1831HttpStatus: 500
1832
1833Value: 2914
1772Name: CHECK_PAYMENT_DB_FETCH_CONTRACT_TERMS_ERROR 1834Name: CHECK_PAYMENT_DB_FETCH_CONTRACT_TERMS_ERROR
1773Description: We failed to contract terms from our merchant database. 1835Description: We failed to contract terms from our merchant database.
1774HttpStatus: 500 1836HttpStatus: 500
1775 1837
1776Value: 2912 1838Value: 2915
1777Name: CHECK_PAYMENT_DB_FETCH_ORDER_ERROR 1839Name: CHECK_PAYMENT_DB_FETCH_ORDER_ERROR
1778Description: We failed to contract terms from our merchant database. 1840Description: We failed to contract terms from our merchant database.
1779HttpStatus: 500 1841HttpStatus: 500
1780 1842
1781Value: 2913 1843Value: 2916
1782Name: CHECK_PAYMENT_ORDER_ID_UNKNOWN 1844Name: CHECK_PAYMENT_ORDER_ID_UNKNOWN
1783Description: The order id we're checking is unknown, likely the frontend did not create the order first. 1845Description: The order id we're checking is unknown, likely the frontend did not create the order first.
1784HttpStatus: 0 1846HttpStatus: 0
1785 1847
1786Value: 2914 1848Value: 2917
1787Name: CHECK_PAYMENT_FAILED_COMPUTE_PROPOSAL_HASH 1849Name: CHECK_PAYMENT_FAILED_COMPUTE_PROPOSAL_HASH
1788Description: Failed computing a hash code (likely server out-of-memory). 1850Description: Failed computing a hash code (likely server out-of-memory).
1789HttpStatus: 500 1851HttpStatus: 500
1790 1852
1791Value: 2915 1853Value: 2918
1792Name: CHECK_PAYMENT_SESSION_SIGNATURE_INVALID 1854Name: CHECK_PAYMENT_SESSION_SIGNATURE_INVALID
1793Description: Signature "session_sig" failed to verify. 1855Description: Signature "session_sig" failed to verify.
1794HttpStatus: 400 1856HttpStatus: 400
1795 1857
1796Value: 2916 1858Value: 2919
1797Name: CHECK_PAYMENT_RESPONSE_MALFORMED 1859Name: CHECK_PAYMENT_RESPONSE_MALFORMED
1798Description: The response we received from the merchant is malformed. This error is generated client-side. 1860Description: The response we received from the merchant is malformed. This error is generated client-side.
1799HttpStatus: 0 1861HttpStatus: 0