From acead6d4316a1937b44865c5617145b4be1516db Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:13:12 -0500 Subject: add blank line between term and explanation for ‘frontend’, ‘backend’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 1449c9f8..fccac512 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -79,6 +79,7 @@ The Taler software stack for a merchant consists of the following main components: - frontend + A frontend which interacts with the customer’s browser. The frontend enables the customer to build a shopping cart and place an order. Upon payment, it triggers the respective business logic to satisfy @@ -87,6 +88,7 @@ components: develop a Taler frontend. - backend + A Taler-specific payment backend which makes it easy for the frontend to process financial transactions with Taler. For this tutorial, you will use a public sandbox backend. For production use, you must -- cgit v1.2.3 From 39bc96b0bac4cc3291bda81d78a2a5f437b5c2da Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:20:32 -0500 Subject: use semicolon instead of comma --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index fccac512..208144b4 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -212,7 +212,7 @@ Format <#The-Taler-Order-Format>`__. When POSTing an order, you can also specify additional details such as an override for the refund duration and instructions for inventory management. These are rarely needed and not covered in this -tutorial, please read the :doc:`core/api-merchant` reference +tutorial; please read the :doc:`core/api-merchant` reference manual for details. A minimal Python snippet for creating an order would look like this: -- cgit v1.2.3 From 483b8bf659ec8bc714446fea448fa774909a327b Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:23:42 -0500 Subject: delete unfinished sentence fragment --- taler-merchant-api-tutorial.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 208144b4..c016508e 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -271,8 +271,7 @@ Given the order ID, the status of a payment can be checked with the by the customer, ``/private/orders/$ORDER_ID`` will give the frontend a URL (under the name ``payment_redirect_url``) that will trigger the customer’s wallet to execute the payment. This is basically the -``https://example.com/orders/$ORDER_ID/`` URL we discussed above. Note -that +``https://example.com/orders/$ORDER_ID/`` URL we discussed above. Note that the best way to obtain the ``payment_redirect_url`` is to check the status of the payment, even if you know that the user did not pay yet. There -- cgit v1.2.3 From ca225f997ce68401c33a074609ee03f0c149187f Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:30:33 -0500 Subject: mark up ‘taler://’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index c016508e..adf3f021 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -380,7 +380,7 @@ may then want to read it on a different device, possibly one that does not even have a Taler wallet installed. Naturally, at this point the customer would at first still be prompted to pay -for the article again. If the customer then opens the taler://-link in the +for the article again. If the customer then opens the ``taler://`` link in the wallet that did previously pay for the article (for example by scanning the QR code on the desktop with the Android App), the wallet will claim the contract, detect that the fulfillment URL is identical to one that it already has made a -- cgit v1.2.3 From 7bb54b26f81074704f2637e6909e9b5fd88e7276 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:35:50 -0500 Subject: add comma --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index adf3f021..a721a5e1 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -494,7 +494,7 @@ be paid for exactly the same product by each customer. Taler supports this model by allowing the mechant to check whether the “payment receipt” is available on the user’s current device. This prevents users from easily sharing media access by transmitting a link to the -fulfillment page. Of course sophisticated users could share payment +fulfillment page. Of course, sophisticated users could share payment receipts as well, but this is not as easy as sharing a link, and in this case they are more likely to just share the media directly. -- cgit v1.2.3 From a4ae813f68e49b3a846480f425a353e538ce6490 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:42:47 -0500 Subject: move ‘.. index::’ lines prior to their referrent (15 instances) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 41 ++++++++++++++++++++++++++--------------- 1 file changed, 26 insertions(+), 15 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index a721a5e1..2f3ce112 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -551,26 +551,31 @@ describes each of the fields in depth. Financial amounts are always specified as a string in the format ``"CURRENCY:DECIMAL_VALUE"``. +.. index:: amount amount Specifies the total amount to be paid to the merchant by the customer. - .. index:: amount + +.. index:: fees +.. index:: maximum deposit fee max_fee This is the maximum total amount of deposit fees that the merchant is willing to pay. If the deposit fees for the coins exceed this amount, the customer has to include it in the payment total. The fee is specified using the same triplet used for amount. - .. index:: fees - .. index:: maximum deposit fee + +.. index:: fees +.. index:: maximum wire fee max_wire_fee Maximum wire fee accepted by the merchant (customer share to be divided by the ’wire_fee_amortization’ factor, and further reduced if deposit fees are below ’max_fee’). Default if missing is zero. - .. index:: fees - .. index:: maximum wire fee + +.. index:: fees +.. index:: maximum fee amortization wire_fee_amortization Over how many customer transactions does the merchant expect to @@ -581,35 +586,39 @@ wire_fee_amortization ’max_fee’ and the sum of the actual deposit fees. Optional, default value if missing is 1. 0 and negative values are invalid and also interpreted as 1. - .. index:: fees - .. index:: maximum fee amortization + +.. index:: pay_url pay_url Which URL accepts payments. This is the URL where the wallet will POST coins. - .. index:: pay_url + +.. index:: fulfillment URL fulfillment_url Which URL should the wallet go to for obtaining the fulfillment, for example the HTML or PDF of an article that was bought, or an order tracking system for shipments, or a simple human-readable Web page indicating the status of the contract. - .. index:: fulfillment URL + +.. index:: order ID order_id Alphanumeric identifier, freely definable by the merchant. Used by the merchant to uniquely identify the transaction. - .. index:: order ID + +.. index:: summary summary Short, human-readable summary of the contract. To be used when displaying the contract in just one line, for example in the transaction history of the customer. - .. index:: summary timestamp Time at which the offer was generated. +.. index:: payment deadline + pay_deadline Timestamp of the time by which the merchant wants the exchange to definitively wire the money due from this contract. Once this @@ -618,7 +627,8 @@ pay_deadline payment for them. Amounts will be rounded down to the wire transfer unit; if the total amount is still below the wire transfer unit, it will not be disbursed. - .. index:: payment deadline + +.. index:: refund deadline refund_deadline Timestamp until which the merchant willing (and able) to give refunds @@ -627,12 +637,12 @@ refund_deadline the merchant will be able to sign a message to trigger a refund to the customer. After this time, it will no longer be possible to refund the customer. Must be smaller than the pay_deadline. - .. index:: refund deadline products Array of products that are being sold to the customer. Each entry contains a tuple with the following values: - .. index:: product description + +.. index:: product description description Description of the product. @@ -690,6 +700,8 @@ merchant This should give a label in the locations map, specifying the jurisdiction under which this contract is to be arbitrated. +.. index:: location + locations Associative map of locations used in the contract. Labels for locations in this map can be freely chosen and used whenever a @@ -698,7 +710,6 @@ locations the customer or the merchant), it only needs to be listed (and transmitted) once, and can otherwise be referred to via the label. A non-exhaustive list of location attributes is the following: - .. index:: location name receiver name for delivery, either business or person name. -- cgit v1.2.3 From 66753db5e3fa3ab725689c4161ba33b2d515dc44 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:55:42 -0500 Subject: mark up ‘amount’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 2f3ce112..ef3c0092 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -564,7 +564,7 @@ max_fee This is the maximum total amount of deposit fees that the merchant is willing to pay. If the deposit fees for the coins exceed this amount, the customer has to include it in the payment total. The fee is - specified using the same triplet used for amount. + specified using the same triplet used for ``amount``. .. index:: fees .. index:: maximum wire fee -- cgit v1.2.3 From 1e9564d210b703f766cbaeac4c000ed1fe90e98b Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:57:42 -0500 Subject: change markup from U+2018,U+2019 to double-backticks: ‘wire_fee_amortization’, ‘max_fee’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index ef3c0092..62a7b832 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -571,8 +571,8 @@ max_fee max_wire_fee Maximum wire fee accepted by the merchant (customer share to be - divided by the ’wire_fee_amortization’ factor, and further reduced if - deposit fees are below ’max_fee’). Default if missing is zero. + divided by the ``wire_fee_amortization`` factor, and further reduced if + deposit fees are below ``max_fee``). Default if missing is zero. .. index:: fees .. index:: maximum fee amortization -- cgit v1.2.3 From a8f7721ec03d214bc79e5ed615d962cca020498e Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:59:14 -0500 Subject: change markup from U+2018,U+2019 to double-backticks: ‘max_wire_fee’, ‘max_fee’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 62a7b832..9e42501f 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -580,10 +580,10 @@ max_wire_fee wire_fee_amortization Over how many customer transactions does the merchant expect to amortize wire fees on average? If the exchange’s wire fee is above - ’max_wire_fee’, the difference is divided by this number to compute + ``max_wire_fee``, the difference is divided by this number to compute the expected customer’s contribution to the wire fee. The customer’s contribution may further be reduced by the difference between the - ’max_fee’ and the sum of the actual deposit fees. Optional, default + ``max_fee`` and the sum of the actual deposit fees. Optional, default value if missing is 1. 0 and negative values are invalid and also interpreted as 1. -- cgit v1.2.3 From 1a7c61a3e53314f34a6e0889021ba4f990aaf082 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 20:59:54 -0500 Subject: s/0/Zero/ at beginning of sentence --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 9e42501f..d276d072 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -584,7 +584,7 @@ wire_fee_amortization the expected customer’s contribution to the wire fee. The customer’s contribution may further be reduced by the difference between the ``max_fee`` and the sum of the actual deposit fees. Optional, default - value if missing is 1. 0 and negative values are invalid and also + value if missing is 1. Zero and negative values are invalid and also interpreted as 1. .. index:: pay_url -- cgit v1.2.3 From b8a92c3efe1daf7aa58d652397877ddf8d0c2202 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:02:31 -0500 Subject: mark up ‘refund_deadline’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index d276d072..2f2f6eac 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -623,7 +623,7 @@ pay_deadline Timestamp of the time by which the merchant wants the exchange to definitively wire the money due from this contract. Once this deadline expires, the exchange will aggregate all deposits where the - contracts are past the refund_deadline and execute one large wire + contracts are past the ``refund_deadline`` and execute one large wire payment for them. Amounts will be rounded down to the wire transfer unit; if the total amount is still below the wire transfer unit, it will not be disbursed. -- cgit v1.2.3 From d987b2f5b05b6cf04ea6f5947c23fe1c669c78f2 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:03:22 -0500 Subject: mark up ‘pay_deadline’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 2f2f6eac..66e0dc9f 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -636,7 +636,7 @@ refund_deadline the payment in escrow at least until this deadline. Until this time, the merchant will be able to sign a message to trigger a refund to the customer. After this time, it will no longer be possible to - refund the customer. Must be smaller than the pay_deadline. + refund the customer. Must be smaller than the ``pay_deadline``. products Array of products that are being sold to the customer. Each entry -- cgit v1.2.3 From 6007c9edd51ce53823549491e6238d7ac12c02f4 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:05:09 -0500 Subject: add ‘e.g.’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 66e0dc9f..3efa549e 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -648,7 +648,7 @@ products Description of the product. quantity - Quantity of the items to be shipped. May specify a unit (``1 kg``) + Quantity of the items to be shipped. May specify a unit (e.g. ``1 kg``) or just the count. price -- cgit v1.2.3 From 1f88639332cf73b4629dceeffc2eaca8d958a1fb Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:06:06 -0500 Subject: mark up ‘delivery_location’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 3efa549e..0880ee97 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -653,7 +653,7 @@ products price Price for quantity units of this product shipped to the given - delivery_location. Note that usually the sum of all of the prices + ``delivery_location``. Note that usually the sum of all of the prices should add up to the total amount of the contract, but it may be different due to discounts or because individual prices are unavailable. -- cgit v1.2.3 From d67f99c7bad7259064de93199a7556eb12c942a7 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:13:47 -0500 Subject: indent ‘.. index::’ for "product description" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 0880ee97..7fd1e054 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -642,7 +642,7 @@ products Array of products that are being sold to the customer. Each entry contains a tuple with the following values: -.. index:: product description + .. index:: product description description Description of the product. -- cgit v1.2.3 From befcb85e0149b5a31e184b477e700d517b70d6fe Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:18:37 -0500 Subject: mark up ‘locations’ (two instances) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 7fd1e054..62991c15 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -689,7 +689,7 @@ products merchant address - This should give a label in the locations map, specifying where + This should give a label in the ``locations`` map, specifying where the merchant is located. name @@ -697,7 +697,7 @@ merchant business. jurisdiction - This should give a label in the locations map, specifying the + This should give a label in the ``locations`` map, specifying the jurisdiction under which this contract is to be arbitrated. .. index:: location -- cgit v1.2.3 From 2451350a454de5f7ce63acdea0f5aed2565ccf92 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:20:08 -0500 Subject: capitalize "receiver" at beginning of sentence --- taler-merchant-api-tutorial.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 62991c15..35bf07c2 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -712,7 +712,7 @@ locations non-exhaustive list of location attributes is the following: name - receiver name for delivery, either business or person name. + Receiver name for delivery, either business or person name. country Name of the country for delivery, as found on a postal package, -- cgit v1.2.3 From fad4cb64ce8cac7ed24234bc0e7781ae04526e36 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:21:40 -0500 Subject: change "i.e." to "e.g." (two instances) --- taler-merchant-api-tutorial.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 35bf07c2..5afa7a14 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -716,10 +716,10 @@ locations country Name of the country for delivery, as found on a postal package, - i.e. “France”. + e.g. “France”. state - Name of the state for delivery, as found on a postal package, i.e. + Name of the state for delivery, as found on a postal package, e.g. “NY”. region -- cgit v1.2.3 From 996140163d18824529c8f7aef6d3260a321e24b9 Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Tue, 24 Nov 2020 21:29:00 -0500 Subject: move ‘.. index::’ for "product description" prior to ‘products’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 5afa7a14..39f5ae54 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -638,12 +638,12 @@ refund_deadline the customer. After this time, it will no longer be possible to refund the customer. Must be smaller than the ``pay_deadline``. +.. index:: product description + products Array of products that are being sold to the customer. Each entry contains a tuple with the following values: - .. index:: product description - description Description of the product. -- cgit v1.2.3 From eea346162b9ba78c9f4b0f48b9c2b2bcda425ecd Mon Sep 17 00:00:00 2001 From: Thien-Thi Nguyen Date: Wed, 25 Nov 2020 12:21:39 -0500 Subject: convert from table @item to @cindex: ‘frontend’, ‘backend’ MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- taler-merchant-api-tutorial.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst index 39f5ae54..33e0f8e5 100644 --- a/taler-merchant-api-tutorial.rst +++ b/taler-merchant-api-tutorial.rst @@ -78,18 +78,18 @@ Architecture overview The Taler software stack for a merchant consists of the following main components: -- frontend +.. index:: frontend - A frontend which interacts with the customer’s browser. The frontend +- A frontend which interacts with the customer’s browser. The frontend enables the customer to build a shopping cart and place an order. Upon payment, it triggers the respective business logic to satisfy the order. This component is not included with Taler, but rather assumed to exist at the merchant. This tutorial describes how to develop a Taler frontend. -- backend +.. index:: backend - A Taler-specific payment backend which makes it easy for the frontend +- A Taler-specific payment backend which makes it easy for the frontend to process financial transactions with Taler. For this tutorial, you will use a public sandbox backend. For production use, you must either set up your own backend or ask another person to do so for -- cgit v1.2.3