path: root/integration-merchant.rst
diff options
authorMarcello Stanisci <>2016-03-22 20:26:17 +0100
committerMarcello Stanisci <>2016-03-22 20:26:17 +0100
commit256deb70603ddecd59e4d6f06463f1c905bdc88e (patch)
tree42560107e8e2fe98d38b24be9c58404037dda349 /integration-merchant.rst
parent37cdbc1e2b4be69ac7d268b2db220d1c0754973b (diff)
half baking #4169
Diffstat (limited to 'integration-merchant.rst')
1 files changed, 20 insertions, 0 deletions
diff --git a/integration-merchant.rst b/integration-merchant.rst
index 289b9ce..f2f2fc0 100644
--- a/integration-merchant.rst
+++ b/integration-merchant.rst
@@ -1,3 +1,17 @@
+ This file is part of GNU TALER.
+ Copyright (C) 2014, 2015, 2016 INRIA
+ TALER is free software; you can redistribute it and/or modify it under the
+ terms of the GNU General Public License as published by the Free Software
+ Foundation; either version 2.1, or (at your option) any later version.
+ TALER is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+ A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
+ You should have received a copy of the GNU Lesser General Public License along with
+ TALER; see the file COPYING. If not, see <>
+ @author Marcello Stanisci
Interaction with merchant websites
@@ -28,10 +42,14 @@ a physical good on his screen, the user will receive it by mail.
IIG triggers different flows according to the user visiting an offering or a fulfillment
URL. For clarity, below are listed the steps taken when the user visits an offering URL.
+.. _offer:
IIG by `offering` URL
+0. If the state associated to the resource requested is `payed`, go to 7.
1. The merchant sends the following object embedded in a `taler-confirm-contract` event
.. code-block:: tsref
@@ -96,6 +114,8 @@ IIG by `fulfillment` URL
We stress again that the fulfillment URL contains all the information a merchant needs
to reconstruct a contract.
+0. If the state associated to the resource requested is `payed`, go to point 7 above.
1. The user visits a fulfillment URL
2. The merchant replies with the same data structure shown in point 4 above