Comments (5)
Sounds good. One extra bullet point to add to the proposal that makes it clear how these proposals get implemented in the specifications:
- The W3C Web Payments Terms and their respective mappings to common terms and ISO20022 will be implemented in the Web Payments IG Glossary, which will be dynamically pulled into all WPWG specifications.
from webpayments.
+1 to this proposal now
from webpayments.
This looks fine to me. It's not totally clear to me how this will map to roles in a Web API interaction, but I suppose that will become clearer as the API solidifies.
from webpayments.
@msporny - edited to include your additonal bullet
@bifurcation - have you had a look at the high-level architecture?
https://github.com/w3c/webpayments/wiki/A-Payments-Initiation-Architecture-for-the-Web
from webpayments.
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
from webpayments.
Related Issues (20)
- [Payment apps] How can we optimize user experience when there is only one match? HOT 1
- Pull filters out of payment method data HOT 2
- Overview document figure 5 HOT 13
- Propose a payment method specification that includes an example of field level security HOT 1
- propose to add encoding attribute to data set HOT 18
- European market - Security concerns HOT 10
- [Tokenized Card Payment] Replace usage of 'last4' with 'suffix' HOT 8
- [Tokenized Card Payment] TokenCardRequest should inherit from BasicCardRequest HOT 3
- 3D secure support HOT 4
- Sepamail WebIDL syntax and algorithms HOT 4
- Payment Method Manifest spec - should enable country specific app discovery HOT 9
- Fingerprint and version metadata (in Web App Manifest spec) HOT 36
- Should the WPWG develop a cryptocurrency payment method specification HOT 14
- Adopt a "test as you commit" policy HOT 10
- Just a question, curious HOT 1
- Visual Identity for Web Payments HOT 14
- Specify both pickup and delivery addresses in a single payment request HOT 2
- QR use cases HOT 5
- Proposal to restore charter text around UI being out of scope HOT 10
- Pagos alex
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from webpayments.