From 3a5ae3759e49c64c170d58e6b24a906327f766fe Mon Sep 17 00:00:00 2001 From: MS Date: Thu, 1 Oct 2020 14:59:07 +0200 Subject: Payment processing. Describing the situation where a customer tries to access one resource that was paid in the past, but whose cookies were deleted. --- design-documents/007-payment.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'design-documents/007-payment.rst') diff --git a/design-documents/007-payment.rst b/design-documents/007-payment.rst index 613a9ce4..8f7050d4 100644 --- a/design-documents/007-payment.rst +++ b/design-documents/007-payment.rst @@ -53,7 +53,8 @@ When *resource-URL* is requested, the storefront runs the following steps: 7. If the client has not (fully) obtained the granted refunds yet, show a link to the public order page of the backend to allow the client to obtain the refund. **Terminate.** 8. If the *order-status* is paid, return to the client the resource associated with *resource name*. **Terminate.** -9. Otherwise, the *order-status* is unpaid. Redirect the client to *client-order-status-URL*. **Terminate.** +9. Otherwise, either the *order-status* is unpaid or the customer tried to access a paid resource after having deleted their cookies. Redirect the client to *client-order-status-URL*. **Terminate.** +10. If the wallet detects that the resource was paid before, it will resend the same payment again, and will get the item; if not, the wallet will create a new payment and send to the merchant. .. note:: -- cgit v1.2.3