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