W3C home > Mailing lists > Public > public-webpayments@w3.org > November 2014

Re: Loyalty cards - Trust, Privacy, Security and Convenience issues

From: Nate Otto <nate@ottonomy.net>
Date: Thu, 06 Nov 2014 01:36:59 +0000
Message-ID: <CAPk0ugm-=Bm4fdNdwawGsdV_+2f6ZxSf2eSowrSbm9qoc_qLZg@mail.gmail.com>
To: Manu Sporny <msporny@digitalbazaar.com>, Web Payments CG <public-webpayments@w3.org>
> How you pay for that offer of sale is orthogonal. From a technical
> standpoint, this creates a nice separation of concerns. Each problem
> neatly in its own space.
Well put.

I think I agree with most or all loyalty schemes just needing the first of
your two types.

One example that a couple local growler-filling stations use for a shared
loyalty card is Fivestars where points accrue, but the card itself is still
just a simple identity credential. Points are granted, read, and spent
through API calls to the central loyalty service, which doesn't mean they
need to be transmitted as a credential. I'm not sure exactly what the
shared incentives are that might encourage businesses to join this network,
whether there actually is any currency that trades hands if a consumer
earns all their points at one store and spends them at another. But either
way, the potential fake currency may all just be handled by the central
service and still doesn't ever need to change hands.

Received on Thursday, 6 November 2014 01:37:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:37 UTC