1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
<!DOCTYPE html>
<html lang="{{ _('en') }}">
<head>
<meta charset="UTF-8"/>
<title>{{ _("GNU Taler") }} - {{ _("Merchants") }}</title>
<meta name="description" content=""/>
{% include "common/header.j2.inc" %}
</head>
<body>
<div class="container">
{% include "common/navigation.j2.inc" %}
<!-- Jumbotron -->
<div class="jumbotron">
<h1>{{ _("Advantages for merchants") }}</h1>
</div>
<div class="row">
<div class="col-lg-4">
<h2>{{ _("Fast") }}</h2>
<p>{{ _("Processing transactions with Taler is fast, allowing you
to confirm the transaction with your customer virtually immediately.
Your customers will appreciate that they do not have to type in credit
card information and play the "verified by" game. By making payments
significantly more convenient for your customers, you may be able to
use Taler for small transactions that would not work with credit card
payments due to the mental overhead for customers.") }}</p>
</div>
<div class="col-lg-4">
<h2>{{ _("Secure") }}</h2>
<p>{{ _("You never learn sensitive customer information. You need
to ensure that your website provides the correct account information
for your business, and that you correctly validate the payment
confirmations from the Taler exchange. As a result, you will have
cryptographic proof of payment for the specific contracts you entered
with your customers, and cryptographically signed confirmations from
the Taler exchange about the deposits. Taler does not require you to
undergo any particular security audits, processes or procedures, as
you never handle sensitive customer information. Your systems will
have cryptographically signed contracts which you can use in court in
case of disputes.") }}</p>
</div>
<div class="col-lg-4">
<h2>{{ _("Free Software") }}</h2>
<p>{{ _("Taler is free software, and you can use the
liberally-licensed reference code as a starting point to integrate
Taler into your services. To use Taler, you do not need to pay license
fees, and the free software development model will ensure that you can
select from many competent developers to help you with your
integration.") }}</p>
</div>
</div>
<div class="row">
<div class="col-lg-4">
<h2>{{ _("Low Fees") }}</h2>
<p>{{ _("Taler is designed to minimize the work the exchange needs to
perform. Combined with Taler's strong security which prevents fraud,
exchanges can operate with very low overhead and thus low transaction
fees. Given Taler's free software exchange reference implementation,
competition among exchanges will ensure fair, low transaction fees for
merchants.") }}</p>
</div>
<div class="col-lg-4">
<h2>{{ _("Flexible") }}</h2>
<p>{{ _("Taler can be used for different currencies (such as Euros
or US Dollars) and different payment models limited only by what the
exchange supports in its interactions.") }}</p>
</div>
<div class="col-lg-4">
<h2>{{ _("Ethical") }}</h2>
<p>{{ _("Taler does not support tax evasion or money laundering, and is
also not a pyramid scheme or speculative investment. Taler's
protocols are efficient and do not waste energy. Taler encourages
competition by providing an open standard and free software
reference implementations.") }}</p>
</div>
</div>
<div class="col-lg-12">
<h2 id="overview">{{ _("Taler as seen by merchants") }}</h2>
<p>{{ _("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:
") }}</p>
<p>
<img src="{{ url('images/merchant.svg') }}" alt="merchant perspective" style="float: right; margin: 50px 5px 5px 5px;" width="50%">
<ol>
<li>{{ _("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.") }}</li>
<li>{{ _("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).") }}</li>
<li>{{ _("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.") }}</li>
<li>{{ _("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.") }}</li>
</ol>
</p>
</div>
<div class="col-lg-12">
<h2 id="documentation">{{ _("Manuals for merchants") }}</h2>
<p>
</p><ul>
<li>The GNU Taler merchant backend operator tutorial
(<a href="https://docs.taler.net/current/merchant-backend/tutorial.html">html</a>,
<a href="https://docs.taler.net/current/merchant-backend/tutorial.pdf">pdf</a>)</li>
<li>The GNU Taler Web shop integration tutorial (PHP)
(<a href="https://docs.taler.net/current/merchant-shop/php/tutorial.html">html</a>,
<a href="https://docs.taler.net/current/merchant-shop/php/tutorial.pdf">pdf</a>)</li>
</ul>
<p></p>
</div>
{% include "common/footer.j2.inc" %}
</div> <!-- /container -->
</body>
</html>
|