gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] 08/18: mark up field names ‘refund’, ‘reason’


From: gnunet
Subject: [taler-docs] 08/18: mark up field names ‘refund’, ‘reason’
Date: Fri, 12 Feb 2021 02:00:46 +0100

This is an automated email from the git hooks/post-receive script.

ttn pushed a commit to branch master
in repository docs.

commit db395bbcd5c0f36c3ff2e9693b1c8c8f2708dac5
Author: Thien-Thi Nguyen <ttn@gnuvola.org>
AuthorDate: Thu Feb 11 19:29:36 2021 -0500

    mark up field names ‘refund’, ‘reason’
---
 taler-merchant-api-tutorial.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/taler-merchant-api-tutorial.rst b/taler-merchant-api-tutorial.rst
index bb385e1..bb8eb12 100644
--- a/taler-merchant-api-tutorial.rst
+++ b/taler-merchant-api-tutorial.rst
@@ -328,12 +328,12 @@ The frontend can instruct the merchant backend to 
authorize a refund by
 
 The refund request JSON object has only two fields:
 
--  refund: Amount to be refunded. If a previous refund was authorized
+-  ``refund``: Amount to be refunded. If a previous refund was authorized
    for the same order, the new amount must be higher, otherwise the
    operation has no effect. The value indicates the total amount to be
    refunded, *not* an increase in the refund.
 
--  reason: Human-readable justification for the refund. The reason is
+-  ``reason``: Human-readable justification for the refund. The reason is
    only used by the Back Office and is not exposed to the customer.
 
 If the request is successful (indicated by HTTP status code 200), the

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]