diff options
Diffstat (limited to 'merchants.html.j2')
-rw-r--r-- | merchants.html.j2 | 138 |
1 files changed, 138 insertions, 0 deletions
diff --git a/merchants.html.j2 b/merchants.html.j2 new file mode 100644 index 00000000..dbfd8df6 --- /dev/null +++ b/merchants.html.j2 | |||
@@ -0,0 +1,138 @@ | |||
1 | <html lang="{{ _('en') }}"><head> | ||
2 | <meta charset="utf-8"> | ||
3 | <title>{{ _("GNU Taler") }} - {{ _("Merchants") }}</title> | ||
4 | <meta name="description" content=""> | ||
5 | <!--# include file="common/header.inc" --> | ||
6 | </head> | ||
7 | <body class="en" onload="loadLang();"> | ||
8 | <div class="container"> | ||
9 | <!--# include file="common/navigation.inc" --> | ||
10 | <!-- Jumbotron --> | ||
11 | <div class="jumbotron"> | ||
12 | <h1>{{ _("Advantages for merchants") }}</h1> | ||
13 | </div> | ||
14 | <div class="row"> | ||
15 | <div class="col-lg-4"> | ||
16 | <h2>{{ _("Fast") }}</h2> | ||
17 | |||
18 | <p>{{ _("Processing transactions with Taler is fast, allowing you | ||
19 | to confirm the transaction with your customer virtually immediately. | ||
20 | Your customers will appreciate that they do not have to type in credit | ||
21 | card information and play the "verified by" game. By making payments | ||
22 | significantly more convenient for your customers, you may be able to | ||
23 | use Taler for small transactions that would not work with credit card | ||
24 | payments due to the mental overhead for customers.") }}</p> | ||
25 | </div> | ||
26 | <div class="col-lg-4"> | ||
27 | <h2>{{ _("Secure") }}</h2> | ||
28 | |||
29 | <p>{{ _("You never learn sensitive customer information. You need | ||
30 | to ensure that your website provides the correct account information | ||
31 | for your business, and that you correctly validate the payment | ||
32 | confirmations from the Taler exchange. As a result, you will have | ||
33 | cryptographic proof of payment for the specific contracts you entered | ||
34 | with your customers, and cryptographically signed confirmations from | ||
35 | the Taler exchange about the deposits. Taler does not require you to | ||
36 | undergo any particular security audits, processes or procedures, as | ||
37 | you never handle sensitive customer information. Your systems will | ||
38 | have cryptographically signed contracts which you can use in court in | ||
39 | case of disputes.") }}</p> | ||
40 | </div> | ||
41 | <div class="col-lg-4"> | ||
42 | <h2>{{ _("Free Software") }}</h2> | ||
43 | |||
44 | <p>{{ _("Taler is free software, and you can use the | ||
45 | liberally-licensed reference code as a starting point to integrate | ||
46 | Taler into your services. To use Taler, you do not need to pay license | ||
47 | fees, and the free software development model will ensure that you can | ||
48 | select from many competent developers to help you with your | ||
49 | integration.") }}</p> | ||
50 | </div> | ||
51 | </div> | ||
52 | <div class="row"> | ||
53 | <div class="col-lg-4"> | ||
54 | <h2>{{ _("Low Fees") }}</h2> | ||
55 | |||
56 | <p>{{ _("Taler is designed to minimize the work the exchange needs to | ||
57 | perform. Combined with Taler's strong security which prevents fraud, | ||
58 | exchanges can operate with very low overhead and thus low transaction | ||
59 | fees. Given Taler's free software exchange reference implementation, | ||
60 | competition among exchanges will ensure fair, low transaction fees for | ||
61 | merchants.") }}</p> | ||
62 | </div> | ||
63 | <div class="col-lg-4"> | ||
64 | <h2>{{ _("Flexible") }}</h2> | ||
65 | |||
66 | <p>{{ _("Taler can be used for different currencies (such as Euros | ||
67 | or US Dollars) and different payment models limited only by what the | ||
68 | exchange supports in its interactions.") }}</p> | ||
69 | </div> | ||
70 | <div class="col-lg-4"> | ||
71 | <h2>{{ _("Ethical") }}</h2> | ||
72 | |||
73 | <p>{{ _("Taler does not support tax evasion or money laundering, and is | ||
74 | also not a pyramid scheme or speculative investment. Taler's | ||
75 | protocols are efficient and do not waste energy. Taler encourages | ||
76 | competition by providing an open standard and free software | ||
77 | reference implementations.") }}</p> | ||
78 | </div> | ||
79 | </div> | ||
80 | <div class="col-lg-12"> | ||
81 | <h2 id="overview">{{ _("Taler as seen by merchants") }}</h2> | ||
82 | |||
83 | <p>{{ _("Merchants supporting the Taler system need to integrate | ||
84 | some relatively simple logic into their transaction processing | ||
85 | system. | ||
86 | Typical steps performed by the merchant system are: | ||
87 | ") }}</p> | ||
88 | |||
89 | <p> | ||
90 | <img src="images/merchant.svg" alt="merchant perspective" style="float: right; margin: 50px 5px 5px 5px;" width="50%"> | ||
91 | <ol> | ||
92 | <li>{{ _("The new logic detects when a customer's system | ||
93 | supports Taler and then needs to send a cryptographically signed | ||
94 | version of the proposed contract in a simple JSON format to | ||
95 | the customer. | ||
96 | The message also includes salted, hashed wire details for | ||
97 | the merchant, as well as restrictions as to which exchange operators | ||
98 | the merchant is willing to deal with.") }}</li> | ||
99 | |||
100 | <li>{{ _("The customer sends a signed response which states | ||
101 | that certain digital coins now belong to the merchant to both | ||
102 | signal acceptance of the deal as well as to pay the respective | ||
103 | amount (bottom).") }}</li> | ||
104 | |||
105 | <li>{{ _("The merchant then forwards the signed messages | ||
106 | received from the customer to the exchange, together with its | ||
107 | wire details and the salt (without hashing). The exchange verifies | ||
108 | the details and sends a signed confirmation (or an error | ||
109 | message) to the merchant. The merchant checks that the | ||
110 | exchange's signature is valid, sends a confirmation to the | ||
111 | customer and executes the contract-specific business logic.") }}</li> | ||
112 | |||
113 | <li>{{ _("The exchange performs wire transfers corresponding to | ||
114 | the claims deposited by the merchant. Note that the exchange may | ||
115 | charge fees for the deposit operation, hence merchants may | ||
116 | impose limits restricting the set of exchange operators they are | ||
117 | willing to deal with, for example by imposing a bound on | ||
118 | deposit fees.") }}</li> | ||
119 | </ol> | ||
120 | </p> | ||
121 | </div> | ||
122 | <div class="col-lg-12"> | ||
123 | <h2 id="documentation">{{ _("Manuals for merchants") }}</h2> | ||
124 | <p> | ||
125 | </p><ul> | ||
126 | <li>The GNU Taler merchant backend operator tutorial | ||
127 | (<a href="https://docs.taler.net/current/merchant-backend/tutorial.html">html</a>, | ||
128 | <a href="https://docs.taler.net/current/merchant-backend/tutorial.pdf">pdf</a>)</li> | ||
129 | <li>The GNU Taler Web shop integration tutorial (PHP) | ||
130 | (<a href="https://docs.taler.net/current/merchant-shop/php/tutorial.html">html</a>, | ||
131 | <a href="https://docs.taler.net/current/merchant-shop/php/tutorial.pdf">pdf</a>)</li> | ||
132 | </ul> | ||
133 | <p></p> | ||
134 | </div> | ||
135 | <!--# include file="common/footer.inc" --> | ||
136 | </div> <!-- /container --> | ||
137 | </body> | ||
138 | </html> | ||