taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 6d32d8a1e3fa95cea7af760cd72c4595fa10de97
parent d9f891a5e989b8c112367ccf8fcc4aa832a731ea
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
Date:   Thu, 11 Feb 2021 19:41:17 -0500

mark up field names ‘amount’, ‘instance’, ‘justification’, ‘next_url’

Diffstat:
Mtaler-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 @@ -447,15 +447,15 @@ funds available for tipping, query the ``/tip-query`` endpoint: To authorize a tip, ``POST`` to ``/tip-authorize``. The following fields are recognized in the JSON request object: -- amount: Amount that should be given to the visitor as a tip. +- ``amount``: Amount that should be given to the visitor as a tip. -- instance: Merchant instance that grants the tip (each instance may +- ``instance``: Merchant instance that grants the tip (each instance may have its own independent tipping funds configured). -- justification: Description of why the tip was granted. Human-readable +- ``justification``: Description of why the tip was granted. Human-readable text not exposed to the customer, but used by the Back Office. -- next_url: The URL that the user’s browser should be redirected to by +- ``next_url``: The URL that the user’s browser should be redirected to by the wallet, once the tip has been processed. The response from the backend contains a ``tip_redirect_url``. The