diff options
Diffstat (limited to 'merchants.html')
-rw-r--r-- | merchants.html | 54 |
1 files changed, 54 insertions, 0 deletions
diff --git a/merchants.html b/merchants.html index 09eece94..4d4bd72b 100644 --- a/merchants.html +++ b/merchants.html | |||
@@ -222,6 +222,60 @@ | |||
222 | fornendo standard aperti e implementazioni di riferimento in free-software.</p> | 222 | fornendo standard aperti e implementazioni di riferimento in free-software.</p> |
223 | </div> | 223 | </div> |
224 | </div> | 224 | </div> |
225 | <div class="col-lg-12"> | ||
226 | <h2 lang="en" id="overview">Taler as seen by merchants</h1> | ||
227 | <h2 lang="de">Taler aus Geschäftssicht</h1> | ||
228 | <h2 lang="fr" note="outdated"></h2> | ||
229 | <h2 lang="it" note="outdated"></h2> | ||
230 | <p lang="en">Merchants supporting the Taler system need to integrate | ||
231 | some relatively simple logic into their transaction processing | ||
232 | system. | ||
233 | Typical steps performed by the merchant system are: | ||
234 | </p> | ||
235 | <p lang="de" note="outdated"></p> | ||
236 | <p lang="fr" note="outdated"></p> | ||
237 | <p lang="it" note="outdated"></p> | ||
238 | <p> | ||
239 | <img src="images/merchant.svg" alt="merchant perspective" style="float: right; margin: 50px 5px 5px 5px;" width="50%"> | ||
240 | <ol> | ||
241 | <li lang="en">The new logic detects when a customer's system | ||
242 | supports Taler and then needs to send a digitally signed | ||
243 | version of the proposed contract in a simple JSON format to | ||
244 | the customer. | ||
245 | The message also includes salted, hashed wire details for | ||
246 | the merchant, as well as restrictions as to which mint operators | ||
247 | the merchant is willing to deal with.</li> | ||
248 | <li lang="de" note="outdated"></li> | ||
249 | <li lang="fr" note="outdated"></li> | ||
250 | <li lang="it" note="outdated"></li> | ||
251 | <li lang="en">The customer sends a signed response which states | ||
252 | that certain digital coins now belong to the merchant to both | ||
253 | signal acceptance of the deal as well as to pay the respective | ||
254 | amount (bottom).</li> | ||
255 | <li lang="de" note="outdated"></li> | ||
256 | <li lang="fr" note="outdated"></li> | ||
257 | <li lang="it" note="outdated"></li> | ||
258 | <li lang="en">The merchant then forwards the signed messages | ||
259 | received from the customer to the mint, together with its | ||
260 | wire details and the salt (without hashing). The mint verifies | ||
261 | the details and sends a signed confirmation (or an error | ||
262 | message) to the merchant. The merchant checks that the | ||
263 | mint's signature is valid, sends a confirmation to the | ||
264 | customer and executes the contract-specific business logic.</li> | ||
265 | <li lang="de" note="outdated"></li> | ||
266 | <li lang="fr" note="outdated"></li> | ||
267 | <li lang="it" note="outdated"></li> | ||
268 | <li lang="en">The mint performs wire transfers corresponding to | ||
269 | the claims deposited by the merchant. Note that the mint may | ||
270 | charge fees for the deposit operation, hence merchants may | ||
271 | impose limits restricting the set of mint operators they are | ||
272 | willing to deal with.</li> | ||
273 | <li lang="de" note="outdated"></li> | ||
274 | <li lang="fr" note="outdated"></li> | ||
275 | <li lang="it" note="outdated"></li> | ||
276 | </ol> | ||
277 | </p> | ||
278 | </div> | ||
225 | <!--# include file="common/footer.inc" --> | 279 | <!--# include file="common/footer.inc" --> |
226 | </div> <!-- /container --> | 280 | </div> <!-- /container --> |
227 | </body> | 281 | </body> |