Re: Updated Web Payments Architecture Summary

Manu,

Thanks. I haven't review it yet but wanted to make a quick comment re
ISO20022 harmonisation.

ISO20022 defines the term payment instruction and I don't believe what we
have defined as a Payment Request is the same thing.

I like the terminology we have used because it is accurate in describing
what the purpose of that message/data is. It is a request for a payment.
Importantly it is not a request to MAKE a payment or a request to AUTHORIZE
a payment. The request is simply that a payment happens and the payment
method chosen by the payer defines the action that must be taken both by
the payer and the payee.

Adrian

On 27 June 2016 at 14:16, Manu Sporny <msporny@digitalbazaar.com> wrote:

> Based on AdrianHB and IanJ's comments, the Web Payments Architecture
> Summary has been updated and is available for review here:
>
> https://w3c.github.io/webpayments/proposals/wparch/
>
> Changes made include:
>
> * Removing ISO20022 harmonization via Payment Instruction
> * Removing the word "Transaction" from certain diagrams/text
> * Adding issue markers for items above
> * Adding issue marker for payment app registration
>
> I think we'll want to have a discussion with the ISO 20022 RA folks (and
> the broader payments industry) about the direction of our work at the
> upcoming face-to-face.
>
> -- manu
>
> --
> Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
> Founder/CEO - Digital Bazaar, Inc.
> JSON-LD Best Practice: Context Caching
> https://manu.sporny.org/2016/json-ld-context-caching/
>
>