|
|
I'm not sure I understand the report. |
|
|
The SPA shows incoming in the first table and after the merchant checked the bank account and confirm the transfer the row moves from the first table to the second table. The second table is https://docs.taler.net/core/api-merchant.html#get-[-instances-$INSTANCE]-private-transfers Every row in the first table have the field `expected_transfer_serial_id` which can be used in https://docs.taler.net/core/api-merchant.html#get-[-instances-$INSTANCE]-private-incoming-$ID (Based on the spec) but the second table has `transfer_serial_id` In the way the spec is formulated, this section: ``` Obtain details about an expected incoming wire transfers the backend is anticipating. ID must be the expected_transfer_serial_id from ExpectedTransferDetails ``` The SPA can't use `transfer_serial_id` and there is no way to get the same information from https://docs.taler.net/core/api-merchant.html#get-[-instances-$INSTANCE]-private-incoming-$ID for wire transfer that are already confirmed. Either the spec is confusing or we need some changes to be able to show wire transfer amount calculation and aggregated orders. image.png (87,960 bytes) |
- Anonymous
