taler-docs

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

commit 612772b0ac7e8431f9c74dee26b51b9d085e7418
parent d2c183b7c5334d2bd12a59450ede5028d0f4565c
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu,  9 Dec 2021 17:00:14 +0100

iban

Diffstat:
Mtaler-developer-manual.rst | 2+-
Mtaler-exchange-manual.rst | 2+-
Mtaler-exchange-setup-guide.rst | 8++++----
Mtaler-wallet-cli-manual.rst | 2+-
4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/taler-developer-manual.rst b/taler-developer-manual.rst @@ -1690,7 +1690,7 @@ for the Taler exchange or Taler merchants. Print version information. **-w** *WIREFORMAT* \| **--wire** *WIREFORMAT* - Specifies which wire format to use (i.e. “test” or “sepa”) + Specifies which wire format to use (i.e. “x-talerbank” or “iban”) **--bank-uri** Alternative to specify wire configuration to use for the exchange and diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst @@ -711,7 +711,7 @@ Wire fee structure .. index:: wire fee .. index:: fee -For each wire method (“sepa” or “x-taler-wire”) the +For each wire method (“sepa” or “x-taler-bank”) the exchange must know about applicable wire fees. This is also done using the ``taler-exchange-offline`` tool: diff --git a/taler-exchange-setup-guide.rst b/taler-exchange-setup-guide.rst @@ -648,7 +648,7 @@ exchange processes should not have access to this information. enable_debit = yes # Account identifier in the form of an RFC-8905 payto:// URI. - # For SEPA, looks like payto://sepa/$IBAN?receiver-name=$NAME + # For SEPA, looks like payto://iban/$IBAN?receiver-name=$NAME # Make sure to URL-encode spaces in $NAME! payto_uri = @@ -871,9 +871,9 @@ steps involving the offline signing machine must be completed: [root@exchange-offline]# taler-exchange-offline \ sign < sig-request.json > sig-response.json [root@exchange-offline]# taler-exchange-offline \ - enable-account payto://sepa/$IBAN?receiver-name=$NAME > acct-response.json + enable-account payto://iban/$IBAN?receiver-name=$NAME > acct-response.json [root@exchange-offline]# taler-exchange-offline \ - wire-fee 2021 sepa EUR:0 EUR:0 > fee-response.json + wire-fee 2021 iban EUR:0 EUR:0 > fee-response.json [root@exchange-online]# taler-exchange-offline upload < sig-response.json [root@exchange-online]# taler-exchange-offline upload < acct-response.json [root@exchange-online]# taler-exchange-offline upload < fee-response.json @@ -940,7 +940,7 @@ provides this functionality for testing.) .. code-block:: shell-session $ taler-wallet-cli deposit create EUR:5 \ - payto://sepa/$IBAN?receiver-name=Name + payto://iban/$IBAN?receiver-name=Name $ taler-wallet-cli run-pending diff --git a/taler-wallet-cli-manual.rst b/taler-wallet-cli-manual.rst @@ -127,7 +127,7 @@ is functional: # Now, directly deposit coins with the exchange into a target account # (Usually, a payment is made via a merchant. The wallet provides # this functionality for testing.) - $ taler-wallet-cli deposit create EUR:5 payto://sepa/$IBAN + $ taler-wallet-cli deposit create EUR:5 payto://iban/$IBAN # Check if transaction was successful. # (If not, fix issue with exchange and run "run-pending" command again)