diff options
Diffstat (limited to 'gnu-taler-error-codes/registry.rec')
-rw-r--r-- | gnu-taler-error-codes/registry.rec | 2672 |
1 files changed, 2664 insertions, 8 deletions
diff --git a/gnu-taler-error-codes/registry.rec b/gnu-taler-error-codes/registry.rec index a3c52db..9f2d195 100644 --- a/gnu-taler-error-codes/registry.rec +++ b/gnu-taler-error-codes/registry.rec | |||
@@ -8,7 +8,7 @@ | |||
8 | %constraint: ( Value < 100 ) || ( Value > 999 ) | 8 | %constraint: ( Value < 100 ) || ( Value > 999 ) |
9 | %type: Value ValueRange_t | 9 | %type: Value ValueRange_t |
10 | %mandatory: Value | 10 | %mandatory: Value |
11 | %typedef: Description_t regexp /^[abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_-][abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_\(\)\. -]*$/ | 11 | %typedef: Description_t regexp /^[abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789_-].*$/ |
12 | %type: Description Description_t | 12 | %type: Description Description_t |
13 | %mandatory: Description | 13 | %mandatory: Description |
14 | %typedef: Name_t regexp /^[ABCDEFGHIJKLMNOPQRSTUVWXYZ_][ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789]*$/ | 14 | %typedef: Name_t regexp /^[ABCDEFGHIJKLMNOPQRSTUVWXYZ_][ABCDEFGHIJKLMNOPQRSTUVWXYZ_0123456789]*$/ |
@@ -23,15 +23,2671 @@ | |||
23 | 23 | ||
24 | Value: 0 | 24 | Value: 0 |
25 | Name: NONE | 25 | Name: NONE |
26 | Description: No error (success). | 26 | Description: Special code to indicate no error (or no "code" present). |
27 | HttpStatus: 0 | 27 | HttpStatus: 0 |
28 | 28 | ||
29 | Value: 1 | 29 | Value: 1 |
30 | Name: TEST | 30 | Name: INVALID |
31 | Description: Testing | 31 | Description: Special code to indicate that a non-integer error code was returned in |
32 | HttpStatus: 200 | 32 | + the JSON response. |
33 | HttpStatus: 0 | ||
33 | 34 | ||
34 | Value: 2 | 35 | Value: 2 |
35 | Name: TEST2 | 36 | Name: INVALID_RESPONSE |
36 | Description: Invalid | 37 | Description: The response we got from the server was not even in JSON format. |
37 | HttpStatus: 199 | 38 | HttpStatus: 0 |
39 | |||
40 | Value: 3 | ||
41 | Name: NOT_IMPLEMENTED | ||
42 | Description: Generic implementation error: this function was not yet implemented. | ||
43 | HttpStatus: 0 | ||
44 | |||
45 | Value: 4 | ||
46 | Name: EXCHANGE_BAD_CONFIGURATION | ||
47 | Description: Exchange is badly configured and thus cannot operate. | ||
48 | HttpStatus: 0 | ||
49 | |||
50 | Value: 5 | ||
51 | Name: INTERNAL_INVARIANT_FAILURE | ||
52 | Description: Internal assertion error. | ||
53 | HttpStatus: 0 | ||
54 | |||
55 | Value: 6 | ||
56 | Name: TIMEOUT | ||
57 | Description: Operation timed out. | ||
58 | HttpStatus: 0 | ||
59 | |||
60 | Value: 7 | ||
61 | Name: JSON_ALLOCATION_FAILURE | ||
62 | Description: Exchange failed to allocate memory for building JSON reply. | ||
63 | HttpStatus: 0 | ||
64 | |||
65 | Value: 8 | ||
66 | Name: METHOD_INVALID | ||
67 | Description: HTTP method invalid for this URL. | ||
68 | HttpStatus: 0 | ||
69 | |||
70 | Value: 9 | ||
71 | Name: OPERATION_INVALID | ||
72 | Description: Operation specified invalid for this URL (resulting in a "NOT FOUND" | ||
73 | + for the overall response). | ||
74 | HttpStatus: 0 | ||
75 | |||
76 | Value: 10 | ||
77 | Name: ENDPOINT_UNKNOWN | ||
78 | Description: There is no endpoint defined for the URL provided by the client | ||
79 | + (returned together with a #MHD_HTTP_NOT_FOUND status code). | ||
80 | HttpStatus: 404 | ||
81 | |||
82 | Value: 11 | ||
83 | Name: URI_TOO_LONG | ||
84 | Description: The URI is longer than the longest URI the HTTP server is willing to | ||
85 | + parse. Returned together with an HTTP status code of | ||
86 | + #MHD_HTTP_URI_TOO_LONG. | ||
87 | HttpStatus: 414 | ||
88 | |||
89 | Value: 12 | ||
90 | Name: WRONG_NUMBER_OF_SEGMENTS | ||
91 | Description: The number of segments included in the URI does not match the number | ||
92 | + of segments expected by the endpoint. (returned together with a | ||
93 | + #MHD_HTTP_NOT_FOUND status code). | ||
94 | HttpStatus: 404 | ||
95 | |||
96 | Value: 13 | ||
97 | Name: HOLE_IN_WIRE_FEE_STRUCTURE | ||
98 | Description: The start and end-times in the wire fee structure leave a hole. This | ||
99 | + is not allowed. Generated as an error on the client-side. | ||
100 | HttpStatus: 0 | ||
101 | |||
102 | Value: 14 | ||
103 | Name: VERSION_MALFORMED | ||
104 | Description: The version string given does not follow the expected | ||
105 | + CURRENT:REVISION:AGE Format. Generated as an error on the client | ||
106 | + side. | ||
107 | HttpStatus: 0 | ||
108 | |||
109 | Value: 15 | ||
110 | Name: CLIENT_INTERNAL_FAILURE | ||
111 | Description: The client-side experienced an internal failure. Generated as an error | ||
112 | + on the client side. | ||
113 | HttpStatus: 0 | ||
114 | |||
115 | Value: 1001 | ||
116 | Name: DB_SETUP_FAILED | ||
117 | Description: The exchange failed to even just initialize its connection to the | ||
118 | + database. This response is provided with HTTP status code | ||
119 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
120 | HttpStatus: 500 | ||
121 | |||
122 | Value: 1002 | ||
123 | Name: DB_START_FAILED | ||
124 | Description: The exchange encountered an error event to just start the database | ||
125 | + transaction. This response is provided with HTTP status code | ||
126 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
127 | HttpStatus: 500 | ||
128 | |||
129 | Value: 1003 | ||
130 | Name: DB_COMMIT_FAILED_HARD | ||
131 | Description: The exchange encountered an error event to commit the database | ||
132 | + transaction (hard, unrecoverable error). This response is provided | ||
133 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
134 | HttpStatus: 500 | ||
135 | |||
136 | Value: 1004 | ||
137 | Name: DB_COMMIT_FAILED_ON_RETRY | ||
138 | Description: The exchange encountered an error event to commit the database | ||
139 | + transaction, even after repeatedly retrying it there was always a | ||
140 | + conflicting transaction. (This indicates a repeated serialization | ||
141 | + error; should only happen if some client maliciously tries to create | ||
142 | + conflicting concurrent transactions.) This response is provided with | ||
143 | + HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
144 | HttpStatus: 500 | ||
145 | |||
146 | Value: 1005 | ||
147 | Name: PARSER_OUT_OF_MEMORY | ||
148 | Description: The exchange had insufficient memory to parse the request. This | ||
149 | + response is provided with HTTP status code | ||
150 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
151 | HttpStatus: 500 | ||
152 | |||
153 | Value: 1006 | ||
154 | Name: JSON_INVALID | ||
155 | Description: The JSON in the client's request to the exchange was malformed. | ||
156 | + (Generic parse error). This response is provided with HTTP status code | ||
157 | + #MHD_HTTP_BAD_REQUEST. | ||
158 | HttpStatus: 400 | ||
159 | |||
160 | Value: 1007 | ||
161 | Name: JSON_INVALID_WITH_DETAILS | ||
162 | Description: The JSON in the client's request to the exchange was malformed. | ||
163 | + Details about the location of the parse error are provided. This | ||
164 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
165 | HttpStatus: 400 | ||
166 | |||
167 | Value: 1008 | ||
168 | Name: PARAMETER_MISSING | ||
169 | Description: A required parameter in the request to the exchange was missing. This | ||
170 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
171 | HttpStatus: 400 | ||
172 | |||
173 | Value: 1009 | ||
174 | Name: PARAMETER_MALFORMED | ||
175 | Description: A parameter in the request to the exchange was malformed. This | ||
176 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
177 | HttpStatus: 400 | ||
178 | |||
179 | Value: 1010 | ||
180 | Name: COIN_HISTORY_DB_ERROR_INSUFFICIENT_FUNDS | ||
181 | Description: The exchange failed to obtain the transaction history of the given | ||
182 | + coin from the database while generating an insufficient funds errors. | ||
183 | + This can happen during /deposit or /recoup requests. This response is | ||
184 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
185 | HttpStatus: 500 | ||
186 | |||
187 | Value: 1011 | ||
188 | Name: INTERNAL_LOGIC_ERROR | ||
189 | Description: Internal logic error. Some server-side function failed that really | ||
190 | + should not. This response is provided with HTTP status code | ||
191 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
192 | HttpStatus: 500 | ||
193 | |||
194 | Value: 1012 | ||
195 | Name: PAYTO_WRONG_METHOD | ||
196 | Description: The method specified in a payto:// URI is not one we expected. | ||
197 | HttpStatus: 0 | ||
198 | |||
199 | Value: 1013 | ||
200 | Name: PAYTO_MALFORMED | ||
201 | Description: The payto:// URI is malformed. | ||
202 | HttpStatus: 0 | ||
203 | |||
204 | Value: 1014 | ||
205 | Name: DB_COIN_HISTORY_STORE_ERROR | ||
206 | Description: We failed to update the database of known coins. | ||
207 | HttpStatus: 0 | ||
208 | |||
209 | Value: 1050 | ||
210 | Name: COINS_INVALID_COIN_PUB | ||
211 | Description: The public key of given to a /coins/ handler was malformed. | ||
212 | HttpStatus: 0 | ||
213 | |||
214 | Value: 1051 | ||
215 | Name: RESERVES_INVALID_RESERVE_PUB | ||
216 | Description: The reserve key of given to a /reserves/ handler was malformed. | ||
217 | HttpStatus: 0 | ||
218 | |||
219 | Value: 1052 | ||
220 | Name: TRANSFERS_INVALID_WTID | ||
221 | Description: The public key of given to a /transfers/ handler was malformed. | ||
222 | HttpStatus: 0 | ||
223 | |||
224 | Value: 1053 | ||
225 | Name: DEPOSITS_INVALID_H_WIRE | ||
226 | Description: The wire hash of given to a /deposits/ handler was malformed. | ||
227 | HttpStatus: 0 | ||
228 | |||
229 | Value: 1054 | ||
230 | Name: DEPOSITS_INVALID_MERCHANT_PUB | ||
231 | Description: The merchant key of given to a /deposits/ handler was malformed. | ||
232 | HttpStatus: 0 | ||
233 | |||
234 | Value: 1055 | ||
235 | Name: DEPOSITS_INVALID_H_CONTRACT_TERMS | ||
236 | Description: The hash of the contract terms given to a /deposits/ handler was | ||
237 | + malformed. | ||
238 | HttpStatus: 0 | ||
239 | |||
240 | Value: 1056 | ||
241 | Name: DEPOSITS_INVALID_COIN_PUB | ||
242 | Description: The coin public key of given to a /deposits/ handler was malformed. | ||
243 | HttpStatus: 0 | ||
244 | |||
245 | Value: 1057 | ||
246 | Name: DEPOSITS_INVALID_BODY_BY_EXCHANGE | ||
247 | Description: The body returned by the exchange for a /deposits/ request was | ||
248 | + malformed. Error created client-side. | ||
249 | HttpStatus: 0 | ||
250 | |||
251 | Value: 1058 | ||
252 | Name: DEPOSITS_INVALID_SIGNATURE_BY_EXCHANGE | ||
253 | Description: The signature returned by the exchange in a /deposits/ request was | ||
254 | + malformed. Error created client-side. | ||
255 | HttpStatus: 0 | ||
256 | |||
257 | Value: 1100 | ||
258 | Name: WITHDRAW_INSUFFICIENT_FUNDS | ||
259 | Description: The given reserve does not have sufficient funds to admit the | ||
260 | + requested withdraw operation at this time. The response includes the | ||
261 | + current "balance" of the reserve as well as the transaction "history" | ||
262 | + that lead to this balance. This response is provided with HTTP status | ||
263 | + code #MHD_HTTP_CONFLICT. | ||
264 | HttpStatus: 409 | ||
265 | |||
266 | Value: 1101 | ||
267 | Name: WITHDRAW_RESERVE_UNKNOWN | ||
268 | Description: The exchange has no information about the "reserve_pub" that was | ||
269 | + given. This response is provided with HTTP status code | ||
270 | + #MHD_HTTP_NOT_FOUND. | ||
271 | HttpStatus: 404 | ||
272 | |||
273 | Value: 1102 | ||
274 | Name: WITHDRAW_AMOUNT_FEE_OVERFLOW | ||
275 | Description: The amount to withdraw together with the fee exceeds the numeric range | ||
276 | + for Taler amounts. This is not a client failure, as the coin value | ||
277 | + and fees come from the exchange's configuration. This response is | ||
278 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
279 | HttpStatus: 500 | ||
280 | |||
281 | Value: 1103 | ||
282 | Name: AMOUNT_DEPOSITS_OVERFLOW | ||
283 | Description: All of the deposited amounts into this reserve total up to a value | ||
284 | + that is too big for the numeric range for Taler amounts. This is not a | ||
285 | + client failure, as the transaction history comes from the exchange's | ||
286 | + configuration. This response is provided with HTTP status code | ||
287 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
288 | HttpStatus: 500 | ||
289 | |||
290 | Value: 1104 | ||
291 | Name: WITHDRAW_HISTORIC_DENOMINATION_KEY_NOT_FOUND | ||
292 | Description: For one of the historic withdrawals from this reserve, the exchange | ||
293 | + could not find the denomination key. This is not a client failure, as | ||
294 | + the transaction history comes from the exchange's configuration. This | ||
295 | + response is provided with HTTP status code | ||
296 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
297 | HttpStatus: 500 | ||
298 | |||
299 | Value: 1105 | ||
300 | Name: WITHDRAW_AMOUNT_WITHDRAWALS_OVERFLOW | ||
301 | Description: All of the withdrawals from reserve total up to a value that is too | ||
302 | + big for the numeric range for Taler amounts. This is not a client | ||
303 | + failure, as the transaction history comes from the exchange's | ||
304 | + configuration. This response is provided with HTTP status code | ||
305 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
306 | HttpStatus: 500 | ||
307 | |||
308 | Value: 1106 | ||
309 | Name: WITHDRAW_RESERVE_WITHOUT_WIRE_TRANSFER | ||
310 | Description: The exchange somehow knows about this reserve, but there seem to have | ||
311 | + been no wire transfers made. This is not a client failure, as this is | ||
312 | + a database consistency issue of the exchange. This response is | ||
313 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
314 | HttpStatus: 500 | ||
315 | |||
316 | Value: 1107 | ||
317 | Name: WITHDRAW_SIGNATURE_FAILED | ||
318 | Description: The exchange failed to create the signature using the denomination | ||
319 | + key. This response is provided with HTTP status code | ||
320 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
321 | HttpStatus: 500 | ||
322 | |||
323 | Value: 1108 | ||
324 | Name: WITHDRAW_DB_STORE_ERROR | ||
325 | Description: The exchange failed to store the withdraw operation in its database. | ||
326 | + This response is provided with HTTP status code | ||
327 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
328 | HttpStatus: 500 | ||
329 | |||
330 | Value: 1109 | ||
331 | Name: WITHDRAW_DB_FETCH_ERROR | ||
332 | Description: The exchange failed to check against historic withdraw data from | ||
333 | + database (as part of ensuring the idempotency of the operation). This | ||
334 | + response is provided with HTTP status code | ||
335 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
336 | HttpStatus: 500 | ||
337 | |||
338 | Value: 1110 | ||
339 | Name: WITHDRAW_DENOMINATION_KEY_NOT_FOUND | ||
340 | Description: The exchange is not aware of the denomination key the wallet requested | ||
341 | + for the withdrawal. This response is provided with HTTP status code | ||
342 | + #MHD_HTTP_NOT_FOUND. | ||
343 | HttpStatus: 404 | ||
344 | |||
345 | Value: 1111 | ||
346 | Name: WITHDRAW_RESERVE_SIGNATURE_INVALID | ||
347 | Description: The signature of the reserve is not valid. This response is provided | ||
348 | + with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
349 | HttpStatus: 400 | ||
350 | |||
351 | Value: 1112 | ||
352 | Name: WITHDRAW_HISTORY_DB_ERROR_INSUFFICIENT_FUNDS | ||
353 | Description: When computing the reserve history, we ended up with a negative | ||
354 | + overall balance, which should be impossible. This response is provided | ||
355 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
356 | HttpStatus: 500 | ||
357 | |||
358 | Value: 1113 | ||
359 | Name: WITHDRAW_RESERVE_HISTORY_IMPOSSIBLE | ||
360 | Description: When computing the reserve history, we ended up with a negative | ||
361 | + overall balance, which should be impossible. This response is provided | ||
362 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
363 | HttpStatus: 500 | ||
364 | |||
365 | Value: 1114 | ||
366 | Name: WITHDRAW_VALIDITY_IN_FUTURE | ||
367 | Description: Validity period of the coin to be withdrawn is in the future. | ||
368 | + Returned with an HTTP status of #MHD_HTTP_PRECONDITION_FAILED. | ||
369 | HttpStatus: 412 | ||
370 | |||
371 | Value: 1115 | ||
372 | Name: WITHDRAW_VALIDITY_IN_PAST | ||
373 | Description: Withdraw period of the coin to be withdrawn is in the past. Returned | ||
374 | + with an HTTP status of #MHD_HTTP_GONE. | ||
375 | HttpStatus: 410 | ||
376 | |||
377 | Value: 1116 | ||
378 | Name: DENOMINATION_KEY_LOST | ||
379 | Description: Withdraw period of the coin to be withdrawn is in the past. Returned | ||
380 | + with an HTTP status of #MHD_HTTP_GONE. | ||
381 | HttpStatus: 410 | ||
382 | |||
383 | Value: 1117 | ||
384 | Name: WITHDRAW_RESERVE_BALANCE_CORRUPT | ||
385 | Description: The exchange's database entry with the reserve balance summary is | ||
386 | + inconsistent with its own history of the reserve. Returned with an | ||
387 | + HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
388 | HttpStatus: 500 | ||
389 | |||
390 | Value: 1118 | ||
391 | Name: WITHDRAW_REPLY_MALFORMED | ||
392 | Description: The exchange responded with a reply that did not satsify the protocol. | ||
393 | + This error is not used in the protocol but created client-side. | ||
394 | HttpStatus: 0 | ||
395 | |||
396 | Value: 1119 | ||
397 | Name: WITHDRAW_UNBLIND_FAILURE | ||
398 | Description: The client failed to unblind the blind signature. This error is not | ||
399 | + used in the protocol but created client-side. | ||
400 | HttpStatus: 0 | ||
401 | |||
402 | Value: 1150 | ||
403 | Name: RESERVE_STATUS_DB_ERROR | ||
404 | Description: The exchange failed to obtain the transaction history of the given | ||
405 | + reserve from the database. This response is provided with HTTP status | ||
406 | + code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
407 | HttpStatus: 500 | ||
408 | |||
409 | Value: 1151 | ||
410 | Name: RESERVE_STATUS_UNKNOWN | ||
411 | Description: The reserve status was requested using a unknown key, to be returned | ||
412 | + with 404 Not Found. | ||
413 | HttpStatus: 0 | ||
414 | |||
415 | Value: 1152 | ||
416 | Name: RESERVE_STATUS_REPLY_MALFORMED | ||
417 | Description: The exchange responded with a reply that did not satsify the protocol. | ||
418 | + This error is not used in the protocol but created client-side. | ||
419 | HttpStatus: 0 | ||
420 | |||
421 | Value: 1200 | ||
422 | Name: DEPOSIT_INSUFFICIENT_FUNDS | ||
423 | Description: The respective coin did not have sufficient residual value for the | ||
424 | + /deposit operation (i.e. due to double spending). The "history" in the | ||
425 | + respose provides the transaction history of the coin proving this | ||
426 | + fact. This response is provided with HTTP status code | ||
427 | + #MHD_HTTP_CONFLICT. | ||
428 | HttpStatus: 409 | ||
429 | |||
430 | Value: 1201 | ||
431 | Name: DEPOSIT_HISTORY_DB_ERROR | ||
432 | Description: The exchange failed to obtain the transaction history of the given | ||
433 | + coin from the database (this does not happen merely because the coin | ||
434 | + is seen by the exchange for the first time). This response is provided | ||
435 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
436 | HttpStatus: 500 | ||
437 | |||
438 | Value: 1202 | ||
439 | Name: DEPOSIT_STORE_DB_ERROR | ||
440 | Description: The exchange failed to store the /depost information in the database. | ||
441 | + This response is provided with HTTP status code | ||
442 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
443 | HttpStatus: 500 | ||
444 | |||
445 | Value: 1203 | ||
446 | Name: DEPOSIT_DB_DENOMINATION_KEY_UNKNOWN | ||
447 | Description: The exchange database is unaware of the denomination key that signed | ||
448 | + the coin (however, the exchange process is; this is not supposed to | ||
449 | + happen; it can happen if someone decides to purge the DB behind the | ||
450 | + back of the exchange process). Hence the deposit is being refused. | ||
451 | + This response is provided with HTTP status code | ||
452 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
453 | HttpStatus: 500 | ||
454 | |||
455 | Value: 1204 | ||
456 | Name: DEPOSIT_DENOMINATION_KEY_UNKNOWN | ||
457 | Description: The exchange was trying to lookup the denomination key for the purpose | ||
458 | + of a DEPOSIT operation. However, the denomination key is unavailable | ||
459 | + for that purpose. This can be because it is entirely unknown to the | ||
460 | + exchange or not in the validity period for the deposit operation. | ||
461 | + Hence the deposit is being refused. This response is provided with | ||
462 | + HTTP status code #MHD_HTTP_NOT_FOUND. | ||
463 | HttpStatus: 404 | ||
464 | |||
465 | Value: 1205 | ||
466 | Name: DEPOSIT_COIN_SIGNATURE_INVALID | ||
467 | Description: The signature made by the coin over the deposit permission is not | ||
468 | + valid. This response is provided with HTTP status code | ||
469 | + #MHD_HTTP_BAD_REQUEST. | ||
470 | HttpStatus: 400 | ||
471 | |||
472 | Value: 1206 | ||
473 | Name: DEPOSIT_DENOMINATION_SIGNATURE_INVALID | ||
474 | Description: The signature of the denomination key over the coin is not valid. This | ||
475 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
476 | HttpStatus: 400 | ||
477 | |||
478 | Value: 1207 | ||
479 | Name: DEPOSIT_NEGATIVE_VALUE_AFTER_FEE | ||
480 | Description: The stated value of the coin after the deposit fee is subtracted would | ||
481 | + be negative. This response is provided with HTTP status code | ||
482 | + #MHD_HTTP_BAD_REQUEST. | ||
483 | HttpStatus: 400 | ||
484 | |||
485 | Value: 1208 | ||
486 | Name: DEPOSIT_REFUND_DEADLINE_AFTER_WIRE_DEADLINE | ||
487 | Description: The stated refund deadline is after the wire deadline. This response | ||
488 | + is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
489 | HttpStatus: 400 | ||
490 | |||
491 | Value: 1209 | ||
492 | Name: DEPOSIT_INVALID_WIRE_FORMAT_TYPE | ||
493 | Description: The exchange does not recognize the validity of or support the given | ||
494 | + wire format type. This response is provided with HTTP status code | ||
495 | + #MHD_HTTP_BAD_REQUEST. | ||
496 | HttpStatus: 400 | ||
497 | |||
498 | Value: 1210 | ||
499 | Name: DEPOSIT_INVALID_WIRE_FORMAT_JSON | ||
500 | Description: The exchange failed to canonicalize and hash the given wire format. | ||
501 | + For example, the merchant failed to provide the "salt" or a valid | ||
502 | + payto:// URI in the wire details. Note that while the exchange will | ||
503 | + do some basic sanity checking on the wire details, it cannot warrant | ||
504 | + that the banking system will ultimately be able to route to the | ||
505 | + specified address, even if this check passed. This response is | ||
506 | + provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
507 | HttpStatus: 400 | ||
508 | |||
509 | Value: 1211 | ||
510 | Name: DEPOSIT_INVALID_WIRE_FORMAT_CONTRACT_HASH_CONFLICT | ||
511 | Description: The hash of the given wire address does not match the hash specified | ||
512 | + in the proposal data. This response is provided with HTTP status code | ||
513 | + #MHD_HTTP_BAD_REQUEST. | ||
514 | HttpStatus: 400 | ||
515 | |||
516 | Value: 1213 | ||
517 | Name: DEPOSIT_INVALID_WIRE_FORMAT_ACCOUNT_NUMBER | ||
518 | Description: The exchange detected that the given account number is invalid for the | ||
519 | + selected wire format type. This response is provided with HTTP status | ||
520 | + code #MHD_HTTP_BAD_REQUEST. | ||
521 | HttpStatus: 400 | ||
522 | |||
523 | Value: 1218 | ||
524 | Name: DEPOSIT_INVALID_TIMESTAMP | ||
525 | Description: Timestamp included in deposit permission is intolerably far off with | ||
526 | + respect to the clock of the exchange. | ||
527 | HttpStatus: 0 | ||
528 | |||
529 | Value: 1219 | ||
530 | Name: DEPOSIT_DENOMINATION_VALIDITY_IN_FUTURE | ||
531 | Description: Validity period of the denomination key is in the future. Returned | ||
532 | + with an HTTP status of #MHD_HTTP_PRECONDITION_FAILED. | ||
533 | HttpStatus: 412 | ||
534 | |||
535 | Value: 1220 | ||
536 | Name: DEPOSIT_DENOMINATION_EXPIRED | ||
537 | Description: Denomination key of the coin is past the deposit deadline. Returned | ||
538 | + with an HTTP status of #MHD_HTTP_GONE. | ||
539 | HttpStatus: 410 | ||
540 | |||
541 | Value: 1221 | ||
542 | Name: DEPOSIT_INVALID_SIGNATURE_BY_EXCHANGE | ||
543 | Description: The signature provided by the exchange is not valid. Error created | ||
544 | + client-side. | ||
545 | HttpStatus: 0 | ||
546 | |||
547 | Value: 1222 | ||
548 | Name: DEPOSIT_CURRENCY_MISMATCH | ||
549 | Description: The currency specified for the deposit is different from the currency | ||
550 | + of the coin. This response is provided with HTTP status code | ||
551 | + #MHD_HTTP_PRECONDITION_FAILED. | ||
552 | HttpStatus: 412 | ||
553 | |||
554 | Value: 1300 | ||
555 | Name: MELT_INSUFFICIENT_FUNDS | ||
556 | Description: The respective coin did not have sufficient residual value for the | ||
557 | + /refresh/melt operation. The "history" in this response provdes the | ||
558 | + "residual_value" of the coin, which may be less than its | ||
559 | + "original_value". This response is provided with HTTP status code | ||
560 | + #MHD_HTTP_CONFLICT. | ||
561 | HttpStatus: 409 | ||
562 | |||
563 | Value: 1301 | ||
564 | Name: MELT_DENOMINATION_KEY_NOT_FOUND | ||
565 | Description: The respective coin did not have sufficient residual value for the | ||
566 | + /refresh/melt operation. The "history" in this response provdes the | ||
567 | + "residual_value" of the coin, which may be less than its | ||
568 | + "original_value". This response is provided with HTTP status code | ||
569 | + #MHD_HTTP_CONFLICT. | ||
570 | HttpStatus: 409 | ||
571 | |||
572 | Value: 1302 | ||
573 | Name: MELT_COIN_HISTORY_COMPUTATION_FAILED | ||
574 | Description: The exchange had an internal error reconstructing the transaction | ||
575 | + history of the coin that was being melted. This response is provided | ||
576 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
577 | HttpStatus: 500 | ||
578 | |||
579 | Value: 1303 | ||
580 | Name: MELT_DB_FETCH_ERROR | ||
581 | Description: The exchange failed to check against historic melt data from database | ||
582 | + (as part of ensuring the idempotency of the operation). This response | ||
583 | + is provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
584 | HttpStatus: 500 | ||
585 | |||
586 | Value: 1304 | ||
587 | Name: MELT_DB_STORE_SESSION_ERROR | ||
588 | Description: The exchange failed to store session data in the database. This | ||
589 | + response is provided with HTTP status code | ||
590 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
591 | HttpStatus: 500 | ||
592 | |||
593 | Value: 1305 | ||
594 | Name: MELT_FEES_EXCEED_CONTRIBUTION | ||
595 | Description: The exchange encountered melt fees exceeding the melted coin's | ||
596 | + contribution. This response is provided with HTTP status code | ||
597 | + #MHD_HTTP_BAD_REQUEST. | ||
598 | HttpStatus: 400 | ||
599 | |||
600 | Value: 1306 | ||
601 | Name: MELT_DENOMINATION_SIGNATURE_INVALID | ||
602 | Description: The denomination key signature on the melted coin is invalid. This | ||
603 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
604 | HttpStatus: 400 | ||
605 | |||
606 | Value: 1307 | ||
607 | Name: MELT_COIN_SIGNATURE_INVALID | ||
608 | Description: The signature made with the coin to be melted is invalid. This | ||
609 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
610 | HttpStatus: 400 | ||
611 | |||
612 | Value: 1308 | ||
613 | Name: MELT_HISTORY_DB_ERROR_INSUFFICIENT_FUNDS | ||
614 | Description: The exchange failed to obtain the transaction history of the given | ||
615 | + coin from the database while generating an insufficient funds errors. | ||
616 | + This response is provided with HTTP status code | ||
617 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
618 | HttpStatus: 500 | ||
619 | |||
620 | Value: 1309 | ||
621 | Name: MELT_COIN_EXPIRED_NO_ZOMBIE | ||
622 | Description: The denomination of the given coin has past its expiration date and it | ||
623 | + is also not a valid zombie (that is, was not refreshed with the fresh | ||
624 | + coin being subjected to recoup). | ||
625 | HttpStatus: 0 | ||
626 | |||
627 | Value: 1310 | ||
628 | Name: MELT_INVALID_SIGNATURE_BY_EXCHANGE | ||
629 | Description: The signature returned by the exchange in a melt request was | ||
630 | + malformed. Error created client-side. | ||
631 | HttpStatus: 0 | ||
632 | |||
633 | Value: 1311 | ||
634 | Name: MELT_CURRENCY_MISMATCH | ||
635 | Description: The currency specified for the melt amount is different from the | ||
636 | + currency of the coin. This response is provided with HTTP status code | ||
637 | + #MHD_HTTP_PRECONDITION_FAILED. | ||
638 | HttpStatus: 412 | ||
639 | |||
640 | Value: 1351 | ||
641 | Name: REFRESH_RECOUP_DENOMINATION_KEY_NOT_FOUND | ||
642 | Description: The exchange is unaware of the denomination key that was used to sign | ||
643 | + the melted zombie coin. This response is provided with HTTP status | ||
644 | + code #MHD_HTTP_NOT_FOUND. | ||
645 | HttpStatus: 404 | ||
646 | |||
647 | Value: 1352 | ||
648 | Name: REFRESH_RECOUP_DENOMINATION_VALIDITY_IN_FUTURE | ||
649 | Description: Validity period of the denomination key is in the future. Returned | ||
650 | + with an HTTP status of #MHD_HTTP_PRECONDITION_FAILED. | ||
651 | HttpStatus: 412 | ||
652 | |||
653 | Value: 1353 | ||
654 | Name: REFRESH_RECOUP_DENOMINATION_EXPIRED | ||
655 | Description: Denomination key of the coin is past the deposit deadline. Returned | ||
656 | + with an HTTP status of #MHD_HTTP_GONE. | ||
657 | HttpStatus: 410 | ||
658 | |||
659 | Value: 1354 | ||
660 | Name: REFRESH_ZOMBIE_DENOMINATION_EXPIRED | ||
661 | Description: Denomination key of the coin is past the deposit deadline. Returned | ||
662 | + with an HTTP status of #MHD_HTTP_GONE. | ||
663 | HttpStatus: 410 | ||
664 | |||
665 | Value: 1370 | ||
666 | Name: REVEAL_COMMITMENT_VIOLATION | ||
667 | Description: The provided transfer keys do not match up with the original | ||
668 | + commitment. Information about the original commitment is included in | ||
669 | + the response. This response is provided with HTTP status code | ||
670 | + #MHD_HTTP_CONFLICT. | ||
671 | HttpStatus: 409 | ||
672 | |||
673 | Value: 1371 | ||
674 | Name: REVEAL_SIGNING_ERROR | ||
675 | Description: Failed to produce the blinded signatures over the coins to be | ||
676 | + returned. This response is provided with HTTP status code | ||
677 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
678 | HttpStatus: 500 | ||
679 | |||
680 | Value: 1372 | ||
681 | Name: REVEAL_SESSION_UNKNOWN | ||
682 | Description: The exchange is unaware of the refresh session specified in the | ||
683 | + request. This response is provided with HTTP status code | ||
684 | + #MHD_HTTP_BAD_REQUEST. | ||
685 | HttpStatus: 400 | ||
686 | |||
687 | Value: 1373 | ||
688 | Name: REVEAL_DB_FETCH_SESSION_ERROR | ||
689 | Description: The exchange failed to retrieve valid session data from the database. | ||
690 | + This response is provided with HTTP status code | ||
691 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
692 | HttpStatus: 500 | ||
693 | |||
694 | Value: 1374 | ||
695 | Name: REVEAL_DB_FETCH_REVEAL_ERROR | ||
696 | Description: The exchange failed to retrieve previously revealed data from the | ||
697 | + database. This response is provided with HTTP status code | ||
698 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
699 | HttpStatus: 500 | ||
700 | |||
701 | Value: 1375 | ||
702 | Name: REVEAL_DB_COMMIT_ERROR | ||
703 | Description: The exchange failed to retrieve commitment data from the database. | ||
704 | + This response is provided with HTTP status code | ||
705 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
706 | HttpStatus: 500 | ||
707 | |||
708 | Value: 1376 | ||
709 | Name: REVEAL_CNC_TRANSFER_ARRAY_SIZE_INVALID | ||
710 | Description: The size of the cut-and-choose dimension of the private transfer keys | ||
711 | + request does not match #TALER_CNC_KAPPA - 1. This response is provided | ||
712 | + with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
713 | HttpStatus: 400 | ||
714 | |||
715 | Value: 1377 | ||
716 | Name: REVEAL_NEW_DENOMS_ARRAY_SIZE_EXCESSIVE | ||
717 | Description: The number of coins to be created in refresh exceeds the limits of the | ||
718 | + exchange. private transfer keys request does not match | ||
719 | + #TALER_CNC_KAPPA - 1. This response is provided with HTTP status code | ||
720 | + #MHD_HTTP_BAD_REQUEST. | ||
721 | HttpStatus: 400 | ||
722 | |||
723 | Value: 1378 | ||
724 | Name: REVEAL_NEW_DENOMS_ARRAY_SIZE_MISMATCH | ||
725 | Description: The number of envelopes given does not match the number of | ||
726 | + denomination keys given. This response is provided with HTTP status | ||
727 | + code #MHD_HTTP_BAD_REQUEST. | ||
728 | HttpStatus: 400 | ||
729 | |||
730 | Value: 1379 | ||
731 | Name: REVEAL_COST_CALCULATION_OVERFLOW | ||
732 | Description: The exchange encountered a numeric overflow totaling up the cost for | ||
733 | + the refresh operation. This response is provided with HTTP status | ||
734 | + code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
735 | HttpStatus: 500 | ||
736 | |||
737 | Value: 1380 | ||
738 | Name: REVEAL_AMOUNT_INSUFFICIENT | ||
739 | Description: The exchange's cost calculation shows that the melt amount is below | ||
740 | + the costs of the transaction. This response is provided with HTTP | ||
741 | + status code #MHD_HTTP_BAD_REQUEST. | ||
742 | HttpStatus: 400 | ||
743 | |||
744 | Value: 1381 | ||
745 | Name: REVEAL_FRESH_DENOMINATION_KEY_NOT_FOUND | ||
746 | Description: The exchange is unaware of the denomination key that was requested for | ||
747 | + one of the fresh coins. This response is provided with HTTP status | ||
748 | + code #MHD_HTTP_BAD_REQUEST. | ||
749 | HttpStatus: 400 | ||
750 | |||
751 | Value: 1382 | ||
752 | Name: REVEAL_LINK_SIGNATURE_INVALID | ||
753 | Description: The signature made with the coin over the link data is invalid. This | ||
754 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
755 | HttpStatus: 400 | ||
756 | |||
757 | Value: 1383 | ||
758 | Name: REVEAL_KEYS_MISSING | ||
759 | Description: The exchange failed to generate the signature as it could not find the | ||
760 | + signing key for the denomination. This response is provided with HTTP | ||
761 | + status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
762 | HttpStatus: 500 | ||
763 | |||
764 | Value: 1384 | ||
765 | Name: REVEAL_INVALID_RCH | ||
766 | Description: The refresh session hash given to a /refreshes/ handler was malformed. | ||
767 | HttpStatus: 0 | ||
768 | |||
769 | Value: 1385 | ||
770 | Name: REVEAL_REPLY_MALFORMED | ||
771 | Description: The exchange responded with a reply that did not satsify the protocol. | ||
772 | + This error is not used in the protocol but created client-side. | ||
773 | HttpStatus: 0 | ||
774 | |||
775 | Value: 1400 | ||
776 | Name: LINK_COIN_UNKNOWN | ||
777 | Description: The coin specified in the link request is unknown to the exchange. | ||
778 | + This response is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
779 | HttpStatus: 404 | ||
780 | |||
781 | Value: 1401 | ||
782 | Name: LINK_REPLY_MALFORMED | ||
783 | Description: The exchange responded with a reply that did not satsify the protocol. | ||
784 | + This error is not used in the protocol but created client-side. | ||
785 | HttpStatus: 0 | ||
786 | |||
787 | Value: 1500 | ||
788 | Name: REFUND_COIN_NOT_FOUND | ||
789 | Description: The exchange knows literally nothing about the coin we were asked to | ||
790 | + refund. But without a transaction history, we cannot issue a refund. | ||
791 | + This is kind-of OK, the owner should just refresh it directly without | ||
792 | + executing the refund. This response is provided with HTTP status code | ||
793 | + #MHD_HTTP_NOT_FOUND. | ||
794 | HttpStatus: 404 | ||
795 | |||
796 | Value: 1501 | ||
797 | Name: REFUND_CONFLICT | ||
798 | Description: We could not process the refund request as the coin's transaction | ||
799 | + history does not permit the requested refund at this time. The | ||
800 | + "history" in the response proves this. This response is provided with | ||
801 | + HTTP status code #MHD_HTTP_CONFLICT. | ||
802 | HttpStatus: 409 | ||
803 | |||
804 | Value: 1503 | ||
805 | Name: REFUND_DEPOSIT_NOT_FOUND | ||
806 | Description: The exchange knows about the coin we were asked to refund, but not | ||
807 | + about the specific /deposit operation. Hence, we cannot issue a | ||
808 | + refund (as we do not know if this merchant public key is authorized to | ||
809 | + do a refund). This response is provided with HTTP status code | ||
810 | + #MHD_HTTP_NOT_FOUND. | ||
811 | HttpStatus: 404 | ||
812 | |||
813 | Value: 1504 | ||
814 | Name: REFUND_CURRENCY_MISMATCH | ||
815 | Description: The currency specified for the refund is different from the currency | ||
816 | + of the coin. This response is provided with HTTP status code | ||
817 | + #MHD_HTTP_BAD_REQUEST. | ||
818 | HttpStatus: 400 | ||
819 | |||
820 | Value: 1505 | ||
821 | Name: REFUND_DB_INCONSISTENT | ||
822 | Description: When we tried to check if we already paid out the coin, the exchange's | ||
823 | + database suddenly disagreed with data it previously provided (internal | ||
824 | + inconsistency). This response is provided with HTTP status code | ||
825 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
826 | HttpStatus: 500 | ||
827 | |||
828 | Value: 1506 | ||
829 | Name: REFUND_MERCHANT_ALREADY_PAID | ||
830 | Description: The exchange can no longer refund the customer/coin as the money was | ||
831 | + already transferred (paid out) to the merchant. (It should be past the | ||
832 | + refund deadline.) This response is provided with HTTP status code | ||
833 | + #MHD_HTTP_GONE. | ||
834 | HttpStatus: 410 | ||
835 | |||
836 | Value: 1507 | ||
837 | Name: REFUND_INSUFFICIENT_FUNDS | ||
838 | Description: The amount the exchange was asked to refund exceeds (with fees) the | ||
839 | + total amount of the deposit (including fees). This response is | ||
840 | + provided with HTTP status code #MHD_HTTP_PRECONDITION_FAILED. | ||
841 | HttpStatus: 412 | ||
842 | |||
843 | Value: 1508 | ||
844 | Name: REFUND_DENOMINATION_KEY_NOT_FOUND | ||
845 | Description: The exchange failed to recover information about the denomination key | ||
846 | + of the refunded coin (even though it recognizes the key). Hence it | ||
847 | + could not check the fee strucutre. This response is provided with HTTP | ||
848 | + status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
849 | HttpStatus: 500 | ||
850 | |||
851 | Value: 1509 | ||
852 | Name: REFUND_FEE_TOO_LOW | ||
853 | Description: The refund fee specified for the request is lower than the refund fee | ||
854 | + charged by the exchange for the given denomination key of the refunded | ||
855 | + coin. This response is provided with HTTP status code | ||
856 | + #MHD_HTTP_BAD_REQUEST. | ||
857 | HttpStatus: 400 | ||
858 | |||
859 | Value: 1510 | ||
860 | Name: REFUND_STORE_DB_ERROR | ||
861 | Description: The exchange failed to store the refund information to its database. | ||
862 | + This response is provided with HTTP status code | ||
863 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
864 | HttpStatus: 500 | ||
865 | |||
866 | Value: 1511 | ||
867 | Name: REFUND_FEE_CURRENCY_MISMATCH | ||
868 | Description: The refund fee is specified in a different currency than the refund | ||
869 | + amount. This response is provided with HTTP status code | ||
870 | + #MHD_HTTP_BAD_REQUEST. | ||
871 | HttpStatus: 400 | ||
872 | |||
873 | Value: 1512 | ||
874 | Name: REFUND_FEE_ABOVE_AMOUNT | ||
875 | Description: The refunded amount is smaller than the refund fee, which would result | ||
876 | + in a negative refund. This response is provided with HTTP status code | ||
877 | + #MHD_HTTP_BAD_REQUEST. | ||
878 | HttpStatus: 400 | ||
879 | |||
880 | Value: 1513 | ||
881 | Name: REFUND_MERCHANT_SIGNATURE_INVALID | ||
882 | Description: The signature of the merchant is invalid. This response is provided | ||
883 | + with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
884 | HttpStatus: 400 | ||
885 | |||
886 | Value: 1514 | ||
887 | Name: REFUND_MERCHANT_SIGNING_FAILED | ||
888 | Description: Merchant backend failed to create the refund confirmation signature. | ||
889 | + This response is provided with HTTP status code | ||
890 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
891 | HttpStatus: 500 | ||
892 | |||
893 | Value: 1515 | ||
894 | Name: REFUND_INVALID_SIGNATURE_BY_EXCHANGE | ||
895 | Description: The signature returned by the exchange in a refund request was | ||
896 | + malformed. Error created client-side. | ||
897 | HttpStatus: 0 | ||
898 | |||
899 | Value: 1600 | ||
900 | Name: ADMIN_ADD_INCOMING_WIREFORMAT_UNSUPPORTED | ||
901 | Description: The wire format specified in the "sender_account_details" is not | ||
902 | + understood or not supported by this exchange. Returned with an HTTP | ||
903 | + status code of #MHD_HTTP_NOT_FOUND. (As we did not find an | ||
904 | + interpretation of the wire format.) | ||
905 | HttpStatus: 404 | ||
906 | |||
907 | Value: 1601 | ||
908 | Name: ADMIN_ADD_INCOMING_CURRENCY_UNSUPPORTED | ||
909 | Description: The currency specified in the "amount" parameter is not supported by | ||
910 | + this exhange. Returned with an HTTP status code of | ||
911 | + #MHD_HTTP_BAD_REQUEST. | ||
912 | HttpStatus: 400 | ||
913 | |||
914 | Value: 1602 | ||
915 | Name: ADMIN_ADD_INCOMING_DB_STORE | ||
916 | Description: The exchange failed to store information about the incoming transfer | ||
917 | + in its database. This response is provided with HTTP status code | ||
918 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
919 | HttpStatus: 500 | ||
920 | |||
921 | Value: 1700 | ||
922 | Name: TRANSFERS_GET_DB_FETCH_FAILED | ||
923 | Description: The exchange encountered an error (that is not about not finding the | ||
924 | + wire transfer) trying to lookup a wire transfer identifier in the | ||
925 | + database. This response is provided with HTTP status code | ||
926 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
927 | HttpStatus: 500 | ||
928 | |||
929 | Value: 1701 | ||
930 | Name: TRANSFERS_GET_DB_INCONSISTENT | ||
931 | Description: The exchange found internally inconsistent data when resolving a wire | ||
932 | + transfer identifier in the database. This response is provided with | ||
933 | + HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
934 | HttpStatus: 500 | ||
935 | |||
936 | Value: 1702 | ||
937 | Name: TRANSFERS_GET_WTID_NOT_FOUND | ||
938 | Description: The exchange did not find information about the specified wire | ||
939 | + transfer identifier in the database. This response is provided with | ||
940 | + HTTP status code #MHD_HTTP_NOT_FOUND. | ||
941 | HttpStatus: 404 | ||
942 | |||
943 | Value: 1703 | ||
944 | Name: TRANSFERS_GET_WIRE_FEE_NOT_FOUND | ||
945 | Description: The exchange did not find information about the wire transfer fees it | ||
946 | + charged. This response is provided with HTTP status code | ||
947 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
948 | HttpStatus: 500 | ||
949 | |||
950 | Value: 1704 | ||
951 | Name: TRANSFERS_GET_WIRE_FEE_INCONSISTENT | ||
952 | Description: The exchange found a wire fee that was above the total transfer value | ||
953 | + (and thus could not have been charged). This response is provided with | ||
954 | + HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
955 | HttpStatus: 500 | ||
956 | |||
957 | Value: 1705 | ||
958 | Name: TRANSFERS_GET_REPLY_MALFORMED | ||
959 | Description: The exchange responded with a reply that did not satsify the protocol. | ||
960 | + This error is not used in the protocol but created client-side. | ||
961 | HttpStatus: 0 | ||
962 | |||
963 | Value: 1800 | ||
964 | Name: DEPOSITS_GET_DB_FEE_INCONSISTENT | ||
965 | Description: The exchange found internally inconsistent fee data when resolving a | ||
966 | + transaction in the database. This response is provided with HTTP | ||
967 | + status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
968 | HttpStatus: 500 | ||
969 | |||
970 | Value: 1801 | ||
971 | Name: DEPOSITS_GET_DB_FETCH_FAILED | ||
972 | Description: The exchange encountered an error (that is not about not finding the | ||
973 | + transaction) trying to lookup a transaction in the database. This | ||
974 | + response is provided with HTTP status code | ||
975 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
976 | HttpStatus: 500 | ||
977 | |||
978 | Value: 1802 | ||
979 | Name: DEPOSITS_GET_NOT_FOUND | ||
980 | Description: The exchange did not find information about the specified transaction | ||
981 | + in the database. This response is provided with HTTP status code | ||
982 | + #MHD_HTTP_NOT_FOUND. | ||
983 | HttpStatus: 404 | ||
984 | |||
985 | Value: 1803 | ||
986 | Name: DEPOSITS_GET_WTID_RESOLUTION_ERROR | ||
987 | Description: The exchange failed to identify the wire transfer of the transaction | ||
988 | + (or information about the plan that it was supposed to still happen in | ||
989 | + the future). This response is provided with HTTP status code | ||
990 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
991 | HttpStatus: 500 | ||
992 | |||
993 | Value: 1804 | ||
994 | Name: DEPOSITS_GET_MERCHANT_SIGNATURE_INVALID | ||
995 | Description: The signature of the merchant is invalid. This response is provided | ||
996 | + with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
997 | HttpStatus: 400 | ||
998 | |||
999 | Value: 1850 | ||
1000 | Name: RECOUP_DENOMINATION_KEY_UNKNOWN | ||
1001 | Description: The given denomination key is not in the "recoup" set of the exchange | ||
1002 | + right now. This response is provided with an HTTP status code of | ||
1003 | + #MHD_HTTP_NOT_FOUND. | ||
1004 | HttpStatus: 404 | ||
1005 | |||
1006 | Value: 1851 | ||
1007 | Name: RECOUP_SIGNATURE_INVALID | ||
1008 | Description: The given coin signature is invalid for the request. This response is | ||
1009 | + provided with an HTTP status code of #MHD_HTTP_FORBIDDEN. | ||
1010 | HttpStatus: 403 | ||
1011 | |||
1012 | Value: 1852 | ||
1013 | Name: RECOUP_DENOMINATION_SIGNATURE_INVALID | ||
1014 | Description: The signature of the denomination key over the coin is not valid. This | ||
1015 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1016 | HttpStatus: 400 | ||
1017 | |||
1018 | Value: 1853 | ||
1019 | Name: RECOUP_DB_FETCH_FAILED | ||
1020 | Description: The exchange failed to access its own database about reserves. This | ||
1021 | + response is provided with HTTP status code | ||
1022 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1023 | HttpStatus: 500 | ||
1024 | |||
1025 | Value: 1854 | ||
1026 | Name: RECOUP_WITHDRAW_NOT_FOUND | ||
1027 | Description: The exchange could not find the corresponding withdraw operation. The | ||
1028 | + request is denied. This response is provided with an HTTP status code | ||
1029 | + of #MHD_HTTP_NOT_FOUND. | ||
1030 | HttpStatus: 404 | ||
1031 | |||
1032 | Value: 1855 | ||
1033 | Name: RECOUP_HISTORY_DB_ERROR | ||
1034 | Description: The exchange obtained an internally inconsistent transaction history | ||
1035 | + for the given coin. This response is provided with HTTP status code | ||
1036 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1037 | HttpStatus: 500 | ||
1038 | |||
1039 | Value: 1856 | ||
1040 | Name: RECOUP_DB_PUT_FAILED | ||
1041 | Description: The exchange failed to store information about the recoup to be | ||
1042 | + performed in the database. This response is provided with HTTP status | ||
1043 | + code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1044 | HttpStatus: 500 | ||
1045 | |||
1046 | Value: 1857 | ||
1047 | Name: RECOUP_COIN_BALANCE_ZERO | ||
1048 | Description: The coin's remaining balance is zero. The request is denied. This | ||
1049 | + response is provided with an HTTP status code of #MHD_HTTP_FORBIDDEN. | ||
1050 | HttpStatus: 403 | ||
1051 | |||
1052 | Value: 1858 | ||
1053 | Name: RECOUP_BLINDING_FAILED | ||
1054 | Description: The exchange failed to reproduce the coin's blinding. This response is | ||
1055 | + provided with an HTTP status code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1056 | HttpStatus: 500 | ||
1057 | |||
1058 | Value: 1859 | ||
1059 | Name: RECOUP_COIN_BALANCE_NEGATIVE | ||
1060 | Description: The coin's remaining balance is zero. The request is denied. This | ||
1061 | + response is provided with an HTTP status code of | ||
1062 | + #MHD_HTTP_INTERNAL_SERVER_ERROR | ||
1063 | HttpStatus: 500 | ||
1064 | |||
1065 | Value: 1860 | ||
1066 | Name: RECOUP_DENOMINATION_VALIDITY_IN_FUTURE | ||
1067 | Description: Validity period of the denomination key is in the future. Returned | ||
1068 | + with an HTTP status of #MHD_HTTP_PRECONDITION_FAILED. | ||
1069 | HttpStatus: 412 | ||
1070 | |||
1071 | Value: 1861 | ||
1072 | Name: RECOUP_REPLY_MALFORMED | ||
1073 | Description: The exchange responded with a reply that did not satsify the protocol. | ||
1074 | + This error is not used in the protocol but created client-side. | ||
1075 | HttpStatus: 0 | ||
1076 | |||
1077 | Value: 1900 | ||
1078 | Name: KEYS_HAVE_NOT_NUMERIC | ||
1079 | Description: The "have" parameter was not a natural number. This response is | ||
1080 | + provied with an HTTP status code of #MHD_HTTP_BAD_REQUEST. | ||
1081 | HttpStatus: 400 | ||
1082 | |||
1083 | Value: 1901 | ||
1084 | Name: KEYS_MISSING | ||
1085 | Description: We currently cannot find any keys. This response is provied with an | ||
1086 | + HTTP status code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1087 | HttpStatus: 500 | ||
1088 | |||
1089 | Value: 1902 | ||
1090 | Name: KEYS_TIMETRAVEL_FORBIDDEN | ||
1091 | Description: This exchange does not allow clients to request /keys for times other | ||
1092 | + than the current (exchange) time. This response is provied with an | ||
1093 | + HTTP status code of #MHD_HTTP_FORBIDDEN. | ||
1094 | HttpStatus: 403 | ||
1095 | |||
1096 | Value: 1903 | ||
1097 | Name: KEYS_INVALID | ||
1098 | Description: The keys response was malformed. This error is generated client-side. | ||
1099 | HttpStatus: 0 | ||
1100 | |||
1101 | Value: 2000 | ||
1102 | Name: INSTANCE_UNKNOWN | ||
1103 | Description: The backend could not find the merchant instance specified in the | ||
1104 | + request. This response is provided with HTTP status code | ||
1105 | + #MHD_HTTP_NOT_FOUND. | ||
1106 | HttpStatus: 404 | ||
1107 | |||
1108 | Value: 2002 | ||
1109 | Name: PROPOSAL_INSTANCE_CONFIGURATION_LACKS_WIRE | ||
1110 | Description: The backend lacks a wire transfer method configuration option for the | ||
1111 | + given instance. | ||
1112 | HttpStatus: 0 | ||
1113 | |||
1114 | Value: 2100 | ||
1115 | Name: PAY_MERCHANT_INVALID_RESPONSE | ||
1116 | Description: The merchant failed to provide a meaningful response to a /pay | ||
1117 | + request. This error is created client-side. | ||
1118 | HttpStatus: 0 | ||
1119 | |||
1120 | Value: 2101 | ||
1121 | Name: PAY_EXCHANGE_FAILED | ||
1122 | Description: The exchange failed to provide a meaningful response to a /deposit | ||
1123 | + request. This response is provided with HTTP status code | ||
1124 | + #MHD_HTTP_FAILED_DEPENDENCY, or #MHD_HTTP_CONFLICT in case the | ||
1125 | + exchange reports #TALER_EC_DEPOSIT_INSUFFICIENT_FUNDS (aka double | ||
1126 | + spending). | ||
1127 | HttpStatus: 424 | ||
1128 | HttpStatus: 409 | ||
1129 | |||
1130 | Value: 2102 | ||
1131 | Name: PAY_DB_STORE_PAY_ERROR | ||
1132 | Description: The merchant failed to commit the exchanges' response to a /deposit | ||
1133 | + request to its database. This response is provided with HTTP status | ||
1134 | + code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1135 | HttpStatus: 500 | ||
1136 | |||
1137 | Value: 2103 | ||
1138 | Name: PAY_EXCHANGE_REJECTED | ||
1139 | Description: The specified exchange is not supported/trusted by this merchant. | ||
1140 | + This response is provided with HTTP status code | ||
1141 | + #MHD_HTTP_PRECONDITION_FAILED. | ||
1142 | HttpStatus: 412 | ||
1143 | |||
1144 | Value: 2104 | ||
1145 | Name: PAY_DENOMINATION_KEY_NOT_FOUND | ||
1146 | Description: The denomination key used for payment is not listed among the | ||
1147 | + denomination keys of the exchange. This response is provided with | ||
1148 | + HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1149 | HttpStatus: 400 | ||
1150 | |||
1151 | Value: 2105 | ||
1152 | Name: PAY_DENOMINATION_KEY_AUDITOR_FAILURE | ||
1153 | Description: The denomination key used for payment is not audited by an auditor | ||
1154 | + approved by the merchant. This response is provided with HTTP status | ||
1155 | + code #MHD_HTTP_BAD_REQUEST. | ||
1156 | HttpStatus: 400 | ||
1157 | |||
1158 | Value: 2106 | ||
1159 | Name: PAY_AMOUNT_OVERFLOW | ||
1160 | Description: There was an integer overflow totaling up the amounts or deposit fees | ||
1161 | + in the payment. This response is provided with HTTP status code | ||
1162 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1163 | HttpStatus: 500 | ||
1164 | |||
1165 | Value: 2107 | ||
1166 | Name: PAY_FEES_EXCEED_PAYMENT | ||
1167 | Description: The deposit fees exceed the total value of the payment. This response | ||
1168 | + is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1169 | HttpStatus: 400 | ||
1170 | |||
1171 | Value: 2108 | ||
1172 | Name: PAY_PAYMENT_INSUFFICIENT_DUE_TO_FEES | ||
1173 | Description: After considering deposit and wire fees, the payment is insufficient | ||
1174 | + to satisfy the required amount for the contract. The client should | ||
1175 | + revisit the logic used to calculate fees it must cover. This response | ||
1176 | + is provided with HTTP status code #MHD_HTTP_ACCEPTED. | ||
1177 | HttpStatus: 202 | ||
1178 | |||
1179 | Value: 2109 | ||
1180 | Name: PAY_PAYMENT_INSUFFICIENT | ||
1181 | Description: Even if we do not consider deposit and wire fees, the payment is | ||
1182 | + insufficient to satisfy the required amount for the contract. This | ||
1183 | + response is provided with HTTP status code #MHD_HTTP_ACCEPTED. | ||
1184 | HttpStatus: 202 | ||
1185 | |||
1186 | Value: 2110 | ||
1187 | Name: PAY_COIN_SIGNATURE_INVALID | ||
1188 | Description: The signature over the contract of one of the coins was invalid. This | ||
1189 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1190 | HttpStatus: 400 | ||
1191 | |||
1192 | Value: 2111 | ||
1193 | Name: PAY_EXCHANGE_TIMEOUT | ||
1194 | Description: We failed to contact the exchange for the /pay request. This response | ||
1195 | + is provided with HTTP status code #MHD_HTTP_REQUEST_TIMEOUT. | ||
1196 | HttpStatus: 408 | ||
1197 | |||
1198 | Value: 2112 | ||
1199 | Name: PAY_EXCHANGE_LOOKUP_FAILED | ||
1200 | Description: When we tried to find information about the exchange to issue the | ||
1201 | + deposit, we failed. This usually only happens if the merchant backend | ||
1202 | + is somehow unable to get its own HTTP client logic to work. This | ||
1203 | + response is provided with HTTP status code | ||
1204 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1205 | HttpStatus: 500 | ||
1206 | |||
1207 | Value: 2114 | ||
1208 | Name: PAY_REFUND_DEADLINE_PAST_WIRE_TRANSFER_DEADLINE | ||
1209 | Description: The refund deadline in the contract is after the transfer deadline. | ||
1210 | + This response is provided with HTTP status code | ||
1211 | + #MHD_HTTP_INTERNAL_SERVER_ERROR as this should have been caught when | ||
1212 | + the offer was first setup. | ||
1213 | HttpStatus: 500 | ||
1214 | |||
1215 | Value: 2115 | ||
1216 | Name: PAY_COINS_ARRAY_EMPTY | ||
1217 | Description: The request fails to provide coins for the payment. This response is | ||
1218 | + provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1219 | HttpStatus: 400 | ||
1220 | |||
1221 | Value: 2116 | ||
1222 | Name: PAY_DB_FETCH_PAY_ERROR | ||
1223 | Description: The merchant failed to fetch the contract terms from the merchant's | ||
1224 | + database. This response is provided with HTTP status code | ||
1225 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1226 | HttpStatus: 500 | ||
1227 | |||
1228 | Value: 2117 | ||
1229 | Name: PAY_DB_FETCH_TRANSACTION_ERROR | ||
1230 | Description: The merchant failed to fetch the merchant's previous state with | ||
1231 | + respect to transactions from its database. This response is provided | ||
1232 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1233 | HttpStatus: 500 | ||
1234 | |||
1235 | Value: 2119 | ||
1236 | Name: PAY_DB_STORE_TRANSACTION_ERROR | ||
1237 | Description: The merchant failed to store the merchant's state with respect to the | ||
1238 | + transaction in its database. This response is provided with HTTP | ||
1239 | + status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1240 | HttpStatus: 500 | ||
1241 | |||
1242 | Value: 2120 | ||
1243 | Name: PAY_EXCHANGE_KEYS_FAILURE | ||
1244 | Description: The exchange failed to provide a valid response to the merchant's | ||
1245 | + /keys request. This response is provided with HTTP status code | ||
1246 | + #MHD_HTTP_FAILED_DEPENDENCY. | ||
1247 | HttpStatus: 424 | ||
1248 | |||
1249 | Value: 2121 | ||
1250 | Name: PAY_OFFER_EXPIRED | ||
1251 | Description: The payment is too late, the offer has expired. This response is | ||
1252 | + provided with HTTP status code #MHD_HTTP_GONE. | ||
1253 | HttpStatus: 410 | ||
1254 | |||
1255 | Value: 2122 | ||
1256 | Name: PAY_MERCHANT_FIELD_MISSING | ||
1257 | Description: The "merchant" field is missing in the proposal data. This response is | ||
1258 | + provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1259 | HttpStatus: 400 | ||
1260 | |||
1261 | Value: 2123 | ||
1262 | Name: PAY_FAILED_COMPUTE_PROPOSAL_HASH | ||
1263 | Description: Failed computing a hash code (likely server out-of-memory). This | ||
1264 | + response is provided with HTTP status code | ||
1265 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1266 | HttpStatus: 500 | ||
1267 | |||
1268 | Value: 2124 | ||
1269 | Name: PAY_WIRE_HASH_UNKNOWN | ||
1270 | Description: Failed to locate merchant's account information matching the wire hash | ||
1271 | + given in the proposal. This response is provided with HTTP status code | ||
1272 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1273 | HttpStatus: 500 | ||
1274 | |||
1275 | Value: 2125 | ||
1276 | Name: PAY_WIRE_FEE_CURRENCY_MISMATCH | ||
1277 | Description: We got different currencies for the wire fee and the maximum wire fee. | ||
1278 | + This response is provided with HTTP status code of | ||
1279 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1280 | HttpStatus: 500 | ||
1281 | |||
1282 | Value: 2127 | ||
1283 | Name: PAY_WRONG_INSTANCE | ||
1284 | Description: A unknown merchant public key was included in the payment. That | ||
1285 | + happens typically when the wallet sends the payment to the wrong | ||
1286 | + merchant instance. This response is provided with an HTTP status code | ||
1287 | + of #MHD_HTTP_NOT_FOUND. | ||
1288 | HttpStatus: 404 | ||
1289 | |||
1290 | Value: 2128 | ||
1291 | Name: PAY_EXCHANGE_HAS_NO_KEYS | ||
1292 | Description: The exchange failed to give us a response when we asked for /keys. | ||
1293 | + This response is provided with HTTP status code | ||
1294 | + #MHD_HTTP_FAILED_DEPENDENCY. | ||
1295 | HttpStatus: 424 | ||
1296 | |||
1297 | Value: 2129 | ||
1298 | Name: PAY_DENOMINATION_DEPOSIT_EXPIRED | ||
1299 | Description: The deposit time for the denomination has expired. This response is | ||
1300 | + provided with HTTP status code #MHD_HTTP_GONE. | ||
1301 | HttpStatus: 410 | ||
1302 | |||
1303 | Value: 2130 | ||
1304 | Name: PAY_PROPOSAL_NOT_FOUND | ||
1305 | Description: The proposal is not known to the backend. This response is provided | ||
1306 | + with an HTTP status code of #MHD_HTTP_NOT_FOUND. | ||
1307 | HttpStatus: 404 | ||
1308 | |||
1309 | Value: 2131 | ||
1310 | Name: PAY_EXCHANGE_WIRE_FEE_ADDITION_FAILED | ||
1311 | Description: The exchange of the deposited coin charges a wire fee that could not | ||
1312 | + be added to the total (total amount too high). This response is | ||
1313 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1314 | HttpStatus: 500 | ||
1315 | |||
1316 | Value: 2132 | ||
1317 | Name: PAY_REFUNDED | ||
1318 | Description: The contract was not fully paid because of refunds. Note that clients | ||
1319 | + MAY treat this as paid if, for example, contracts must be executed | ||
1320 | + despite of refunds. This response is provided with HTTP status code | ||
1321 | + #MHD_HTTP_PAYMENT_REQUIRED. | ||
1322 | HttpStatus: 402 | ||
1323 | |||
1324 | Value: 2133 | ||
1325 | Name: PAY_REFUNDS_EXCEED_PAYMENTS | ||
1326 | Description: According to our database, we have refunded more than we were paid | ||
1327 | + (which should not be possible). This response is provided with HTTP | ||
1328 | + status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1329 | HttpStatus: 500 | ||
1330 | |||
1331 | Value: 2134 | ||
1332 | Name: PAY_ABORT_REFUND_REFUSED_PAYMENT_COMPLETE | ||
1333 | Description: Legacy stuff. Remove me with protocol v1. This response is provided | ||
1334 | + with HTTP status code #MHD_HTTP_PREREQUISITE. | ||
1335 | HttpStatus: 0 | ||
1336 | |||
1337 | Value: 2150 | ||
1338 | Name: ABORT_EXCHANGE_KEYS_FAILURE | ||
1339 | Description: The merchant failed to contact the exchange. This response is provided | ||
1340 | + with HTTP status code of #MHD_HTTP_FAILED_DEPENDENCY. | ||
1341 | HttpStatus: 424 | ||
1342 | |||
1343 | Value: 2151 | ||
1344 | Name: ABORT_EXCHANGE_REFUND_FAILED | ||
1345 | Description: The merchant failed to send the exchange the refund request. This | ||
1346 | + response is provided with HTTP status code of | ||
1347 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1348 | HttpStatus: 500 | ||
1349 | |||
1350 | Value: 2152 | ||
1351 | Name: ABORT_EXCHANGE_LOOKUP_FAILED | ||
1352 | Description: The merchant failed to find the exchange to process the lookup. This | ||
1353 | + response is provided with HTTP status code of | ||
1354 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1355 | HttpStatus: 500 | ||
1356 | |||
1357 | Value: 2153 | ||
1358 | Name: ABORT_DB_STORE_ABORT_ERROR | ||
1359 | Description: The merchant failed to store the abort request in its database. This | ||
1360 | + response is provided with HTTP status code of | ||
1361 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1362 | HttpStatus: 500 | ||
1363 | |||
1364 | Value: 2154 | ||
1365 | Name: ABORT_DB_STORE_TRANSACTION_ERROR | ||
1366 | Description: The merchant failed to repeatedly serialize the transaction. This | ||
1367 | + response is provided with HTTP status code of | ||
1368 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1369 | HttpStatus: 500 | ||
1370 | |||
1371 | Value: 2155 | ||
1372 | Name: ABORT_DB_FETCH_TRANSACTION_ERROR | ||
1373 | Description: The merchant failed in the lookup part of the transaction. This | ||
1374 | + response is provided with HTTP status code of | ||
1375 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1376 | HttpStatus: 500 | ||
1377 | |||
1378 | Value: 2156 | ||
1379 | Name: ABORT_CONTRACT_NOT_FOUND | ||
1380 | Description: The merchant could not find the contract. This response is provided | ||
1381 | + with HTTP status code of #MHD_HTTP_NOT_FOUND. | ||
1382 | HttpStatus: 404 | ||
1383 | |||
1384 | Value: 2157 | ||
1385 | Name: ABORT_REFUND_REFUSED_PAYMENT_COMPLETE | ||
1386 | Description: The payment was already completed and thus cannot be aborted anymore. | ||
1387 | + This response is provided with HTTP status code of | ||
1388 | + #MHD_HTTP_PRECONDITION_FAILED. | ||
1389 | HttpStatus: 412 | ||
1390 | |||
1391 | Value: 2158 | ||
1392 | Name: ABORT_CONTRACT_HASH_MISSMATCH | ||
1393 | Description: The hash provided by the wallet does not match the order. This | ||
1394 | + response is provided with HTTP status code of #MHD_HTTP_FORBIDDEN. | ||
1395 | HttpStatus: 403 | ||
1396 | |||
1397 | Value: 2159 | ||
1398 | Name: ABORT_COINS_ARRAY_EMPTY | ||
1399 | Description: The array of coins cannot be empty. This response is provided with | ||
1400 | + HTTP status code of #MHD_HTTP_BAD_REQUEST. | ||
1401 | HttpStatus: 400 | ||
1402 | |||
1403 | Value: 2160 | ||
1404 | Name: ABORT_EXCHANGE_TIMEOUT | ||
1405 | Description: The merchant experienced a timeout processing the request. This | ||
1406 | + response is provided with HTTP status code of | ||
1407 | + #MHD_HTTP_REQUEST_TIMEOUT. | ||
1408 | HttpStatus: 408 | ||
1409 | |||
1410 | Value: 2200 | ||
1411 | Name: HISTORY_TIMESTAMP_OVERFLOW | ||
1412 | Description: Integer overflow with specified timestamp argument detected. This | ||
1413 | + response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
1414 | HttpStatus: 400 | ||
1415 | |||
1416 | Value: 2201 | ||
1417 | Name: HISTORY_DB_FETCH_ERROR | ||
1418 | Description: Failed to retrieve history from merchant database. This response is | ||
1419 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1420 | HttpStatus: 500 | ||
1421 | |||
1422 | Value: 2250 | ||
1423 | Name: POLL_PAYMENT_CONTRACT_NOT_FOUND | ||
1424 | Description: The backend could not find the contract specified in the request. | ||
1425 | + This response is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
1426 | HttpStatus: 404 | ||
1427 | |||
1428 | Value: 2251 | ||
1429 | Name: POLL_PAYMENT_REPLY_MALFORMED | ||
1430 | Description: The response provided by the merchant backend was malformed. This | ||
1431 | + error is created client-side. | ||
1432 | HttpStatus: 0 | ||
1433 | |||
1434 | Value: 2300 | ||
1435 | Name: TRACK_TRANSACTION_EXCHANGE_TIMEOUT | ||
1436 | Description: We failed to contact the exchange for the /track/transaction request. | ||
1437 | + This response is provided with HTTP status code | ||
1438 | + #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
1439 | HttpStatus: 503 | ||
1440 | |||
1441 | Value: 2301 | ||
1442 | Name: TRACK_TRANSACTION_EXCHANGE_KEYS_FAILURE | ||
1443 | Description: We failed to get a valid /keys response from the exchange for the | ||
1444 | + /track/transaction request. This response is provided with HTTP | ||
1445 | + status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
1446 | HttpStatus: 424 | ||
1447 | |||
1448 | Value: 2302 | ||
1449 | Name: TRACK_TRANSACTION_TRANSACTION_UNKNOWN | ||
1450 | Description: The backend could not find the transaction specified in the request. | ||
1451 | + This response is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
1452 | HttpStatus: 404 | ||
1453 | |||
1454 | Value: 2303 | ||
1455 | Name: TRACK_TRANSACTION_DB_FETCH_TRANSACTION_ERROR | ||
1456 | Description: The backend had a database access error trying to retrieve transaction | ||
1457 | + data from its database. The response is provided with HTTP status code | ||
1458 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1459 | HttpStatus: 500 | ||
1460 | |||
1461 | Value: 2304 | ||
1462 | Name: TRACK_TRANSACTION_DB_FETCH_PAYMENT_ERROR | ||
1463 | Description: The backend had a database access error trying to retrieve payment | ||
1464 | + data from its database. The response is provided with HTTP status code | ||
1465 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1466 | HttpStatus: 500 | ||
1467 | |||
1468 | Value: 2305 | ||
1469 | Name: TRACK_TRANSACTION_DB_NO_DEPOSITS_ERROR | ||
1470 | Description: The backend found no applicable deposits in the database. This is odd, | ||
1471 | + as we know about the transaction, but not about deposits we made for | ||
1472 | + the transaction. The response is provided with HTTP status code | ||
1473 | + #MHD_HTTP_NOT_FOUND. | ||
1474 | HttpStatus: 404 | ||
1475 | |||
1476 | Value: 2306 | ||
1477 | Name: TRACK_TRANSACTION_COIN_TRACE_ERROR | ||
1478 | Description: We failed to obtain a wire transfer identifier for one of the coins in | ||
1479 | + the transaction. The response is provided with HTTP status code | ||
1480 | + #MHD_HTTP_FAILED_DEPENDENCY if the exchange had a hard error, or | ||
1481 | + #MHD_HTTP_ACCEPTED if the exchange signaled that the transfer was in | ||
1482 | + progress. | ||
1483 | HttpStatus: 424 | ||
1484 | HttpStatus: 202 | ||
1485 | |||
1486 | Value: 2307 | ||
1487 | Name: TRACK_TRANSACTION_WIRE_TRANSFER_TRACE_ERROR | ||
1488 | Description: We failed to obtain the full wire transfer identifier for the transfer | ||
1489 | + one of the coins was aggregated into. The response is provided with | ||
1490 | + HTTP status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
1491 | HttpStatus: 424 | ||
1492 | |||
1493 | Value: 2308 | ||
1494 | Name: TRACK_TRANSACTION_CONFLICTING_REPORTS | ||
1495 | Description: We got conflicting reports from the exhange with respect to which | ||
1496 | + transfers are included in which aggregate. The response is provided | ||
1497 | + with HTTP status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
1498 | HttpStatus: 424 | ||
1499 | |||
1500 | Value: 2350 | ||
1501 | Name: GET_TRANSFERS_DB_FETCH_ERROR | ||
1502 | Description: We did failed to retrieve information from our database. The response | ||
1503 | + is provided with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1504 | HttpStatus: 500 | ||
1505 | |||
1506 | Value: 2400 | ||
1507 | Name: POST_TRANSFERS_EXCHANGE_TIMEOUT | ||
1508 | Description: We failed to contact the exchange for the /track/transfer request. | ||
1509 | + This response is provided with HTTP status code | ||
1510 | + #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
1511 | HttpStatus: 503 | ||
1512 | |||
1513 | Value: 2401 | ||
1514 | Name: POST_TRANSFERS_EXCHANGE_KEYS_FAILURE | ||
1515 | Description: We failed to obtain an acceptable /keys response from the exchange for | ||
1516 | + the /track/transfer request. This response is provided with HTTP | ||
1517 | + status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
1518 | HttpStatus: 424 | ||
1519 | |||
1520 | Value: 2402 | ||
1521 | Name: POST_TRANSFERS_DB_STORE_COIN_ERROR | ||
1522 | Description: We failed to persist coin wire transfer information in our merchant | ||
1523 | + database. The response is provided with HTTP status code | ||
1524 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1525 | HttpStatus: 500 | ||
1526 | |||
1527 | Value: 2403 | ||
1528 | Name: POST_TRANSFERS_REQUEST_ERROR | ||
1529 | Description: We internally failed to execute the /track/transfer request. The | ||
1530 | + response is provided with HTTP status code | ||
1531 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1532 | HttpStatus: 500 | ||
1533 | |||
1534 | Value: 2404 | ||
1535 | Name: POST_TRANSFERS_DB_STORE_TRANSFER_ERROR | ||
1536 | Description: We failed to persist wire transfer information in our merchant | ||
1537 | + database. The response is provided with HTTP status code | ||
1538 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1539 | HttpStatus: 500 | ||
1540 | |||
1541 | Value: 2405 | ||
1542 | Name: POST_TRANSFERS_EXCHANGE_ERROR | ||
1543 | Description: The exchange returned an error from /track/transfer. The response is | ||
1544 | + provided with HTTP status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
1545 | HttpStatus: 424 | ||
1546 | |||
1547 | Value: 2406 | ||
1548 | Name: POST_TRANSFERS_DB_FETCH_DEPOSIT_ERROR | ||
1549 | Description: We failed to fetch deposit information from our merchant database. The | ||
1550 | + response is provided with HTTP status code | ||
1551 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1552 | HttpStatus: 500 | ||
1553 | |||
1554 | Value: 2407 | ||
1555 | Name: POST_TRANSFERS_DB_INTERNAL_LOGIC_ERROR | ||
1556 | Description: We encountered an internal logic error. The response is provided with | ||
1557 | + HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1558 | HttpStatus: 500 | ||
1559 | |||
1560 | Value: 2408 | ||
1561 | Name: POST_TRANSFERS_CONFLICTING_REPORTS | ||
1562 | Description: The exchange gave conflicting information about a coin which has been | ||
1563 | + wire transferred. The response is provided with HTTP status code | ||
1564 | + #MHD_HTTP_FAILED_DEPENDENCY. | ||
1565 | HttpStatus: 424 | ||
1566 | |||
1567 | Value: 2409 | ||
1568 | Name: POST_TRANSFERS_JSON_RESPONSE_ERROR | ||
1569 | Description: The merchant backend had problems in creating the JSON response. | ||
1570 | HttpStatus: 0 | ||
1571 | |||
1572 | Value: 2410 | ||
1573 | Name: POST_TRANSFERS_JSON_BAD_WIRE_FEE | ||
1574 | Description: The exchange charged a different wire fee than what it originally | ||
1575 | + advertised, and it is higher. The response is provided with an HTTP | ||
1576 | + status of #MHD_HTTP_FAILED_DEPENDENCY. | ||
1577 | HttpStatus: 424 | ||
1578 | |||
1579 | Value: 2411 | ||
1580 | Name: POST_TRANSFERS_ACCOUNT_NOT_FOUND | ||
1581 | Description: We did not find the account that the transfer was made to. The | ||
1582 | + response is provided with an HTTP status of #MHD_HTTP_NOT_FOUND. | ||
1583 | HttpStatus: 404 | ||
1584 | |||
1585 | Value: 2412 | ||
1586 | Name: POST_TRANSFERS_DB_STORE_ERROR | ||
1587 | Description: We did failed to store information in our database. The response is | ||
1588 | + provided with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1589 | HttpStatus: 500 | ||
1590 | |||
1591 | Value: 2413 | ||
1592 | Name: POST_TRANSFERS_DB_LOOKUP_ERROR | ||
1593 | Description: We did failed to retrieve information from our database. The response | ||
1594 | + is provided with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1595 | HttpStatus: 500 | ||
1596 | |||
1597 | Value: 2450 | ||
1598 | Name: POST_INSTANCES_ALREADY_EXISTS | ||
1599 | Description: The merchant backend cannot create an instance under the given | ||
1600 | + identifier as one already exists. Use PATCH to modify the existing | ||
1601 | + entry. The response is provied with an HTTP status of | ||
1602 | + #MHD_HTTP_CONFLICT. | ||
1603 | HttpStatus: 409 | ||
1604 | |||
1605 | Value: 2451 | ||
1606 | Name: POST_INSTANCES_BAD_PAYTO_URIS | ||
1607 | Description: The merchant backend cannot create an instance because the specified | ||
1608 | + bank accounts are somehow invalid. The response is provied with an | ||
1609 | + HTTP status of #MHD_HTTP_BAD_REQUEST. | ||
1610 | HttpStatus: 400 | ||
1611 | |||
1612 | Value: 2452 | ||
1613 | Name: POST_INSTANCES_DB_START_ERROR | ||
1614 | Description: The merchant backend cannot create an instance because it failed to | ||
1615 | + start the database transaction. The response is provied with an HTTP | ||
1616 | + status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1617 | HttpStatus: 500 | ||
1618 | |||
1619 | Value: 2453 | ||
1620 | Name: POST_INSTANCES_DB_COMMIT_ERROR | ||
1621 | Description: The merchant backend cannot create an instance because it failed to | ||
1622 | + commit the database transaction. The response is provied with an HTTP | ||
1623 | + status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1624 | HttpStatus: 500 | ||
1625 | |||
1626 | Value: 2454 | ||
1627 | Name: DELETE_INSTANCES_ID_DB_HARD_FAILURE | ||
1628 | Description: The merchant backend cannot delete an instance because it failed to | ||
1629 | + commit the database transaction. The response is provied with an HTTP | ||
1630 | + status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1631 | HttpStatus: 500 | ||
1632 | |||
1633 | Value: 2455 | ||
1634 | Name: DELETE_INSTANCES_ID_NO_SUCH_INSTANCE | ||
1635 | Description: The merchant backend cannot delete the data because it already does | ||
1636 | + not exist. The response is provied with an HTTP status of | ||
1637 | + #MHD_HTTP_NOT_FOUND. | ||
1638 | HttpStatus: 404 | ||
1639 | |||
1640 | Value: 2456 | ||
1641 | Name: PATCH_INSTANCES_BAD_PAYTO_URIS | ||
1642 | Description: The merchant backend cannot update an instance because the specified | ||
1643 | + bank accounts are somehow invalid. The response is provied with an | ||
1644 | + HTTP status of #MHD_HTTP_BAD_REQUEST. | ||
1645 | HttpStatus: 400 | ||
1646 | |||
1647 | Value: 2457 | ||
1648 | Name: PATCH_INSTANCES_DB_START_ERROR | ||
1649 | Description: The merchant backend cannot patch an instance because it failed to | ||
1650 | + start the database transaction. The response is provied with an HTTP | ||
1651 | + status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1652 | HttpStatus: 500 | ||
1653 | |||
1654 | Value: 2458 | ||
1655 | Name: PATCH_INSTANCES_DB_COMMIT_ERROR | ||
1656 | Description: The merchant backend cannot patch an instance because it failed to | ||
1657 | + commit the database transaction. The response is provied with an HTTP | ||
1658 | + status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1659 | HttpStatus: 500 | ||
1660 | |||
1661 | Value: 2500 | ||
1662 | Name: MAP_IN_UNMATCHED_HASH | ||
1663 | Description: The hash provided in the request of /map/in does not match the | ||
1664 | + contract sent alongside in the same request. | ||
1665 | HttpStatus: 0 | ||
1666 | |||
1667 | Value: 2501 | ||
1668 | Name: PROPOSAL_STORE_DB_ERROR | ||
1669 | Description: The backend encountered an error while trying to store the | ||
1670 | + h_contract_terms into the database. The response is provided with HTTP | ||
1671 | + status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1672 | HttpStatus: 500 | ||
1673 | |||
1674 | Value: 2502 | ||
1675 | Name: PROPOSAL_LOOKUP_DB_ERROR | ||
1676 | Description: The backend encountered an error while trying to retrieve the proposal | ||
1677 | + data from database. Likely to be an internal error. The response is | ||
1678 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1679 | HttpStatus: 500 | ||
1680 | |||
1681 | Value: 2503 | ||
1682 | Name: PROPOSAL_LOOKUP_NOT_FOUND | ||
1683 | Description: The proposal being looked up is not found on this merchant. Returned | ||
1684 | + with an HTTP status code of #MHD_HTTP_NOT_FOUND | ||
1685 | HttpStatus: 404 | ||
1686 | |||
1687 | Value: 2504 | ||
1688 | Name: PROPOSAL_NO_LOCALTIME | ||
1689 | Description: The proposal had no timestamp and the backend failed to obtain the | ||
1690 | + local time. Likely to be an internal error. The response is provided | ||
1691 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1692 | HttpStatus: 500 | ||
1693 | |||
1694 | Value: 2505 | ||
1695 | Name: PROPOSAL_ORDER_PARSE_ERROR | ||
1696 | Description: The order provided to the backend could not be parsed, some required | ||
1697 | + fields were missing or ill-formed. Returned with an HTTP status code | ||
1698 | + #MHD_HTTP_BAD_REQUEST. | ||
1699 | HttpStatus: 400 | ||
1700 | |||
1701 | Value: 2506 | ||
1702 | Name: PROPOSAL_STORE_DB_ERROR_HARD | ||
1703 | Description: The backend encountered an error while trying to find the existing | ||
1704 | + proposal in the database. The response is provided with HTTP status | ||
1705 | + code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1706 | HttpStatus: 500 | ||
1707 | |||
1708 | Value: 2507 | ||
1709 | Name: PROPOSAL_STORE_DB_ERROR_SOFT | ||
1710 | Description: The backend encountered an error while trying to find the existing | ||
1711 | + proposal in the database. The response is provided with HTTP status | ||
1712 | + code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1713 | HttpStatus: 500 | ||
1714 | |||
1715 | Value: 2508 | ||
1716 | Name: PROPOSAL_STORE_DB_ERROR_ALREADY_EXISTS | ||
1717 | Description: The backend encountered an error: the proposal already exists. The | ||
1718 | + response is provided with HTTP status code | ||
1719 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1720 | HttpStatus: 500 | ||
1721 | |||
1722 | Value: 2509 | ||
1723 | Name: PROPOSAL_ORDER_BAD_CURRENCY | ||
1724 | Description: The order provided to the backend uses an amount in a currency that | ||
1725 | + does not match the backend's configuration. Returned with HTTP status | ||
1726 | + code #MHD_HTTP_BAD_REQUEST. | ||
1727 | HttpStatus: 400 | ||
1728 | |||
1729 | Value: 2510 | ||
1730 | Name: PROPOSAL_REPLY_MALFORMED | ||
1731 | Description: The response provided by the merchant backend was malformed. This | ||
1732 | + error is created client-side. | ||
1733 | HttpStatus: 0 | ||
1734 | |||
1735 | Value: 2511 | ||
1736 | Name: ORDERS_DELETE_NO_SUCH_ORDER | ||
1737 | Description: The order provided to the backend could not be deleted, it is not | ||
1738 | + known. Returned with an HTTP status code #MHD_HTTP_NOT_FOUND. | ||
1739 | HttpStatus: 404 | ||
1740 | |||
1741 | Value: 2512 | ||
1742 | Name: ORDERS_DELETE_AWAITING_PAYMENT | ||
1743 | Description: The order provided to the backend could not be deleted, our offer is | ||
1744 | + still valid and awaiting payment. Returned with an HTTP status code | ||
1745 | + #MHD_HTTP_CONFLICT. | ||
1746 | HttpStatus: 409 | ||
1747 | |||
1748 | Value: 2513 | ||
1749 | Name: ORDERS_DELETE_DB_HARD_FAILURE | ||
1750 | Description: The order provided to the backend could not be deleted, due to a | ||
1751 | + database error. Returned with an HTTP status code | ||
1752 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1753 | HttpStatus: 500 | ||
1754 | |||
1755 | Value: 2514 | ||
1756 | Name: ORDERS_LOOKUP_PRODUCT_DB_HARD_FAILURE | ||
1757 | Description: The order provided to the backend could not be completed, due to a | ||
1758 | + database error trying to fetch product inventory data. Returned with | ||
1759 | + an HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1760 | HttpStatus: 500 | ||
1761 | |||
1762 | Value: 2515 | ||
1763 | Name: ORDERS_LOOKUP_PRODUCT_DB_SOFT_FAILURE | ||
1764 | Description: The order provided to the backend could not be completed, due to a | ||
1765 | + database serialization error (which should be impossible) trying to | ||
1766 | + fetch product inventory data. Returned with an HTTP status code | ||
1767 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1768 | HttpStatus: 500 | ||
1769 | |||
1770 | Value: 2516 | ||
1771 | Name: ORDERS_LOOKUP_PRODUCT_NOT_FOUND | ||
1772 | Description: The order provided to the backend could not be completed, because a | ||
1773 | + product to be completed via inventory data is not actually in our | ||
1774 | + inventory. Returned with an HTTP status code #MHD_HTTP_NOT_FOUND. | ||
1775 | HttpStatus: 404 | ||
1776 | |||
1777 | Value: 2517 | ||
1778 | Name: ORDERS_GET_DB_LOOKUP_ERROR | ||
1779 | Description: We could not obtain a list of all orders because of a database | ||
1780 | + failure. Returned with an HTTP status code | ||
1781 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1782 | HttpStatus: 500 | ||
1783 | |||
1784 | Value: 2518 | ||
1785 | Name: ORDERS_CLAIM_HARD_DB_ERROR | ||
1786 | Description: We could not claim the order because of a database failure. Returned | ||
1787 | + with an HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1788 | HttpStatus: 500 | ||
1789 | |||
1790 | Value: 2519 | ||
1791 | Name: ORDERS_CLAIM_SOFT_DB_ERROR | ||
1792 | Description: We could not claim the order because of a database serialization | ||
1793 | + failure. Returned with an HTTP status code | ||
1794 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1795 | HttpStatus: 500 | ||
1796 | |||
1797 | Value: 2520 | ||
1798 | Name: ORDERS_CLAIM_NOT_FOUND | ||
1799 | Description: We could not claim the order because the backend is unaware of it. | ||
1800 | + Returned with an HTTP status code #MHD_HTTP_NOT_FOUND. | ||
1801 | HttpStatus: 404 | ||
1802 | |||
1803 | Value: 2521 | ||
1804 | Name: ORDERS_ALREADY_CLAIMED | ||
1805 | Description: We could not claim the order because someone else claimed it first. | ||
1806 | + Returned with an HTTP status code #MHD_HTTP_CONFLICT. | ||
1807 | HttpStatus: 409 | ||
1808 | |||
1809 | Value: 2550 | ||
1810 | Name: GET_PRODUCTS_DB_LOOKUP_ERROR | ||
1811 | Description: The merchant backend failed to lookup the products. The response is | ||
1812 | + provied with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1813 | HttpStatus: 500 | ||
1814 | |||
1815 | Value: 2551 | ||
1816 | Name: PRODUCTS_POST_DB_START_ERROR | ||
1817 | Description: The merchant backend failed to start the transaction. The response is | ||
1818 | + provied with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1819 | HttpStatus: 500 | ||
1820 | |||
1821 | Value: 2552 | ||
1822 | Name: PRODUCTS_POST_CONFLICT_PRODUCT_EXISTS | ||
1823 | Description: The product ID exists. The response is provied with an HTTP status of | ||
1824 | + #MHD_HTTP_CONFLICT. | ||
1825 | HttpStatus: 409 | ||
1826 | |||
1827 | Value: 2553 | ||
1828 | Name: PRODUCTS_POST_DB_COMMIT_SOFT_ERROR | ||
1829 | Description: The merchant backend failed to serialize the transaction. The response | ||
1830 | + is provied with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1831 | HttpStatus: 500 | ||
1832 | |||
1833 | Value: 2554 | ||
1834 | Name: PRODUCTS_POST_DB_COMMIT_HARD_ERROR | ||
1835 | Description: The merchant backend failed to commit the transaction. The response is | ||
1836 | + provied with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1837 | HttpStatus: 500 | ||
1838 | |||
1839 | Value: 2555 | ||
1840 | Name: PRODUCTS_PATCH_DB_COMMIT_HARD_ERROR | ||
1841 | Description: The merchant backend failed to commit the transaction. The response is | ||
1842 | + provied with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1843 | HttpStatus: 500 | ||
1844 | |||
1845 | Value: 2556 | ||
1846 | Name: PRODUCTS_PATCH_UNKNOWN_PRODUCT | ||
1847 | Description: The merchant backend did not find the product to be updated. The | ||
1848 | + response is provied with an HTTP status of #MHD_HTTP_NOT_FOUND. | ||
1849 | HttpStatus: 404 | ||
1850 | |||
1851 | Value: 2557 | ||
1852 | Name: PRODUCTS_PATCH_TOTAL_LOST_REDUCED | ||
1853 | Description: The update would have reduced the total amount of product lost, which | ||
1854 | + is not allowed. The response is provied with an HTTP status of | ||
1855 | + #MHD_HTTP_CONFLICT. | ||
1856 | HttpStatus: 409 | ||
1857 | |||
1858 | Value: 2558 | ||
1859 | Name: PRODUCTS_PATCH_TOTAL_LOST_EXCEEDS_STOCKS | ||
1860 | Description: The update would have mean that more stocks were lost than what | ||
1861 | + remains from total inventory after sales, which is not allowed. The | ||
1862 | + response is provied with an HTTP status of #MHD_HTTP_CONFLICT. | ||
1863 | HttpStatus: 409 | ||
1864 | |||
1865 | Value: 2559 | ||
1866 | Name: PRODUCTS_PATCH_TOTAL_STOCKED_REDUCED | ||
1867 | Description: The update would have reduced the total amount of product in stock, | ||
1868 | + which is not allowed. The response is provied with an HTTP status of | ||
1869 | + #MHD_HTTP_CONFLICT. | ||
1870 | HttpStatus: 409 | ||
1871 | |||
1872 | Value: 2560 | ||
1873 | Name: PRODUCTS_LOCK_INSUFFICIENT_STOCKS | ||
1874 | Description: The lock request is for more products than we have left (unlocked) in | ||
1875 | + stock. The response is provied with an HTTP status of | ||
1876 | + #MHD_HTTP_CONFLICT. | ||
1877 | HttpStatus: 409 | ||
1878 | |||
1879 | Value: 2561 | ||
1880 | Name: PRODUCTS_LOCK_UNKNOWN_PRODUCT | ||
1881 | Description: The lock request is for an unknown product. The response is provied | ||
1882 | + with an HTTP status of #MHD_HTTP_NOT_FOUND. | ||
1883 | HttpStatus: 404 | ||
1884 | |||
1885 | Value: 2562 | ||
1886 | Name: PRODUCTS_DELETE_DB_HARD_FAILURE | ||
1887 | Description: The deletion request resulted in a hard database error. The response | ||
1888 | + is provied with an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1889 | HttpStatus: 500 | ||
1890 | |||
1891 | Value: 2563 | ||
1892 | Name: PRODUCTS_DELETE_NO_SUCH_PRODUCT | ||
1893 | Description: The deletion request was for a product unknown to the backend. The | ||
1894 | + response is provied with an HTTP status of #MHD_HTTP_NOT_FOUND. | ||
1895 | HttpStatus: 404 | ||
1896 | |||
1897 | Value: 2564 | ||
1898 | Name: PRODUCTS_DELETE_CONFLICTING_LOCK | ||
1899 | Description: The deletion request is for a product that is locked. The response is | ||
1900 | + provied with an HTTP status of #MHD_HTTP_CONFLICT. | ||
1901 | HttpStatus: 409 | ||
1902 | |||
1903 | Value: 2600 | ||
1904 | Name: REFUND_LOOKUP_INVALID_RESPONSE | ||
1905 | Description: The merchant returned a malformed response. Error created client-side. | ||
1906 | HttpStatus: 0 | ||
1907 | |||
1908 | Value: 2601 | ||
1909 | Name: REFUND_ORDER_ID_UNKNOWN | ||
1910 | Description: The frontend gave an unknown order id to issue the refund to. | ||
1911 | HttpStatus: 0 | ||
1912 | |||
1913 | Value: 2602 | ||
1914 | Name: REFUND_INCONSISTENT_AMOUNT | ||
1915 | Description: The amount to be refunded is inconsistent: either is lower than the | ||
1916 | + previous amount being awarded, or it is too big to be paid back. In | ||
1917 | + this second case, the fault stays on the business dept. side. Returned | ||
1918 | + with an HTTP status of #MHD_HTTP_CONFLICT. | ||
1919 | HttpStatus: 409 | ||
1920 | |||
1921 | Value: 2603 | ||
1922 | Name: REFUND_LOOKUP_DB_ERROR | ||
1923 | Description: The backend encountered an error while trying to retrieve the payment | ||
1924 | + data from database. Likely to be an internal error. | ||
1925 | HttpStatus: 0 | ||
1926 | |||
1927 | Value: 2604 | ||
1928 | Name: REFUND_MERCHANT_DB_COMMIT_ERROR | ||
1929 | Description: The backend encountered an error while trying to retrieve the payment | ||
1930 | + data from database. Likely to be an internal error. | ||
1931 | HttpStatus: 0 | ||
1932 | |||
1933 | Value: 2605 | ||
1934 | Name: PAY_DB_STORE_PAYMENTS_ERROR | ||
1935 | Description: Payments are stored in a single db transaction; this error indicates | ||
1936 | + that one db operation within that transaction failed. This might | ||
1937 | + involve storing of coins or other related db operations, like | ||
1938 | + starting/committing the db transaction or marking a contract as paid. | ||
1939 | HttpStatus: 0 | ||
1940 | |||
1941 | Value: 2606 | ||
1942 | Name: PAY_REFUND_SIGNATURE_FAILED | ||
1943 | Description: The backend failed to sign the refund request. | ||
1944 | HttpStatus: 0 | ||
1945 | |||
1946 | Value: 2607 | ||
1947 | Name: REFUND_LOOKUP_NO_REFUND | ||
1948 | Description: The merchant backend is not available of any applicable refund(s) for | ||
1949 | + this order. Returned with an HTTP status of #MHD_HTTP_NOT_FOUND. | ||
1950 | HttpStatus: 404 | ||
1951 | |||
1952 | Value: 2650 | ||
1953 | Name: RESERVES_POST_UNSUPPORTED_WIRE_METHOD | ||
1954 | Description: The requested wire method is not supported by the exchange. Returned | ||
1955 | + with an HTTP status of #MHD_HTTP_CONFLICT. | ||
1956 | HttpStatus: 409 | ||
1957 | |||
1958 | Value: 2651 | ||
1959 | Name: RESERVES_POST_DB_COMMIT_HARD_ERROR | ||
1960 | Description: The backend failed to commit the result to the database. Returned with | ||
1961 | + an HTTP status of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1962 | HttpStatus: 500 | ||
1963 | |||
1964 | Value: 2652 | ||
1965 | Name: GET_RESERVES_DB_LOOKUP_ERROR | ||
1966 | Description: The backend failed to fetch the requested information from the | ||
1967 | + database. Returned with an HTTP status of | ||
1968 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
1969 | HttpStatus: 500 | ||
1970 | |||
1971 | Value: 2701 | ||
1972 | Name: TIP_AUTHORIZE_INSTANCE_DOES_NOT_TIP | ||
1973 | Description: The backend knows the instance that was supposed to support the tip, | ||
1974 | + but it was not configured for tipping (i.e. has no exchange associated | ||
1975 | + with it). Likely to be a configuration error. Returned with an HTTP | ||
1976 | + status code of #MHD_HTTP_PRECONDITION_FAILED. | ||
1977 | HttpStatus: 412 | ||
1978 | |||
1979 | Value: 2702 | ||
1980 | Name: TIP_AUTHORIZE_RESERVE_EXPIRED | ||
1981 | Description: The reserve that was used to fund the tips has expired. Returned with | ||
1982 | + an HTTP status code of #MHD_HTTP_GONE. | ||
1983 | HttpStatus: 410 | ||
1984 | |||
1985 | Value: 2703 | ||
1986 | Name: TIP_AUTHORIZE_RESERVE_UNKNOWN | ||
1987 | Description: The reserve that was used to fund the tips was not found in the DB. | ||
1988 | + Returned with an HTTP status code of #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
1989 | HttpStatus: 503 | ||
1990 | |||
1991 | Value: 2704 | ||
1992 | Name: TIP_AUTHORIZE_INSUFFICIENT_FUNDS | ||
1993 | Description: The backend knows the instance that was supposed to support the tip, | ||
1994 | + and it was configured for tipping. However, the funds remaining are | ||
1995 | + insufficient to cover the tip, and the merchant should top up the | ||
1996 | + reserve. Returned with an HTTP status code of #MHD_HTTP_PRECONDITION | ||
1997 | + FAILED. | ||
1998 | HttpStatus: 0 | ||
1999 | |||
2000 | Value: 2705 | ||
2001 | Name: TIP_AUTHORIZE_DB_HARD_ERROR | ||
2002 | Description: The backend had trouble accessing the database to persist information | ||
2003 | + about the tip authorization. Returned with an HTTP status code of | ||
2004 | + internal error. | ||
2005 | HttpStatus: 0 | ||
2006 | |||
2007 | Value: 2706 | ||
2008 | Name: TIP_AUTHORIZE_DB_SOFT_ERROR | ||
2009 | Description: The backend had trouble accessing the database to persist information | ||
2010 | + about the tip authorization. The problem might be fixable by repeating | ||
2011 | + the transaction. | ||
2012 | HttpStatus: 0 | ||
2013 | |||
2014 | Value: 2707 | ||
2015 | Name: TIP_QUERY_RESERVE_STATUS_FAILED_EXCHANGE_DOWN | ||
2016 | Description: The backend failed to obtain a reserve status from the exchange. This | ||
2017 | + response is provided with HTTP status code | ||
2018 | + #MHD_HTTP_FAILED_DEPENDENCY. | ||
2019 | HttpStatus: 424 | ||
2020 | |||
2021 | Value: 2708 | ||
2022 | Name: TIP_QUERY_RESERVE_HISTORY_FAILED_EMPTY | ||
2023 | Description: The backend got an empty (!) reserve history from the exchange. This | ||
2024 | + response is provided with HTTP status code | ||
2025 | + #MHD_HTTP_FAILED_DEPENDENCY. | ||
2026 | HttpStatus: 424 | ||
2027 | |||
2028 | Value: 2709 | ||
2029 | Name: TIP_QUERY_RESERVE_HISTORY_INVALID_NO_DEPOSIT | ||
2030 | Description: The backend got an invalid reserve history (fails to start with a | ||
2031 | + deposit) from the exchange. This response is provided with HTTP status | ||
2032 | + code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2033 | HttpStatus: 424 | ||
2034 | |||
2035 | Value: 2710 | ||
2036 | Name: TIP_QUERY_RESERVE_UNKNOWN_TO_EXCHANGE | ||
2037 | Description: The backend got an 404 response from the exchange when it inquired | ||
2038 | + about the reserve history. The response is provided with HTTP status | ||
2039 | + code #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
2040 | HttpStatus: 503 | ||
2041 | |||
2042 | Value: 2711 | ||
2043 | Name: TIP_QUERY_RESERVE_CURRENCY_MISMATCH | ||
2044 | Description: The backend got a reserve with a currency that does not match the | ||
2045 | + backend's currency. The response is provided with HTTP status code | ||
2046 | + #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
2047 | HttpStatus: 503 | ||
2048 | |||
2049 | Value: 2712 | ||
2050 | Name: TIP_QUERY_RESERVE_HISTORY_ARITHMETIC_ISSUE_DEPOSIT | ||
2051 | Description: The backend got a reserve history with amounts it cannot process | ||
2052 | + (addition failure in deposits). The response is provided with HTTP | ||
2053 | + status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2054 | HttpStatus: 424 | ||
2055 | |||
2056 | Value: 2713 | ||
2057 | Name: TIP_QUERY_RESERVE_HISTORY_ARITHMETIC_ISSUE_WITHDRAW | ||
2058 | Description: The backend got a reserve history with amounts it cannot process | ||
2059 | + (addition failure in withdraw amounts). The response is provided with | ||
2060 | + HTTP status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2061 | HttpStatus: 424 | ||
2062 | |||
2063 | Value: 2714 | ||
2064 | Name: TIP_QUERY_RESERVE_HISTORY_ARITHMETIC_ISSUE_CLOSED | ||
2065 | Description: The backend got a reserve history with amounts it cannot process | ||
2066 | + (addition failure in closing amounts). The response is provided with | ||
2067 | + HTTP status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2068 | HttpStatus: 424 | ||
2069 | |||
2070 | Value: 2715 | ||
2071 | Name: TIP_QUERY_RESERVE_HISTORY_ARITHMETIC_ISSUE_INCONSISTENT | ||
2072 | Description: The backend got a reserve history with inconsistent amounts. | ||
2073 | HttpStatus: 0 | ||
2074 | |||
2075 | Value: 2716 | ||
2076 | Name: TIP_QUERY_DB_ERROR | ||
2077 | Description: The backend encountered a database error querying tipping reserves. | ||
2078 | HttpStatus: 0 | ||
2079 | |||
2080 | Value: 2717 | ||
2081 | Name: TIP_QUERY_RESERVE_HISTORY_FAILED | ||
2082 | Description: The backend got an unexpected resever history reply from the exchange. | ||
2083 | + This response is provided with HTTP status code | ||
2084 | + #MHD_HTTP_FAILED_DEPENDENCY. | ||
2085 | HttpStatus: 424 | ||
2086 | |||
2087 | Value: 2718 | ||
2088 | Name: TIP_QUERY_RESERVE_HISTORY_ARITHMETIC_ISSUE_RECOUP | ||
2089 | Description: The backend got a reserve history with amounts it cannot process | ||
2090 | + (addition failure in withdraw amounts). The response is provided with | ||
2091 | + HTTP status code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2092 | HttpStatus: 424 | ||
2093 | |||
2094 | Value: 2719 | ||
2095 | Name: TIP_QUERY_INSTANCE_DOES_NOT_TIP | ||
2096 | Description: The backend knows the instance that was supposed to support the tip, | ||
2097 | + but it was not configured for tipping (i.e. has no exchange associated | ||
2098 | + with it). Likely to be a configuration error. Returned with an HTTP | ||
2099 | + status code of #MHD_HTTP_PRECONDITION_FAILED. | ||
2100 | HttpStatus: 412 | ||
2101 | |||
2102 | Value: 2720 | ||
2103 | Name: TIP_QUERY_TIP_ID_UNKNOWN | ||
2104 | Description: The tip id is unknown. This could happen if the tip id is wrong or | ||
2105 | + the tip authorization expired. | ||
2106 | HttpStatus: 0 | ||
2107 | |||
2108 | Value: 2721 | ||
2109 | Name: RESERVES_DELETE_DB_HARD_FAILURE | ||
2110 | Description: The reserve could not be deleted due to a database failure. Returned | ||
2111 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2112 | HttpStatus: 500 | ||
2113 | |||
2114 | Value: 2722 | ||
2115 | Name: RESERVES_DELETE_NO_SUCH_RESERVE | ||
2116 | Description: The reserve could not be deleted because it is unknown. Returned with | ||
2117 | + HTTP status code #MHD_HTTP_NOT_FOUND. | ||
2118 | HttpStatus: 404 | ||
2119 | |||
2120 | Value: 2723 | ||
2121 | Name: TIP_LOOKUP_RESERVE_DB_FAILURE | ||
2122 | Description: The backend got an unexpected error trying to lookup reserve details | ||
2123 | + from the backend. This response is provided with HTTP status code | ||
2124 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2125 | HttpStatus: 500 | ||
2126 | |||
2127 | Value: 2724 | ||
2128 | Name: TIP_AUTHORIZE_DB_SERIALIZATION_FAILURE | ||
2129 | Description: The backend repeatedly failed to serialize the transaction to | ||
2130 | + authorize the tip. This response is provided with HTTP status code | ||
2131 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2132 | HttpStatus: 500 | ||
2133 | |||
2134 | Value: 2725 | ||
2135 | Name: TIP_AUTHORIZE_DB_START_FAILURE | ||
2136 | Description: The backend failed to start the transaction to authorize the tip. This | ||
2137 | + response is provided with HTTP status code | ||
2138 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2139 | HttpStatus: 500 | ||
2140 | |||
2141 | Value: 2726 | ||
2142 | Name: TIP_AUTHORIZE_DB_LOOKUP_RESERVE_FAILURE | ||
2143 | Description: The backend failed looking up the reserve needed to authorize the tip. | ||
2144 | + This response is provided with HTTP status code | ||
2145 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2146 | HttpStatus: 500 | ||
2147 | |||
2148 | Value: 2727 | ||
2149 | Name: TIP_AUTHORIZE_DB_RESERVE_NOT_FOUND | ||
2150 | Description: The backend failed to find a reserve needed to authorize the tip. This | ||
2151 | + response is provided with HTTP status code | ||
2152 | + #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
2153 | HttpStatus: 503 | ||
2154 | |||
2155 | Value: 2728 | ||
2156 | Name: TIP_AUTHORIZE_DB_RESERVE_INVARIANT_FAILURE | ||
2157 | Description: The backend encountered an internal invariant violation. This response | ||
2158 | + is provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2159 | HttpStatus: 500 | ||
2160 | |||
2161 | Value: 2729 | ||
2162 | Name: TIP_AUTHORIZE_DB_RESERVE_EXPIRED | ||
2163 | Description: The selected exchange expired. This response is provided with HTTP | ||
2164 | + status code #MHD_HTTP_GONE. | ||
2165 | HttpStatus: 410 | ||
2166 | |||
2167 | Value: 2730 | ||
2168 | Name: TIP_AUTHORIZE_DB_UPDATE_RESERVE_FAILURE | ||
2169 | Description: The backend failed updating the reserve needed to authorize the tip. | ||
2170 | + This response is provided with HTTP status code | ||
2171 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2172 | HttpStatus: 500 | ||
2173 | |||
2174 | Value: 2750 | ||
2175 | Name: TIP_ENABLE_DB_TRANSACTION_ERROR | ||
2176 | Description: The backend had trouble accessing the database to persist information | ||
2177 | + about enabling tips. Returned with an HTTP status code of internal | ||
2178 | + error. | ||
2179 | HttpStatus: 0 | ||
2180 | |||
2181 | Value: 2800 | ||
2182 | Name: TIP_PICKUP_TIP_ID_UNKNOWN | ||
2183 | Description: The tip ID is unknown. This could happen if the tip has expired. | ||
2184 | + Returned with an HTTP status code of #MHD_HTTP_NOT_FOUND. | ||
2185 | HttpStatus: 404 | ||
2186 | |||
2187 | Value: 2801 | ||
2188 | Name: TIP_PICKUP_NO_FUNDS | ||
2189 | Description: The amount requested exceeds the remaining tipping balance for this | ||
2190 | + tip ID. Returned with an HTTP status code of "Conflict" (as it | ||
2191 | + conflicts with a previous pickup operation). | ||
2192 | HttpStatus: 0 | ||
2193 | |||
2194 | Value: 2802 | ||
2195 | Name: TIP_PICKUP_DB_ERROR_SOFT | ||
2196 | Description: We encountered a DB error, repeating the request may work. | ||
2197 | HttpStatus: 0 | ||
2198 | |||
2199 | Value: 2803 | ||
2200 | Name: TIP_PICKUP_DB_ERROR_HARD | ||
2201 | Description: We encountered a DB error, repeating the request will not help. This | ||
2202 | + is an internal server error. | ||
2203 | HttpStatus: 0 | ||
2204 | |||
2205 | Value: 2804 | ||
2206 | Name: TIP_PICKUP_AMOUNT_CHANGED | ||
2207 | Description: The same pickup ID was already used for picking up a different amount. | ||
2208 | + This points to a very strange internal error as the pickup ID is | ||
2209 | + derived from the denomination key which is tied to a particular | ||
2210 | + amount. Hence this should also be an internal server error. | ||
2211 | HttpStatus: 0 | ||
2212 | |||
2213 | Value: 2805 | ||
2214 | Name: TIP_PICKUP_EXCHANGE_DOWN | ||
2215 | Description: We failed to contact the exchange to obtain the denomination keys. | ||
2216 | + Returned with a response code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2217 | HttpStatus: 424 | ||
2218 | |||
2219 | Value: 2806 | ||
2220 | Name: TIP_PICKUP_EXCHANGE_LACKED_KEYS | ||
2221 | Description: We contacted the exchange to obtain any denomination keys, but got no | ||
2222 | + valid keys. Returned with a response code #MHD_HTTP_FAILED_DEPENDENCY. | ||
2223 | HttpStatus: 424 | ||
2224 | |||
2225 | Value: 2807 | ||
2226 | Name: TIP_PICKUP_EXCHANGE_LACKED_KEY | ||
2227 | Description: We contacted the exchange to obtain at least one of the denomination | ||
2228 | + keys specified in the request. Returned with a response code "not | ||
2229 | + found" (404). | ||
2230 | HttpStatus: 0 | ||
2231 | |||
2232 | Value: 2808 | ||
2233 | Name: TIP_PICKUP_EXCHANGE_AMOUNT_OVERFLOW | ||
2234 | Description: We encountered an arithmetic issue totaling up the amount to withdraw. | ||
2235 | + Returned with a response code of #MHD_HTTP_BAD_REQUEST. | ||
2236 | HttpStatus: 400 | ||
2237 | |||
2238 | Value: 2809 | ||
2239 | Name: TIP_PICKUP_EXCHANGE_TOO_MANY_PLANCHETS | ||
2240 | Description: The number of planchets specified exceeded the limit. Returned with a | ||
2241 | + response code of #MHD_HTTP_BAD_REQUEST. | ||
2242 | HttpStatus: 400 | ||
2243 | |||
2244 | Value: 2810 | ||
2245 | Name: TIP_PICKUP_WITHDRAW_FAILED | ||
2246 | Description: The merchant failed to initialize the withdraw operaiton. Returned | ||
2247 | + with a response code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2248 | HttpStatus: 500 | ||
2249 | |||
2250 | Value: 2811 | ||
2251 | Name: TIP_PICKUP_WITHDRAW_FAILED_AT_EXCHANGE | ||
2252 | Description: The merchant failed to initialize the withdraw operaiton. Returned | ||
2253 | + with a response code of #MHD_HTTP_FAILED_DEPENDENCY. | ||
2254 | HttpStatus: 424 | ||
2255 | |||
2256 | Value: 2812 | ||
2257 | Name: TIP_PICKUP_UNBLIND_FAILURE | ||
2258 | Description: The client failed to unblind the signature returned by the merchant. | ||
2259 | + Generated client-side. | ||
2260 | HttpStatus: 0 | ||
2261 | |||
2262 | Value: 2813 | ||
2263 | Name: GET_TIPS_DB_LOOKUP_ERROR | ||
2264 | Description: Merchant failed to access its database to lookup the tip. Returned | ||
2265 | + with a response code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2266 | HttpStatus: 500 | ||
2267 | |||
2268 | Value: 2814 | ||
2269 | Name: GET_TIPS_ID_UNKNOWN | ||
2270 | Description: Merchant failed find the tip in its database. Returned with a response | ||
2271 | + code of #MHD_HTTP_NOT_FOUND. | ||
2272 | HttpStatus: 404 | ||
2273 | |||
2274 | Value: 2815 | ||
2275 | Name: TIP_PICKUP_CONTACT_EXCHANGE_ERROR | ||
2276 | Description: The merchant failed to contact the exchange. Returned with a response | ||
2277 | + code of #MHD_HTTP_FAILED_DEPENDENCY. | ||
2278 | HttpStatus: 424 | ||
2279 | |||
2280 | Value: 2816 | ||
2281 | Name: TIP_PICKUP_EXCHANGE_KEYS_ERROR | ||
2282 | Description: The merchant failed to obtain keys from the exchange. Returned with a | ||
2283 | + response code of #MHD_HTTP_FAILED_DEPENDENCY. | ||
2284 | HttpStatus: 424 | ||
2285 | |||
2286 | Value: 2817 | ||
2287 | Name: TIP_PICKUP_DB_STORE_HARD_ERROR | ||
2288 | Description: The merchant failed to store data in its own database. Returned with a | ||
2289 | + response code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2290 | HttpStatus: 500 | ||
2291 | |||
2292 | Value: 2818 | ||
2293 | Name: TIP_PICKUP_EXCHANGE_TIMEOUT | ||
2294 | Description: The merchant failed to get a timely response from the exchange. | ||
2295 | + Returned with a response code of #MHD_HTTP_REQUEST_TIMEOUT. | ||
2296 | HttpStatus: 408 | ||
2297 | |||
2298 | Value: 2819 | ||
2299 | Name: TIP_PICKUP_EXCHANGE_ERROR | ||
2300 | Description: The exchange returned a failure code for the withdraw operation. | ||
2301 | + Returned with a response code of #MHD_HTTP_FAILED_DEPENDENCY. | ||
2302 | HttpStatus: 424 | ||
2303 | |||
2304 | Value: 2820 | ||
2305 | Name: TIP_PICKUP_SUMMATION_FAILED | ||
2306 | Description: The merchant failed to add up the amounts to compute the pick up | ||
2307 | + value. Returned with a response code of | ||
2308 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2309 | HttpStatus: 500 | ||
2310 | |||
2311 | Value: 2821 | ||
2312 | Name: TIP_PICKUP_HAS_EXPIRED | ||
2313 | Description: The tip expired. Returned with a response code of #MHD_HTTP_GONE. | ||
2314 | HttpStatus: 410 | ||
2315 | |||
2316 | Value: 2822 | ||
2317 | Name: TIP_PICKUP_AMOUNT_EXCEEDS_TIP_REMAINING | ||
2318 | Description: The requested withdraw amount exceeds the amount remaining to be | ||
2319 | + picked up. Returned with a response code of #MHD_HTTP_BAD_REQUEST. | ||
2320 | HttpStatus: 400 | ||
2321 | |||
2322 | Value: 2823 | ||
2323 | Name: TIP_PICKUP_DB_STORE_SOFT_ERROR | ||
2324 | Description: The merchant failed to store data in its own database. Returned with a | ||
2325 | + response code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2326 | HttpStatus: 500 | ||
2327 | |||
2328 | Value: 2824 | ||
2329 | Name: TIP_PICKUP_DENOMINATION_UNKNOWN | ||
2330 | Description: The merchant did not find the specified denomination key in the | ||
2331 | + exchange's key set. Returned with a response code of | ||
2332 | + #MHD_HTTP_CONFLICT. | ||
2333 | HttpStatus: 409 | ||
2334 | |||
2335 | Value: 2900 | ||
2336 | Name: GET_ORDERS_DB_LOOKUP_ERROR | ||
2337 | Description: We failed to fetch contract terms from our merchant database. The | ||
2338 | + response is provided with HTTP status code | ||
2339 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2340 | HttpStatus: 500 | ||
2341 | |||
2342 | Value: 2901 | ||
2343 | Name: GET_ORDERS_ID_UNKNOWN | ||
2344 | Description: We failed to find the contract terms from our merchant database. The | ||
2345 | + response is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
2346 | HttpStatus: 404 | ||
2347 | |||
2348 | Value: 2902 | ||
2349 | Name: GET_ORDERS_WRONG_CONTRACT | ||
2350 | Description: The contract hash provided by the wallet does not match the order. The | ||
2351 | + response is provided with HTTP status code #MHD_HTTP_FORBIDDEN. | ||
2352 | HttpStatus: 403 | ||
2353 | |||
2354 | Value: 2911 | ||
2355 | Name: CHECK_PAYMENT_DB_FETCH_CONTRACT_TERMS_ERROR | ||
2356 | Description: We failed to contract terms from our merchant database. The response | ||
2357 | + is provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2358 | HttpStatus: 500 | ||
2359 | |||
2360 | Value: 2912 | ||
2361 | Name: CHECK_PAYMENT_DB_FETCH_ORDER_ERROR | ||
2362 | Description: We failed to contract terms from our merchant database. The response | ||
2363 | + is provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2364 | HttpStatus: 500 | ||
2365 | |||
2366 | Value: 2913 | ||
2367 | Name: CHECK_PAYMENT_ORDER_ID_UNKNOWN | ||
2368 | Description: The order id we're checking is unknown, likely the frontend did not | ||
2369 | + create the order first. | ||
2370 | HttpStatus: 0 | ||
2371 | |||
2372 | Value: 2914 | ||
2373 | Name: CHECK_PAYMENT_FAILED_COMPUTE_PROPOSAL_HASH | ||
2374 | Description: Failed computing a hash code (likely server out-of-memory). This | ||
2375 | + response is provided with HTTP status code | ||
2376 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2377 | HttpStatus: 500 | ||
2378 | |||
2379 | Value: 2915 | ||
2380 | Name: CHECK_PAYMENT_SESSION_SIGNATURE_INVALID | ||
2381 | Description: Signature "session_sig" failed to verify. This response is provided | ||
2382 | + with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
2383 | HttpStatus: 400 | ||
2384 | |||
2385 | Value: 2916 | ||
2386 | Name: CHECK_PAYMENT_RESPONSE_MALFORMED | ||
2387 | Description: The response we received from the merchant is malformed. This error is | ||
2388 | + generated client-side. | ||
2389 | HttpStatus: 0 | ||
2390 | |||
2391 | Value: 3000 | ||
2392 | Name: DEPOSIT_CONFIRMATION_SIGNATURE_INVALID | ||
2393 | Description: The signature from the exchange on the deposit confirmation is | ||
2394 | + invalid. Returned with a "400 Bad Request" status code. | ||
2395 | HttpStatus: 0 | ||
2396 | |||
2397 | Value: 3001 | ||
2398 | Name: DEPOSIT_CONFIRMATION_STORE_DB_ERROR | ||
2399 | Description: The auditor had trouble storing the deposit confirmation in its | ||
2400 | + database. Returned with an HTTP status code of | ||
2401 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2402 | HttpStatus: 500 | ||
2403 | |||
2404 | Value: 3002 | ||
2405 | Name: LIST_EXCHANGES_DB_ERROR | ||
2406 | Description: The auditor had trouble retrieving the exchange list from its | ||
2407 | + database. Returned with an HTTP status code of | ||
2408 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2409 | HttpStatus: 500 | ||
2410 | |||
2411 | Value: 3003 | ||
2412 | Name: AUDITOR_EXCHANGE_STORE_DB_ERROR | ||
2413 | Description: The auditor had trouble storing an exchange in its database. Returned | ||
2414 | + with an HTTP status code of #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2415 | HttpStatus: 500 | ||
2416 | |||
2417 | Value: 3004 | ||
2418 | Name: AUDITOR_EXCHANGES_REPLY_MALFORMED | ||
2419 | Description: The auditor (!) responded with a reply that did not satsify the | ||
2420 | + protocol. This error is not used in the protocol but created client- | ||
2421 | + side. | ||
2422 | HttpStatus: 0 | ||
2423 | |||
2424 | Value: 4000 | ||
2425 | Name: TEST_ECDH_ERROR | ||
2426 | Description: The exchange failed to compute ECDH. This response is provided with | ||
2427 | + HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2428 | HttpStatus: 500 | ||
2429 | |||
2430 | Value: 4001 | ||
2431 | Name: TEST_EDDSA_INVALID | ||
2432 | Description: The EdDSA test signature is invalid. This response is provided with | ||
2433 | + HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
2434 | HttpStatus: 400 | ||
2435 | |||
2436 | Value: 4002 | ||
2437 | Name: TEST_EDDSA_ERROR | ||
2438 | Description: The exchange failed to compute the EdDSA test signature. This | ||
2439 | + response is provided with HTTP status code | ||
2440 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2441 | HttpStatus: 500 | ||
2442 | |||
2443 | Value: 4003 | ||
2444 | Name: TEST_RSA_GEN_ERROR | ||
2445 | Description: The exchange failed to generate an RSA key. This response is provided | ||
2446 | + with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2447 | HttpStatus: 500 | ||
2448 | |||
2449 | Value: 4004 | ||
2450 | Name: TEST_RSA_PUB_ERROR | ||
2451 | Description: The exchange failed to compute the public RSA key. This response is | ||
2452 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2453 | HttpStatus: 500 | ||
2454 | |||
2455 | Value: 4005 | ||
2456 | Name: TEST_RSA_SIGN_ERROR | ||
2457 | Description: The exchange failed to compute the RSA signature. This response is | ||
2458 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2459 | HttpStatus: 500 | ||
2460 | |||
2461 | Value: 5000 | ||
2462 | Name: SERVER_JSON_INVALID | ||
2463 | Description: The JSON in the server's response was malformed. This response is | ||
2464 | + provided with HTTP status code of 0. | ||
2465 | HttpStatus: 0 | ||
2466 | |||
2467 | Value: 5001 | ||
2468 | Name: SERVER_SIGNATURE_INVALID | ||
2469 | Description: A signature in the server's response was malformed. This response is | ||
2470 | + provided with HTTP status code of 0. | ||
2471 | HttpStatus: 0 | ||
2472 | |||
2473 | Value: 5102 | ||
2474 | Name: BANK_SAME_ACCOUNT | ||
2475 | Description: Wire transfer attempted with credit and debit party being the same | ||
2476 | + bank account. | ||
2477 | HttpStatus: 0 | ||
2478 | |||
2479 | Value: 5103 | ||
2480 | Name: BANK_UNALLOWED_DEBIT | ||
2481 | Description: Wire transfer impossible, due to financial limitation of the party | ||
2482 | + that attempted the payment. | ||
2483 | HttpStatus: 0 | ||
2484 | |||
2485 | Value: 5104 | ||
2486 | Name: BANK_CURRENCY_MISMATCH | ||
2487 | Description: Arithmetic operation between two amounts of different currency was | ||
2488 | + attempted. | ||
2489 | HttpStatus: 0 | ||
2490 | |||
2491 | Value: 5105 | ||
2492 | Name: BANK_PARAMETER_MISSING_OR_INVALID | ||
2493 | Description: At least one GET parameter was either missing or invalid for the | ||
2494 | + requested operation. | ||
2495 | HttpStatus: 0 | ||
2496 | |||
2497 | Value: 5106 | ||
2498 | Name: BANK_JSON_INVALID | ||
2499 | Description: JSON body sent was invalid for the requested operation. | ||
2500 | HttpStatus: 0 | ||
2501 | |||
2502 | Value: 5107 | ||
2503 | Name: BANK_NEGATIVE_NUMBER_AMOUNT | ||
2504 | Description: Negative number was used (as value and/or fraction) to initiate a | ||
2505 | + Amount object. | ||
2506 | HttpStatus: 0 | ||
2507 | |||
2508 | Value: 5108 | ||
2509 | Name: BANK_NUMBER_TOO_BIG | ||
2510 | Description: A number too big was used (as value and/or fraction) to initiate a | ||
2511 | + amount object. | ||
2512 | HttpStatus: 0 | ||
2513 | |||
2514 | Value: 5109 | ||
2515 | Name: BANK_LOGIN_FAILED | ||
2516 | Description: Could not login for the requested operation. | ||
2517 | HttpStatus: 0 | ||
2518 | |||
2519 | Value: 5110 | ||
2520 | Name: BANK_UNKNOWN_ACCOUNT | ||
2521 | Description: The bank account referenced in the requested operation was not found. | ||
2522 | + Returned along "400 Not found". | ||
2523 | HttpStatus: 0 | ||
2524 | |||
2525 | Value: 5111 | ||
2526 | Name: BANK_TRANSACTION_NOT_FOUND | ||
2527 | Description: The transaction referenced in the requested operation (typically a | ||
2528 | + reject operation), was not found. | ||
2529 | HttpStatus: 0 | ||
2530 | |||
2531 | Value: 5112 | ||
2532 | Name: BANK_BAD_FORMAT_AMOUNT | ||
2533 | Description: Bank received a malformed amount string. | ||
2534 | HttpStatus: 0 | ||
2535 | |||
2536 | Value: 5200 | ||
2537 | Name: BANK_REJECT_NO_RIGHTS | ||
2538 | Description: The client does not own the account credited by the transaction which | ||
2539 | + is to be rejected, so it has no rights do reject it. To be returned | ||
2540 | + along HTTP 403 Forbidden. | ||
2541 | HttpStatus: 0 | ||
2542 | |||
2543 | Value: 5300 | ||
2544 | Name: BANK_UNMANAGED_EXCEPTION | ||
2545 | Description: This error code is returned when no known exception types captured the | ||
2546 | + exception, and comes along with a 500 Internal Server Error. | ||
2547 | HttpStatus: 0 | ||
2548 | |||
2549 | Value: 5400 | ||
2550 | Name: BANK_SOFT_EXCEPTION | ||
2551 | Description: This error code is used for all those exceptions that do not really | ||
2552 | + need a specific error code to return to the client, but need to signal | ||
2553 | + the middleware that the bank is not responding with 500 Internal | ||
2554 | + Server Error. Used for example when a client is trying to register | ||
2555 | + with a unavailable username. | ||
2556 | HttpStatus: 0 | ||
2557 | |||
2558 | Value: 5500 | ||
2559 | Name: BANK_TRANSFER_REQUEST_UID_REUSED | ||
2560 | Description: The request UID for a request to transfer funds has already been used, | ||
2561 | + but with different details for the transfer. | ||
2562 | HttpStatus: 0 | ||
2563 | |||
2564 | Value: 6000 | ||
2565 | Name: SYNC_DB_FETCH_ERROR | ||
2566 | Description: The sync service failed to access its database. This response is | ||
2567 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2568 | HttpStatus: 500 | ||
2569 | |||
2570 | Value: 6001 | ||
2571 | Name: SYNC_BACKUP_UNKNOWN | ||
2572 | Description: The sync service failed find the record in its database. This response | ||
2573 | + is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
2574 | HttpStatus: 404 | ||
2575 | |||
2576 | Value: 6002 | ||
2577 | Name: SYNC_ACCOUNT_UNKNOWN | ||
2578 | Description: The sync service failed find the account in its database. This | ||
2579 | + response is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
2580 | HttpStatus: 404 | ||
2581 | |||
2582 | Value: 6003 | ||
2583 | Name: SYNC_BAD_IF_NONE_MATCH | ||
2584 | Description: The SHA-512 hash provided in the If-None-Match header is malformed. | ||
2585 | + This response is provided with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
2586 | HttpStatus: 400 | ||
2587 | |||
2588 | Value: 6004 | ||
2589 | Name: SYNC_BAD_IF_MATCH | ||
2590 | Description: The SHA-512 hash provided in the If-Match header is malformed or | ||
2591 | + missing. This response is provided with HTTP status code | ||
2592 | + #MHD_HTTP_BAD_REQUEST. | ||
2593 | HttpStatus: 400 | ||
2594 | |||
2595 | Value: 6005 | ||
2596 | Name: SYNC_BAD_SYNC_SIGNATURE | ||
2597 | Description: The signature provided in the "Sync-Signature" header is malformed or | ||
2598 | + missing. This response is provided with HTTP status code | ||
2599 | + #MHD_HTTP_BAD_REQUEST. | ||
2600 | HttpStatus: 400 | ||
2601 | |||
2602 | Value: 6007 | ||
2603 | Name: SYNC_INVALID_SIGNATURE | ||
2604 | Description: The signature provided in the "Sync-Signature" header does not match | ||
2605 | + the account, old or new Etags. This response is provided with HTTP | ||
2606 | + status code #MHD_HTTP_FORBIDDEN. | ||
2607 | HttpStatus: 403 | ||
2608 | |||
2609 | Value: 6008 | ||
2610 | Name: SYNC_BAD_CONTENT_LENGTH | ||
2611 | Description: The "Content-length" field for the upload is either not a number, or | ||
2612 | + too big, or missing. This response is provided with HTTP status code | ||
2613 | + #MHD_HTTP_BAD_REQUEST. | ||
2614 | HttpStatus: 400 | ||
2615 | |||
2616 | Value: 6009 | ||
2617 | Name: SYNC_EXCESSIVE_CONTENT_LENGTH | ||
2618 | Description: The "Content-length" field for the upload is too big based on the | ||
2619 | + server's terms of service. This response is provided with HTTP status | ||
2620 | + code #MHD_HTTP_PAYLOAD_TOO_LARGE. | ||
2621 | HttpStatus: 413 | ||
2622 | |||
2623 | Value: 6010 | ||
2624 | Name: SYNC_OUT_OF_MEMORY_ON_CONTENT_LENGTH | ||
2625 | Description: The server is out of memory to handle the upload. Trying again later | ||
2626 | + may succeed. This response is provided with HTTP status code | ||
2627 | + #MHD_HTTP_PAYLOAD_TOO_LARGE. | ||
2628 | HttpStatus: 413 | ||
2629 | |||
2630 | Value: 6011 | ||
2631 | Name: SYNC_INVALID_UPLOAD | ||
2632 | Description: The uploaded data does not match the Etag. This response is provided | ||
2633 | + with HTTP status code #MHD_HTTP_BAD_REQUEST. | ||
2634 | HttpStatus: 400 | ||
2635 | |||
2636 | Value: 6012 | ||
2637 | Name: SYNC_DATABASE_FETCH_ERROR | ||
2638 | Description: We failed to check for existing upload data in the database. This | ||
2639 | + response is provided with HTTP status code | ||
2640 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2641 | HttpStatus: 500 | ||
2642 | |||
2643 | Value: 6013 | ||
2644 | Name: SYNC_SHUTDOWN | ||
2645 | Description: HTTP server was being shutdown while this operation was pending. This | ||
2646 | + response is provided with HTTP status code | ||
2647 | + #MHD_HTTP_SERVICE_UNAVAILABLE. | ||
2648 | HttpStatus: 503 | ||
2649 | |||
2650 | Value: 6014 | ||
2651 | Name: SYNC_PAYMENT_TIMEOUT | ||
2652 | Description: HTTP server experienced a timeout while awaiting promised payment. | ||
2653 | + This response is provided with HTTP status code | ||
2654 | + #MHD_HTTP_REQUEST_TIMEOUT. | ||
2655 | HttpStatus: 408 | ||
2656 | |||
2657 | Value: 6015 | ||
2658 | Name: SYNC_PAYMENT_CREATE_DB_ERROR | ||
2659 | Description: Sync could not store order data in its own database. This response is | ||
2660 | + provided with HTTP status code #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2661 | HttpStatus: 500 | ||
2662 | |||
2663 | Value: 6016 | ||
2664 | Name: SYNC_PAYMENT_CONFIRM_DB_ERROR | ||
2665 | Description: Sync could not store payment confirmation in its own database. This | ||
2666 | + response is provided with HTTP status code | ||
2667 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2668 | HttpStatus: 500 | ||
2669 | |||
2670 | Value: 6017 | ||
2671 | Name: SYNC_PAYMENT_CHECK_ORDER_DB_ERROR | ||
2672 | Description: Sync could not fetch information about possible existing orders from | ||
2673 | + its own database. This response is provided with HTTP status code | ||
2674 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2675 | HttpStatus: 500 | ||
2676 | |||
2677 | Value: 6018 | ||
2678 | Name: SYNC_PAYMENT_CREATE_BACKEND_ERROR | ||
2679 | Description: Sync could not setup the payment request with its own backend. This | ||
2680 | + response is provided with HTTP status code | ||
2681 | + #MHD_HTTP_INTERNAL_SERVER_ERROR. | ||
2682 | HttpStatus: 500 | ||
2683 | |||
2684 | Value: 6019 | ||
2685 | Name: SYNC_PREVIOUS_BACKUP_UNKNOWN | ||
2686 | Description: The sync service failed find the backup to be updated in its database. | ||
2687 | + This response is provided with HTTP status code #MHD_HTTP_NOT_FOUND. | ||
2688 | HttpStatus: 404 | ||
2689 | |||
2690 | Value: 9999 | ||
2691 | Name: END | ||
2692 | Description: End of error code range. | ||
2693 | HttpStatus: 0 | ||