[taler-docs] branch master updated: fix exchange-account documentation (#5642)

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 319426f  fix exchange-account documentation (#5642)
319426f is described below

commit 319426f3cea657aea0e211c2e771cd5e61bc9a7f
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Aug 28 23:42:44 2020 +0200

    fix exchange-account documentation (#5642)
---
 taler-exchange-manual.rst | 39 +++++++++++++++++++++++----------------
 1 file changed, 23 insertions(+), 16 deletions(-)

diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index 703b326..6e4bae8 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -421,18 +421,18 @@ Bank account
 To configure a bank account in Taler, we need to furnish four pieces of
 information:
 
--  The ``payto://`` URL of the bank account, which uniquely idenfies the
-   account. Examples for such URLs include
-   ``payto://sepa/CH9300762011623852957`` for a bank account in the
-   single European payment area (SEPA) or
+-  The ``payto://`` URI of the bank account, which uniquely idenfies the
+   account. Examples for such URIs include
+   ``payto://iban/CH9300762011623852957`` for a bank account with
+   an IBAN or
    ``payto://x-taler-bank/localhost:8080/2`` for the 2nd bank account a
    the Taler bank demonstrator running at ``localhost`` on port 8080.
-   The first part of the URL following ``payto://`` (“sepa” or
+   The first part of the URI following ``payto://`` (“iban” or
    “x-taler-bank”) is called the wire method.
 
--  A file containing the signed JSON-encoded bank account details for
-   the /wire API. This is necessary as Taler supports offline signing
-   for bank accounts for additional security.
+-  A the name of a file containing the signed JSON-encoded bank account
+   details for the /wire API. This is necessary as Taler supports offline
+   signing for bank accounts for additional security.
 
 -  Finally, the exchange needs to be provided resources for authentication
    to the respective banking service. The format in which the
@@ -440,19 +440,26 @@ information:
    for HTTP basic authentication, or nothing for the fakebank.
 
 You can configure multiple accounts for an exchange by creating sections
-starting with “account-” for the section name. You can ENABLE for each
-account whether it should be used, and for what (incoming or outgoing
+starting with “exchange-account-” for the section name. You can ENABLE for
+each account whether it should be used, and for what (incoming or outgoing
 wire transfers):
 
 ::
 
-   [account-1]
-   URL = "payto://sepa/CH9300762011623852957"
+   [exchange-account-1]
+   # With x-taler-bank (say for PyBank)
+   PAYTO_URI = "payto://x-taler-bank/bank.demo.taler.net/Exchange"
+
+   # Example using IBAN (for use with LibEuFin)
+   # PAYTO_URI = "payto://iban/CH9300762011623852957"
+
+   # Where the JSON with the signature is stored. Can be
+   # generated using taler-exchange-wire tool using
+   # this configuration on a system with the private master key.
    WIRE_RESPONSE = ${TALER_CONFIG_HOME}/account-1.json
 
-   # Wire method supported for merchants, i.e. "IBAN" or
-   # "x-taler-bank"
-   METHOD = <method>
+   # URL for talking to the bank wire the wire API.
+   WIRE_GATEWAY_URL = https://bank.demo.taler.net/taler-wire-gateway/Exchange
 
    # Use for exchange-aggregator (outgoing transfers)
    ENABLE_DEBIT = YES
@@ -461,7 +468,7 @@ wire transfers):
 
    # Authentication options for exchange bank account go here.
    # (Next sections have examples of authentication mechanisms)
-   TALER_BANK_AUTH_METHOD = basic
+   WIRE_GATEWAY_AUTH_METHOD = basic
    USERNAME = exchange
    PASSWORD = super-secure
 

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