taler-docs

commit 93c6511c688c8c8c0313c76f83eb149bc5a34875
parent 73171cc84c99cac5a20a9d910132744db850aa53
Author: Bohdan Potuzhnyi <bohdan.potuzhnyi@gmail.com>
Date:   Fri, 31 Jan 2025 12:06:55 +0100

small change to the merchant template docs

Diffstat:
M
core/api-merchant.rst
 | 
12
++++++------

1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -3606,12 +3606,12 @@ The business process for the templating API is also pretty simple. First, the
 private API is used to setup (or edit) the template, providing all of the
 contract terms that subsequently cannot be changed by the customer/wallet.
 This template data is then stored under the template ID which can be freely
-chosen.  The SPA should also make it easy for the merchant to convert the
-template ID into a taler://-URI and/or QR code. Here, the merchant must
-additionally specify the defaults (if any) for the customer-editable values.
-Afterwards, the merchant can print out the QR code for display at the store,
-add a link to the taler://-URI and/or embed the respective QR-code image into
-their Web page.
+chosen and must be in URL-encoded format. The SPA should also make it easy
+for the merchant to convert the template ID into a taler://-URI and/or QR code.
+Here, the merchant must additionally specify the defaults (if any) for the
+customer-editable values. Afterwards, the merchant can print out the QR code
+for display at the store, add a link to the taler://-URI and/or embed the
+respective QR-code image into their Web page.
 
 To receive a payment confirmation, the mechant may choose to configure a
 webhook in the merchant backend on the ``pay`` action, for example to send an