taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 7389c3226c3ecd836e4a001f072c5d70491ca908
parent e657aaa26546082be601259d22f81c57a0e9ad19
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date:   Wed,  7 Sep 2016 11:24:12 +0200

addressing FIXMEs

Diffstat:
Mexample-essay-store.rst | 12+++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/example-essay-store.rst b/example-essay-store.rst @@ -36,9 +36,15 @@ In particular, the offer URLs have the following format: `https://blog.demo.taler.net/essay/article_title` -The offer URLs trigger the expected interaction with the wallet. - FIXME: describe where the contract is generated! - FIXME: give the pay URL. +The offer URLs trigger the expected interaction with the wallet. In practical terms, the +offer URL returns a HTML page that can either show a pay-form in case Taler is not installed +in the user's browser or download the contract from the merchant. +If the user has Taler installed and wants to pay, the wallet will POST the coins to a URL +of the form: + `https://blog.demo.taler.net/pay?uuid=${contract_hashcode}` +The URL comes with the contract's hashcode because each contract is an entry in +the merchant's state, so it can mark it as ``payed`` whenever it receives coins. + For the essay store, the fulfillment URL matches the initial part of an offer URL, but contains the additional parameters needed to