Re: Mobile phone based ATM & payments solution

Sent from my iPad

> On 1 May 2014, at 5:05 pm, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
>> On 2014-05-01 07:53, Timothy Holborn wrote:
>> http://www.zdnet.com/cba-launches-cardless-atm-cash-withdrawal-service-7000028914/
> 
> thanx Tim, this is really interesting!
> 
>> 
>> Implications
>> 1. A definition of a "wallet"
>> 2. Banking based interface for CNP (card not present) payments (receipt might be adapted via www of merchant system.  How's it tag the account / transaction, then link it back to a web-payments account system? )
>> 
>> 3. If user can connect the "app id" to an online "web payments enabled" profile, then 
>> 
>> A. transaction related data could be facilitated to an online account
>> B. how could a merchants online environment and crm be linked to physical retail environments?
>> C. KYC issue seems to be sorted?
> 
> Regarding KYC I remain fix in my belief that this has no room in a payment standard.
> 
> Banks do not generally share customer info between each other and certainly not with merchants.
> Not to mention that the amount of KYC and how you obtain it varies widely.
> Paypal's scheme using a credit-card transaction + email round-trip is an example of a smart but still highly specific KYC method.
> 
> Anders

Perhaps, maintaining KYC, rather than establishing it specifically, in this business case.  KYC is probably the wrong term, but should explain the concept adequately. 

WoT (web of trust), httpa (http accountability) - all similar concepts. 

Accounts will trade data without a banking gateway.  This could be deemed a form of improvement to emailing market sensitive information to involved parties.

> 
> 
>> 
>> Nb: web2 portals trade on user-data (insights, etc.) as part of the ARPU (average revenue per user) calc.  Traditionally banking relationships have not featured a great deal of profiling data, which could be valuable to advertisers in a similar way to the type of data generated in a web2 portal.
>> 
>> Who is the trusted "cloud storage" provider, and how is that information made portable between providers (ie: end-user seeks to take their business elsewhere).  From w3 communities perspective, I guess, we're building standards to minimise potential lock-ins.??
>> 
>> Timh.
>> Sent from my iPad
>

Received on Thursday, 1 May 2014 07:13:31 UTC