commit 82dcb7c6566242da99695d4272b995b4cdfec141
parent c1f3909466600345488557e2cee9ac638a4a2a31
Author: Stefan Kügel <skuegel@web.de>
Date: Wed, 13 Jan 2021 15:10:38 +0100
Added internal links in the doc, applied markup
Diffstat:
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/design-documents/012-fee-schedule-metrics.rst b/design-documents/012-fee-schedule-metrics.rst
@@ -24,16 +24,16 @@ Proposed Solution
The Taler protocol offers the following fee types:
-1. **Withdrawal**: For each successful withdrawal from the checking account, per coin
-2. **Deposit**: For spending, per coin
-3. **Refresh**: Per coin for
+1. **Withdrawal**: For each successful withdrawal from the checking account, **per coin**
+2. **Deposit**: For spending, **per coin**
+3. **Refresh**: **Per coin** for
a. Refresh transactions for receiving change
b. Refresh of coins at the end of their validity
c. Abort of transactions due to network failure
d. Refund
4. **Refund**: For refunds or in case of contract cancellation by seller, per coin
-5. **Wire fee**: For aggregated amounts wired by the Exchange to the merchant's checking account, per wire transfer
-6. **Closing**: In case a withdrawal process could not be accomplished (the user's wallet did not withdraw the value from the reserve), per wire transfer from the Exchange's escrow account to the account of origin
+5. **Wire fee**: For aggregated amounts wired by the Exchange to the merchant's checking account, **per wire transfer**
+6. **Closing**: In case a withdrawal process could not be accomplished (the user's wallet did not withdraw the value from the reserve), **per wire transfer** from the Exchange's escrow account to the account of origin
Fee schedule
============
@@ -104,7 +104,7 @@ Anyone who wants to load Taler wallets with coins must initiate a wire transfer
* **Withdrawal** from the Exchange operator's point of view:
-A fee on each coin generated would indeed affect all electronic coins withdrawn from an exchange operator and allocate costs necessary for their generation over all coins signed for the first time, but would not prevent abuse through other transactions like intentionally often-triggered refresh or refund, and would also discriminate against those users who withdraw and deposit many smaller denominations. Furthermore, buyers using coins with higher denominations could increase the exchange operator's costs by increasing refresh transactions. Overall, the cost increases are marginally small, though.
+A fee on each coin generated would indeed affect all electronic coins withdrawn from an Exchange operator and allocate costs necessary for their generation over all coins signed for the first time, but would not prevent abuse through other transactions like intentionally often-triggered refresh or refund, and would also discriminate against those users who withdraw and deposit many smaller denominations. Furthermore, buyers using coins with higher denominations could increase the Exchange operator's costs by increasing refresh transactions. Overall, the cost increases are marginally small, though.
* **Withdrawal** from the seller's point of view:
@@ -188,3 +188,7 @@ Drawbacks
Discussion / Q&A
================
+
+We should insert pointers to other design documents regarding fee specifications in our documentation:
+:doc:`008-fees`
+<https://docs.taler.net/taler-exchange-manual.html#wire-fee-structure>
