commit e7b46f2cefb7b38813bb233c4a15a55dc511b918
parent e9be542e86ada562bb2d5bed8b1a19cfdfedc74e
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 29 Jun 2025 22:44:55 +0200
fix links
Diffstat:
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
@@ -75,7 +75,7 @@ The Taler software stack for a merchant consists of four main components:
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 `Merchant API Tutorial <https://tutorials.taler.net/merchant/api/taler-merchant-api-tutorial>`_ gives an
+ The `Merchant API Tutorial <https://tutorials.taler.net/dev/merchant-api/>`_ gives an
introduction for how to integrate Taler with Web shop frontends.
- A *back-office* application that enables the shop operators to view
customer orders, match them to financial transfers, and possibly
@@ -207,8 +207,8 @@ In Taler, users pay merchants for *orders*. An order is first created by the
merchant. To create an order, the merchant must specify the specific *terms*
of the order. Order *terms* include details such as the total amount to be
paid, payment fees the merchant is willing to cover, the set of products to
-deliver, a delivery location and many other details. The `merchant API
-specification <contract-terms>`_ specifies the full set of possible order
+deliver, a delivery location and many other details. The :ref:`merchant API
+specification <contract-terms>` specifies the full set of possible order
terms.
After an order is created, it is *claimed* by a wallet. Once an order is
