taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit dd1c2b2ed3fcbb0023741eb36853df43576d5b36
parent 9227c39b417f741f4b4332bec2bb0787d8379477
Author: Florian Dold <florian@dold.me>
Date:   Thu, 16 Feb 2023 21:20:25 +0100

incorporate feedback

Diffstat:
Mdesign-documents/037-wallet-transactions-lifecycle.rst | 9+++------
1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/design-documents/037-wallet-transactions-lifecycle.rst b/design-documents/037-wallet-transactions-lifecycle.rst @@ -143,16 +143,13 @@ States and transitions: * ``[action:abort] => aborting(delete-purse)``: The user aborts the P2P payment. The wallet tries to reclaim money in the purse. * ``[purse-timeout] => aborting(refresh)``: The other party was too slow. * ``[poll-success] => done``: The other party has accepted the payment. - * ``[poll-error] => ??``: The exchange claims that there is a permanent error regarding the purse. XXX: Do we continue - retrying? What do we do? + * ``[poll-error] => aborting(refresh)``: The exchange claims that there is a permanent error regarding the purse. * ``aborting(delete-purse)`` * ``[processed-success] => aborting(refresh)``: The purse was deleted successfully, and refunded coins must be refreshed. - * ``[processed-failed] => ...``: Permanent failure when trying to delete the reserve. - - * If purse is already merged: ``=> done`` - * Otherwise: ``=> failed`` XXX: Do we still try to refresh? + * ``[processed-failed(already-merged)] => done``: The other party claimed the funds faster that we were able to abort. + * ``[processed-failed(other)] => aborting(refresh)``: The exchange reports a permanent error. We still try to refresh. * ``[action:abort-force] => failed``