[Top][All Lists]

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

Re: [Taler] transaction history UX and fulfillment URL semantics

From: Christian Grothoff
Subject: Re: [Taler] transaction history UX and fulfillment URL semantics
Date: Sun, 24 Jan 2016 22:43:48 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0

On 01/24/2016 09:51 PM, Florian Dold wrote:
> And I should mention that with the second suggestion, we still DO have
> the /pay page, but it is not part of the contract wrapper anymore, the
> wallet does not need to persistently store it.

Agreed, if /fulfillment is *required* to auto-redirect to /pay if
needed, we only need the /fulfillment URI in the contract. In that case,
it should probably become part of the signed JSON, not just some
external thing (which is what I think you mean by "contract wrapper").

> Whenever the /fulfillment?UUID=X page detects that the session state is
> missing / wrong, it just asks the wallet to POST the coins to the
> merchant-specific correct URL.

Sure. Still, here I think the merchant should _always_ replay the full
contract, as we should not allow Web pages to interrogate the Wallet
about its contracts in any way.

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

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