taler-docs

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

commit f4d412ee1149740d0c9b88022e9815f9d48603d3
parent 60a915b5bfe15d0f4bdbaf484ea62abdcfb4e705
Author: Florian Dold <florian.dold@gmail.com>
Date:   Mon, 10 Aug 2020 17:24:47 +0530

formatting

Diffstat:
Mdesign-documents/007-payment.rst | 6++++--
1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/design-documents/007-payment.rst b/design-documents/007-payment.rst @@ -82,7 +82,8 @@ The merchant backend runs the following steps to generate the {backendBaseUrl}/orders/{order-ID}?h_contract={contract-hash}&session_id={session-ID} - together with the status *unpaid*. (If *session-ID* is null, it does not matter for which session the contract was paid.) **Terminate.** + together with the status *unpaid*. (If *session-ID* is null, it does not + matter for which session the contract was paid.) **Terminate.** 6. Here *order-ID* must now identify an order that is *paid* or *refunded*. Obtain the contract terms hash *contract-hash* and return the URL @@ -90,7 +91,8 @@ The merchant backend runs the following steps to generate the {backendBaseUrl}/orders/{order-ID}?h_contract={contract-hash}&session_id={session-ID} - together with the status *paid* or *refunded* (and if applicable, with details about the applied refunds). **Terminate.** + together with the status *paid* or *refunded* (and if applicable, with + details about the applied refunds). **Terminate.**