View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008000 | Taler | exchange | public | 2023-12-06 11:42 | 2024-04-15 21:33 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | high | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.10 | Fixed in Version | 0.10 | ||
| Summary | 0008000: return more information about exchange bank accounts | ||||
| Description | We should allow the exchange to return the name of its bank (for users wanting to select exchange accounts by bank) and also allow the specification of an order in which the exchange bank accounts should be listed (so that the exchange operator can control which bank account will be shown to users first). | ||||
| Tags | No tags attached. | ||||
| child of | 0008619 | closed | Florian Dold | wallet-core should pass new exchange bank account display hints to UIs |
|
|
So something like: struct WithdrawalExchangeAccountDetails: Decodable { var bank_name: String var payto_uri: String var transfer_amount: Amount var credit_restrictions: [AccountRestriction]? } (the order could be implied by the order in the array). |
|
|
Could the name not be made part of the payto URI? I don't see why this would necessarily have to be a separate field. Preserving the order could make sense, then the exchange only has to deal with priority numbers internally. We might also want a flag to indicate whether an account is even meant for manual withdrawal. In the NETZBON deployment, I'm not sure how much sense it would make to offer the NETZBON account of the exchange as an option for manual withdrawal. But it should still be present for bank-integrated withdrawal, thus it needs to be part of the wire info. |
|
|
It could be, and I'm not sure what is the best solution yet. We have the receiver-name already, so bank-name is certainly a plausible extension that would be coherent with what we have so far. For accounts not meant for manual withdrawal, we always have the DENY option in credit_restrictions; do we need debit_restrictions? That said, for Netzbon, all accounts are fully intended to be used. |
|
|
If users have accounts at multiple banks, choosing the 'most suitable' bank of the exchange to wire-transfer the money to is highly desired as long as SEPA Instant Payments still cost fees (e.g. my bank charges €1.50). That's also why most bigger companies have multiple bank accounts printed on their invoices, to let the payer choose. I don't care if the bank name is encoded in the paytoURI or a separate field in the exchange account details - but isn't payto a standard already (RFC 8905)? Do you really want to change that? Banks implementing RFC 8905 do not need the receiver bank name since THEY know how to get that from the IBAN - but we don't, thus we need it. ==> I would implement this outside of the paytoURI. |
|
|
API v19 spec: c0dcafaa..dedcfc66 |
|
|
1beb3e72..19c368fc implements support in taler-exchange-httpd and libtalerexchange. |
|
|
19c368fc..2a254b75 implements the remaining taler-exchange-offline functionality. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-12-06 11:42 | Christian Grothoff | New Issue | |
| 2023-12-06 11:42 | Christian Grothoff | Status | new => assigned |
| 2023-12-06 11:42 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2023-12-06 11:43 | Christian Grothoff | Note Added: 0020732 | |
| 2023-12-06 11:43 | Christian Grothoff | Note Edited: 0020732 | |
| 2023-12-12 20:34 | Florian Dold | Note Added: 0020743 | |
| 2023-12-13 04:55 | Christian Grothoff | Note Added: 0020745 | |
| 2023-12-13 15:08 | MarcS | Note Added: 0020751 | |
| 2023-12-23 14:38 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2023-12-23 14:38 | Christian Grothoff | Status | assigned => confirmed |
| 2024-03-08 20:26 | Christian Grothoff | Relationship added | has duplicate 0008615 |
| 2024-03-08 20:26 | Christian Grothoff | Target Version | post-1.0 => 0.10 |
| 2024-03-08 20:26 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2024-03-08 20:26 | Christian Grothoff | Status | confirmed => assigned |
| 2024-03-08 22:27 | Christian Grothoff | Note Added: 0021817 | |
| 2024-03-08 22:38 | Christian Grothoff | Priority | normal => high |
| 2024-03-08 22:54 | Christian Grothoff | Note Added: 0021818 | |
| 2024-03-08 23:18 | Christian Grothoff | Note Added: 0021819 | |
| 2024-03-08 23:19 | Christian Grothoff | Relationship added | child of 0008619 |
| 2024-03-08 23:20 | Christian Grothoff | Status | assigned => resolved |
| 2024-03-08 23:20 | Christian Grothoff | Resolution | open => fixed |
| 2024-03-08 23:20 | Christian Grothoff | Fixed in Version | => 0.10 |
| 2024-03-08 23:23 | Christian Grothoff | Relationship deleted | has duplicate 0008615 |
| 2024-04-15 21:33 | Christian Grothoff | Status | resolved => closed |
