gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: kyc auth


From: Admin
Subject: [taler-docs] branch master updated: kyc auth
Date: Mon, 02 Jun 2025 16:42:04 +0200

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository taler-docs.

The following commit(s) were added to refs/heads/master by this push:
     new d492f336 kyc auth
d492f336 is described below

commit d492f33650ca4d21c5baed97b3625f8b7740d8a0
Author: Florian Dold <florian@dold.me>
AuthorDate: Mon Jun 2 16:42:01 2025 +0200

    kyc auth
---
 deployments/tops-stage-devtesting.rst | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/deployments/tops-stage-devtesting.rst 
b/deployments/tops-stage-devtesting.rst
index bee3d933..73cd5ce5 100644
--- a/deployments/tops-stage-devtesting.rst
+++ b/deployments/tops-stage-devtesting.rst
@@ -46,6 +46,7 @@ Deposits: Deposit with KYC Auth
 -------------------------------
 
 1. Do a basic withdrawal.
+
 2. Generate an IBAN via:
 
    .. code:: none
@@ -53,6 +54,17 @@ Deposits: Deposit with KYC Auth
       ssh -T devtesting@rusty.taler-ops.ch geniban
 
 3. Initiate a deposit in the wallet UI to the randomly generated IBAN.
-4. The deposit transaction should now ask for KYC information.  Fill out the 
corresponding form(s).
-5. The deposit transaction should finish.
+
+4. The deposit transaction should now ask for a KYC auth transfer.  Satisfy 
the auth transfer by running:
+
+   .. code:: none
+
+      ssh -T devtesting@rusty.taler-ops.ch "fake-incoming --amount $AMOUNT 
--subject '$SUBJECT' --debitor-payto '$DEBITOR_PAYTO'"
+
+  with the information shown in the wallet UI, where the ``$DEBITOR_PAYTO`` 
must contain the IBAN generated in step (2).
+
+
+5. The deposit transaction should now ask for KYC information.  Fill out the 
corresponding form(s).
+
+6. The deposit transaction should finish.
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]