[taler-docs] branch master updated: Headline inserted

[gnunet]

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

skuegel pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 1bc751e  Headline inserted
1bc751e is described below

commit 1bc751e8448b6f742c1166aa5244187feac6b8a5
Author: Stefan Kügel <skuegel@web.de>
AuthorDate: Wed Jan 13 22:52:24 2021 +0100

    Headline inserted
---
 design-documents/012-fee-schedule-metrics.rst | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/design-documents/012-fee-schedule-metrics.rst 
b/design-documents/012-fee-schedule-metrics.rst
index 0870e15..f4b15a3 100644
--- a/design-documents/012-fee-schedule-metrics.rst
+++ b/design-documents/012-fee-schedule-metrics.rst
@@ -42,7 +42,7 @@ The fee structure and its underlying metrics are also bound 
to rules and expecta
 Fees chosen by Exchange operators have to be explained to the users by means 
of comprehensive Terms and conditions of services that describe the fee types 
and amounts of fees and how they are calculated. Costs for wired amounts within 
the banking system (IBAN transfers to the Exchange's escrow account for the 
withdrawal transaction; IBAN: International Banking Account Number) have to be 
covered by users, so additionally Terms and conditions of their banks may be 
effective, too. These Ter [...]
 
 Obligations of Exchange operators
-------------------------------------
+---------------------------------
 
 Exchange operators have to adhere to the fee schedule. Otherwise they can lose 
their interface access, have their certification revoked and, moreover, even 
become liable for damages. For each transaction type there is one specific fee 
type. Exchange operators set the fee amount. If a fee type is set to a value of 
0, this fee type will not contribute to the operator's income from fees.
 
@@ -61,7 +61,7 @@ Terms and conditions of every Exchange must also clearly 
indicate to the user th
 A private bank that hosts an Exchange and normally charges its customers for 
IBAN transfers has the option of waiving the applicable fees for their 
customers when they withdraw from their own checking accounts into Taler 
wallets.
 
 Buyer's obligations
-----------------------
+-------------------
 
 Prior to making the first withdrawal from an exchange users are required to 
read and confirm the Terms and conditions of the relevant Exchange. This step 
is mandatory when changes to Terms and conditions take place. Users accept 
Terms and conditions by confirming them in the mobile application or on the 
web. Terms and conditions also require users to accept possible losses of funds 
in wallets through 'Refresh' fees, which can be eventually charged by Exchange 
operators.
 
@@ -72,7 +72,7 @@ In accordance with the Terms and conditions, the users agree 
not to make any cla
 Furthermore, according to the Terms and conditions, users must accept that the 
IBAN transfer from the users' personal checking account to the Exchange's 
escrow account may incur costs depending on the contract with their banks. 
These costs are not related to the Taler payment system and cannot be 
influenced by it.
 
 Obligations of merchants/sellers
------------------------------------
+--------------------------------
 
 Normally, a plurality of buyers' spending transactions is summed up to one 
aggregated amount of revenue and wired to the receiving checking account of the 
merchant. Merchants can set the frequency by which these aggregated amounts are 
wired. Every wire transfer imposes costs on the Exchange operator collected by 
the operator's bank for having the amount wired. Therefore, the Exchange 
operator will tend to charge the 'Wire fee' to the sellers for this transaction 
type, as the sellers are  [...]
 
@@ -81,7 +81,7 @@ During the withdrawal process, the wallet shows to the buyer 
the complete fee sc
 Sellers who enter incorrect account data for their own checking account are 
solely liable for any resulting damage and not the Exchange operator. Sellers 
bear the risk of a loss of value or even a total loss of their revenue if they 
enter a wrong IBAN for the transfer of their revenue, although syntactically 
correct. Similarly, the sellers alone bear charges due to an incorrect 
receiving account number or other posting errors that they cause and for which 
manual routing becomes necessary [...]
 
 Technical framework conditions for the collection of fees
-------------------------------------------------------------
+---------------------------------------------------------
 
 Fees are charged per coin or per wire transfer. The number of coins at 
withdrawal usually increases logarithmically with the amount represented. Fees 
can be applied to both flow quantities (e.g. coins moved at withdrawal and 
deposit transactions) and static quantities (e.g. coins stored in wallets). The 
fees on coins may differ depending on the time of issuance of a coin and 
depending on the value of a coin. They are fixed for each coin at its time of 
issuance, and cannot be changed subs [...]
 
@@ -175,7 +175,7 @@ Costs for the closing of a reserve are incurred by the 
Exchange operator due to
 The closing transaction does not affect sellers in any way.
 
 Fee levels in case of misuse
-____________________________
+----------------------------
 
 Normally, the payment process involves the fee types **Withdrawal**, 
**Deposit** and **Wire fee** - when the amount to be paid is settled with a 
coin of the exactly matching denomination. For any other amount for which a 
coin of higher denomination is used, the refresh transaction will generate 
change, i.e. post one or more fresh coins to the wallet until the difference is 
reached.
 
@@ -199,5 +199,7 @@ Discussion / Q&A
 ================
 
 Other documents regarding fee specifications:
+
 * Fee schedule and metrics from the users' point of view :doc:`008-fees`
+
 * Wire fee for different wiring methods (``sepa`` or ``x-taler-wire``) 
<https://docs.taler.net/taler-exchange-manual.html#wire-fee-structure>

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