diff options
Diffstat (limited to 'taler-merchant-manual.rst')
| -rw-r--r-- | taler-merchant-manual.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst index e27c6569..fdaf138a 100644 --- a/taler-merchant-manual.rst +++ b/taler-merchant-manual.rst @@ -71,24 +71,24 @@ special currency “KUDOS” and includes its own special bank. The Taler software stack for a merchant consists of four main components: -- 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. The :ref:`Merchant API Tutorial <merchant-api-tutorial>` gives an introduction for how to integrate Taler with Web shop frontends. -- A back-office application that enables the shop operators to view +- A *back-office* application that enables the shop operators to view customer orders, match them to financial transfers, and possibly approve refunds if an order cannot be satisfied. This component is not included with Taler, but rather assumed to exist at the merchant. The :ref:`Merchant Backend API <merchant-api>` provides the API specification that should be reviewed to integrate such a back-office with the Taler 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. This manual primarily describes how to install and configure this backend. -- A DBMS which stores the transaction history for the Taler backend. +- A *DBMS* which stores the transaction history for the Taler backend. For now, the GNU Taler reference implementation only supports Postgres, but the code could be easily extended to support another DBMS. Please review the Postgres documentation for details on |