Re: [webpayments] PROPOSAL: Adopt developer friendly-terminology for WG deliverables but root this in ISO20022 data dictionary through our published glossary. (#67)

This proposal was RESOLVED during the 28 January meeting with the following addition as proposed by @msporny:

* The W3C Web Payments Terms and their respective mappings to common terms and ISO20022 will be implemented in the Web Payments IG Glossary

The group also noted that all WG specs SHOULD reference the IG glossary but elected to not include this as an explicit dependency in the proposal.

The final resolution was:

The WG will adopt the following terms for use in its deliverables:

W3C Web Payments Term | Common Terms  |  ISO 20022 definition
-----------------------------------|------------------------|-----------------------------
Payee | Merchant | Creditor, Beneficiary
Payee PSP | Acquirer, Gateway | Acquirer, Intermediary
Payer | Shopper, Consumer, User | Debtor, Initiator
Payer PSP | Wallet | Intermediary

* We will use the W3C Payments Terms in the W3C specifications (to avoid writing out in detail).
* In the flows we will use the complete terms, however it should be realised that Common terms and ISO 20022 definitions may change between flows, for example for Direct Debit the ISO20022 term is Beneficiary, whilst for Credit Transfer it is Creditor.
* We will endeavour to have the W3C Terms added to the ISO repository as reserved words or ideally as specific mappings, e.g. a Payee is the superclass of both the subclasses of Creditors and Beneficiary.
* The W3C Web Payments Terms and their respective mappings to common terms and ISO20022 will be implemented in the Web Payments IG Glossary

@mountainhippo took an action to liaise with the IG and ensure the terms are part of their glossary   
https://www.w3.org/Payments/WG/track/actions/12



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