From 1e2cd1b56cdee70b84a499dbff83eca9421aa700 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Sun, 9 Aug 2020 00:17:52 +0530 Subject: headings for readability --- design-documents/007-payment.rst | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'design-documents') diff --git a/design-documents/007-payment.rst b/design-documents/007-payment.rst index 206d1f77..b4b41a9c 100644 --- a/design-documents/007-payment.rst +++ b/design-documents/007-payment.rst @@ -29,6 +29,9 @@ Session-bound payment flow for Web resources In this payment flow, the user initiates the payment by navigating to a paywalled Web resource. Let *resource-URL* be the URL of the paywalled resource. +Storefront +^^^^^^^^^^ + When *resource-URL* is requested, the storefront runs the following steps: 1. Extract the the *order-ID* (or null) and *resource name* from the *resource-URL*. @@ -47,6 +50,8 @@ When *resource-URL* is requested, the storefront runs the following steps: and return to the client the content for *resource name*. **Terminate.** 9. Otherwise, the *order-status* is unpaid. Redirect the client to *client-order-status-URL*. **Terminate.** +Backend Private Order Status +^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The merchant backend runs the following steps to generate the *client-order-status-URL* when processing a request for ``GET @@ -67,6 +72,9 @@ The merchant backend runs the following steps to generate the {backendBaseUrl}/orders/{order-ID}?h_contract={contract-hash}&session_id={session-ID} +Backend Client Order Status Page +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + The merchant backend runs the following steps to generate the HTML page for ``GET /orders/{order-ID}?session_id={session-ID}&claim_token={claim-token}&h_contract={contract-hash}``: -- cgit v1.2.3