taler-docs

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

commit bafaa3e4f58e5f64a7ccc4bdd6f4315e247955fd
parent e7abc4f2119c778a79983d49887a9426de6f0d25
Author: Florian Dold <florian@dold.me>
Date:   Thu,  8 Feb 2024 15:55:28 +0100

-clarifications

Diffstat:
Mcore/intro-bank-apis.rst | 8++++++--
1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/core/intro-bank-apis.rst b/core/intro-bank-apis.rst @@ -67,11 +67,15 @@ QR-Code or link. The wallet generates the cryptographic identifiers required for the withdrawal, allows the user to choose an exchange (the bank may suggest a default one!), -and then submits this information (chose exchange, reserve public key) for the +and then submits this information (chosen exchange, reserve public key) for the respective WOPID to the bank-integration API. -The user can then confirm (or abort!) the withdrawal on their bank account. +The user can then confirm the withdrawal by completing the 2FA of +their bank account for the operation. (Alternatively, the user can abort the operation +in their banking client / 2FA app.) +The wallet can continuously query the status of the withdrawal operation (via +the API address and WOPID). In the Taler wallet app, the user can now always see the accurate status of their withdrawal operation (e.g. bank transfer done, aborted, confirmation/2FA pending).