taler-docs

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

commit 43a3dca151682b7d64bcdd9872619143dad043d4
parent f50c945d65ea5687b69fe635760346803f00fea3
Author: Florian Dold <florian@dold.me>
Date:   Sat, 22 Apr 2023 20:29:54 +0200

DD37: no p2p (auto-)refunds

Diffstat:
Mdesign-documents/037-wallet-transactions-lifecycle.rst | 8+-------
1 file changed, 1 insertion(+), 7 deletions(-)

diff --git a/design-documents/037-wallet-transactions-lifecycle.rst b/design-documents/037-wallet-transactions-lifecycle.rst @@ -760,7 +760,7 @@ 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 and the purse has now expired. - * ``[poll-success] => pending(refundable)``: The other party has accepted the payment. + * ``[poll-success] => done``: The other party has accepted the payment. * ``[poll-error] => aborting(refresh)``: The exchange claims that there is a permanent error regarding the purse. (FIXME(CG): not clear that this is the best transition! Could also go to ``aborting(refund)`` or ``aborting(delete-purse)``; best choice may depend on the specific error returned.) * ``aborting(delete-purse)`` @@ -786,12 +786,6 @@ States and transitions: * ``[processed-failed] => failed``: Refresh group failed to complete with a permanent error. * ``[action:abort-force] => failed``: The user explicitly asked us to give up and accepted the possible loss of funds. -* ``pending(refundable)`` - - FIXME(CG): I do not understand this state. Left out. Remove? - - * ``[auto-refund-timeout] => done``: FIXME(CG): I do not think we should have auto-refunds with P2P payments. Remove? - * ``done`` The transfer was successful.