RE: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66)

Hello Shane,

Something like that, I recall, was expressed by David Ezell as an outcome of a NACS-study in Sapporo. (I still hear ‘Certainly not another app!’ ringing in my ears…)

What I can confirm from our studies are confirmative statements for having every payment, identity and entitlement instrument in on place. Citing results of a Customer Advisory Board format held in June 2015 at T-Labs:
“Of all the claimed positive aspects, the central place for all identity data was ranked as the most valuable.“

A finding from an online survey conducted in Oct 2015 with about 235 counted participants says:
“The combination of services is the main benefit”

Both refer to the solution we have demoed at several occasions, which puts together identity, payment and other credentials (from the POV of a user, not the techie-interpretation of the term ☺). They, thus, give feedback on the quality perceived with such solution, which was not contrasted with any approach of a less harmonized nature. Rather it was compared to current reality (dozens of passwords, PINs, many different cards, coupons, etc.)

Regards,
                Jörg

From: Shane McCarron [mailto:notifications@github.com]
Sent: Montag, 14. März 2016 16:24
To: WICG/paymentrequest
Cc: webpayments
Subject: Re: [paymentrequest] Payment App Registration: Same Origin is problematic for identifying_url (#66)


Jorg,

Can you confirm that what you are saying is that in environment you have tested, users are not interested in / refuse to install or use more than one payment app in a given environment? And is there any research data you can share on this?

—
Reply to this email directly or view it on GitHub<https://github.com/WICG/paymentrequest/issues/66#issuecomment-196366426>.