View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009169 | Taler | specification | public | 2024-09-04 17:02 | 2024-09-06 15:47 |
| Reporter | sebasjm | Assigned To | Christian Grothoff | ||
| Priority | high | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.14 | Fixed in Version | 0.14 | ||
| Summary | 0009169: not clear what happen when the merchant gets 451 on /deposit [2d] | ||||
| Description | when a wallet tries to pay an order but the merchant needs to complete kyc first. 1.- it should be clear the response code here https://docs.taler.net/core/api-merchant.html#post-[-instances-$INSTANCE]-orders-$ORDER_ID-pay so the wallet can show enough information to know that the merchant is the one that need to complete kyc, and then try again 2.- define what do we want to show to the wallet user the transaction failed, but the problem is transient since it can be repeated again and succeed 3.- merchant spa should show information about the current kyc status, so it can do the KYC way before hitting the limit (very bad case) and complete the kyc process 4.- consider offline point of sale, there could be situations that the merchant won't be able to complete kyc | ||||
| Tags | No tags attached. | ||||
|
|
If we get a 451 on /deposit, we need to: 1) give the SPA an indication that KYC is required so that the merchant backend can prompt for KYC for the failing exchange; 2) return a new error to the wallet 3) so that the wallet can refresh the coins that could not be deposited, and 4a) the wallet MAY then choose to pay with coins from another exchange if available (goto 1), or 4b) the wallet tells the user "sorry, merchant didn't do their KYC yet, cannot pay |
|
|
And yes, the spec is missing in the API, and the merchant backend doesn't implement any of this yet. |
|
|
088dc2bc33d1b26f692bc1665eba69e1afd753d2 contains merchant protocol v17 with the respective specification updates. Note: not yet implemented! |
|
|
Spec is done, let's call #9052 the bug for the implementation in the SPA ;-). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-09-04 17:02 | sebasjm | New Issue | |
| 2024-09-04 17:02 | sebasjm | Status | new => assigned |
| 2024-09-04 17:02 | sebasjm | Assigned To | => Christian Grothoff |
| 2024-09-04 17:04 | Christian Grothoff | Product Version | 1.4 => git (master) |
| 2024-09-04 17:05 | sebasjm | Description Updated | |
| 2024-09-04 17:07 | Christian Grothoff | Note Added: 0023160 | |
| 2024-09-04 17:08 | Christian Grothoff | Note Added: 0023161 | |
| 2024-09-05 13:39 | Christian Grothoff | Summary | not clear what happen when the merchant gets 451 on /deposit => not clear what happen when the merchant gets 451 on /deposit [2d] |
| 2024-09-05 16:13 | Christian Grothoff | Note Added: 0023178 | |
| 2024-09-06 15:47 | Christian Grothoff | Status | assigned => resolved |
| 2024-09-06 15:47 | Christian Grothoff | Resolution | open => fixed |
| 2024-09-06 15:47 | Christian Grothoff | Fixed in Version | => 0.14 |
| 2024-09-06 15:47 | Christian Grothoff | Note Added: 0023208 |
