Re: [webpayments] [Architecture] Payment App is a term used in EMV to describe the applet stored in SC (#31)

Hi, folks–

I also like "payment app", with the caveats described by others.

Regards–
–Doug

On 12/9/15 2:52 PM, webpayments wrote:
> On 12/09/2015 02:36 PM, Dave Longley wrote:
>  > I've come around
>  > <https://github.com/w3c/webpayments/issues/11#issuecomment-163365290>
>  > to agreeing with @adrianhopebailie
>  > <https://github.com/adrianhopebailie>'s approach for abstracting the
>  > details of payment instruments into payment apps. Which means, from
>  > my perspective, we may not even need to really talk about payment
>  > instruments at all -- we only need to talk about payment apps the
>  > payment schemes/methods that they support.
>
> +1, @dlongley and I discussed this a bit in the office and the
> conversation was good for two reasons:
>
> * It clarified what a payment app was and wasn't (at least in my mind),
> so that'll help with the definitions.
> * It simplified the interfaces necessary to make the whole ecosystem
> work, and may have gotten rid of our "decentralized registration"
> concerns as well.
>
> I'll try to elaborate in more depth as time permits.
>
>  > With this in mind, the name "Payment App" is a lot less controversial
>  > to me.
>
> Yes, I was on the fence about 'payment app', but the discussion
> clarified enough for me and now I'm in favor of payment app w/ a few
> changes to the definition (to explain what it isn't, primarily).
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> blog: Web Payments: The Architect, the Sage, and the Moral Voice
> https://manu.sporny.org/2015/payments-collaboration/
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/webpayments/issues/31#issuecomment-163371670>.
>


---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webpayments/issues/31#issuecomment-163373594