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(-) (limited to 'taler-merchant-api-tutorial.rst') 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