View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006363 | Taler | mechant backend | public | 2020-06-03 13:31 | 2021-05-09 19:45 |
| Reporter | Florian Dold | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Summary | 0006363: allow merchants to query more information about the deposit status | ||||
| Description | Quoting from the e-mail discussion: >> I'm not really sure what to do there in practice, as "Taler 1.0" doesn't >> really have any way for the merchant to ask about the status of the >> transfer other than trying to call the exchange. >> > > Well, we do have: > > https://docs.taler.net/core/api-exchange.html#get--deposits-$H_WIRE-$MERCHANT_PUB-$H_CONTRACT_TERMS-$COIN_PUB > > We could easily add a HTTP "Failed Dependency" status code to the API > here and define a message format to indicate details about the problem > to the merchant (and prescribe resolution strategies). > > This would mostly require another taler-exchange-XXX process to _query_ > LibEuFin for R-transactions, *and* a change to the exchange DB schema. > More messy: this will require additional changes to the merchant > backend. Please file a bug on this on Mantis, but I think we should > target Taler v1.5 for this, given the scope of the changes and need for > testing -- and the hopefully reasonably low likelihood of occurrence. At > least I think we should be fine to manually handle the first generation > of complaints for R-transactions, and that might even be better than > trying to automate a process where we may not fully understand all the > ways these things fail in practice. | ||||
| Tags | No tags attached. | ||||
|
|
Some status information is now provided ('wired'), alas automatically querying LibEuFin for transactions as _merchant_ is missing: right now, the merchant has to manually POST incoming transactions to the backend. Writing a taler-merchant-wirewatch tool should be done, but later. |
|
|
DD13 will include the required wire API changes (as we need to change the wire API for DD13 anyway). |
|
|
Discussed with Florian: wire API should NOT be used for this, but a separate libEuFin facade created. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-06-03 13:31 | Florian Dold | New Issue | |
| 2020-06-03 13:31 | Florian Dold | Status | new => assigned |
| 2020-06-03 13:31 | Florian Dold | Assigned To | => Christian Grothoff |
| 2020-07-06 11:00 | Christian Grothoff | Note Added: 0016388 | |
| 2020-07-06 11:00 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2020-07-06 11:00 | Christian Grothoff | Status | assigned => confirmed |
| 2020-07-16 15:16 | Christian Grothoff | Severity | minor => feature |
| 2020-12-20 20:29 | Christian Grothoff | Category | exchange => mechant backend |
| 2020-12-26 17:16 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2020-12-26 17:16 | Christian Grothoff | Status | confirmed => assigned |
| 2021-01-30 23:58 | Christian Grothoff | Status | assigned => confirmed |
| 2021-01-30 23:58 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2021-04-19 19:10 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2021-04-19 19:10 | Christian Grothoff | Status | confirmed => assigned |
| 2021-05-09 13:48 | Christian Grothoff | Note Added: 0017804 | |
| 2021-05-09 19:45 | Christian Grothoff | Note Added: 0017805 |
