From 473887865beb80d10a688d5e36aa843f8346601d Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Tue, 7 Mar 2017 00:45:07 +0100 Subject: revise government page, fix misc i18n issues, fix some style issues --- merchants.html.j2 | 83 +++++++++++++++++++++---------------------------------- 1 file changed, 31 insertions(+), 52 deletions(-) (limited to 'merchants.html.j2') diff --git a/merchants.html.j2 b/merchants.html.j2 index 956a9407..9e94f5a9 100644 --- a/merchants.html.j2 +++ b/merchants.html.j2 @@ -12,10 +12,10 @@ -
+
-

{{ _("Fast") }}

+

{{ _("Fast") }}

{{ _("Processing transactions with Taler is fast, allowing you to confirm the transaction with your @@ -30,7 +30,7 @@

-

{{ _("Secure") }}

+

{{ _("Secure") }}

{{ _("You will have cryptographic proof of payment from the Taler payment service provider. Taler does not @@ -44,7 +44,7 @@

-

{{ _("Free Software") }}

+

{{ _("Free Software") }}

{{ _("Taler is free software, and you can use the liberally-licensed reference code as a starting @@ -58,7 +58,7 @@

-

{{ _("Low Fees") }}

+

{{ _("Low Fees") }}

{{ _("Taler is designed to minimize the work the exchange needs to perform. Combined with Taler's strong @@ -68,7 +68,7 @@

-

{{ _("Flexible") }}

+

{{ _("Flexible") }}

{{ _("Taler can be used for different currencies (such as Euros, US Dollars or Bitcoins) and different @@ -78,7 +78,7 @@

-

{{ _("Ethical") }}

+

{{ _("Ethical") }}

{{ _("Taler prevents tax evasion and money laundering. Taler's protocols are efficient and do not waste @@ -112,54 +112,33 @@

-
-

{{ _("Taler as seen by merchants") }}

- -

{{ _("Merchants supporting the Taler system need to - integrate some relatively simple logic into their - transaction processing system. Typical steps - performed by the merchant system are: ") }}

+
+

{{ _("The GNU Taler Merchant Backend") }}

+

{{ _("Merchants process payments using the Taler backend:") }}

- merchant perspective -

    - -
  1. {{ _("The new logic detects when a customer's system - supports Taler and then needs to send a - cryptographically signed version of the proposed - contract in a simple JSON format to the - customer. The message also includes salted, - hashed wire details for the merchant, as well as - restrictions as to which exchange operators the - merchant is willing to deal with.") }}
  2. - -
  3. {{ _("The customer sends a signed response which - states that certain digital coins now belong to - the merchant to both signal acceptance of the - deal as well as to pay the respective amount - (bottom).") }}
  4. - -
  5. {{ _("The merchant then forwards the signed messages - received from the customer to the exchange, - together with its wire details and the salt - (without hashing). The exchange verifies the - details and sends a signed confirmation (or an - error message) to the merchant. The merchant - checks that the exchange's signature is valid, - sends a confirmation to the customer and - executes the contract-specific business - logic.") }}
  6. - -
  7. {{ _("The exchange performs wire transfers - corresponding to the claims deposited by the - merchant. Note that the exchange may charge - fees for the deposit operation, hence merchants - may impose limits restricting the set of - exchange operators they are willing to deal - with, for example by imposing a bound on - deposit fees.") }}
  8. -
+
    + +
  • {{ _("The backend signs and stores + proposals made by the merchant to customers. + For this, the merchant's frontend needs to give the + customer's order in a JSON format to the backend.") }}
  • + +
  • {{ _("The backend validates and executes + payments received from the wallet. The frontend + must pass the payment request through to the backend + and checks the HTTP status code that is returned.") }}
  • + +
  • {{ _("The backend can list completed transactions + and map aggregated wire transfers to individual + business transactions including the exact terms of + the contract.") }}
  • + +

+
+ customer perspective +
{% endblock body_content %} -- cgit v1.2.3