|Subject:||Re: [Taler] replay and merchant backend/frontend protocol|
|Date:||Tue, 26 Jan 2016 12:02:10 +0100|
|User-agent:||Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0|
Am 26.01.2016 um 11:19 schrieb Christian Grothoff:
The trade-off question was about _when_ the merchant stores it: only when the contract is successful (paid), or already when it is being generated (proposed by the merchant). Depending on the type of application (i.e. serving data vs. shipping goods), being lazy and only storing 'paid' contracts can reduce database transaction volume.
IC. But in both cases the merchant will have some kind of "shopping card", wouldn't he? Even for a single, immediately downloaded item the merchant needs to keep track of her offering - simply because there are different VAT rates in the EU.  So she already needs to store the data anywhere in his own shop.
 I can elaborate this ugly peace of EU taxing on request.
Dipl.-Informatiker (univ), CISSP, CSSLP
Information Security Management, Security Governance, Secure Software Development
Goebel Consult, Landshut
Description: OpenPGP digital signature
|[Prev in Thread]||Current Thread||[Next in Thread]|