Re: [w3c/payment-request] A distinct invoice address should be supported (#550)

Today at the working group is was further agreed that this would not be elevated into the PaymentRequest API.

It was however agreed that the Address definition in https://www.w3.org/TR/payment-request/#paymentaddress-interface could be reused in any payment method.

This allows a consistent definition to be used across all payment methods.

A further thought that occurred to me post this discussion was that if there were a base type for payment method response that included billingAddress, that all payment method responses MUST inherit from, then this would meet the need to force every payment method and (by implication) every payment instrument to have a billing address. This approach would remove the need to change PR API and be consistent with all known implementations that are currently deployed.

I note that this 'mistake' is easy to make as neither tokenised card nor credit transfer has included a billing address in their draft specifications, despite the authors (I'm one of them) being aware of this requirement.

Furthermore https://github.com/w3c/webpayments-methods-tokenization/issues/17 discusses the reuse of data dictionary items between specifications which is as yet unresolved.

I propose that we discuss the merits of duplication vs inheritance further at the slot on tomorrow's agenda at 15:30 https://github.com/w3c/webpayments/wiki/FTF-April2018 (should there be time)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/payment-request/issues/550#issuecomment-382732870