Comments (12)
The group resolved to use ISO20022 terminology where appropriate. One caveat is that this langaue may be confusing in examples or specs so we should consider labels like merchant(debtor) website, user(creditor) payment app and user(creditor)'s browser in examples and use cases. I think we can get away with simply using debtor and creditor in normative sections of the spec.
from webpayments.
+1 for debtor and creditor
Based on the approach of participants and business roles defined in ISO 20022, we will surely be able to map the specific terminology defined in the current flows with the Creditor/Debtor business roles.
from webpayments.
+1 for debtor and creditor. However, I also endorse Adrian's idea that we
use more common terms in labels for clarity to people who are not in the
industry.
On Wed, Jan 20, 2016 at 8:19 AM, Vincent Kuntz [email protected]
wrote:
+1 for debtor and creditor
Based on the approach of participants and business roles defined in ISO
20022, we will surely be able to map the specific terminology defined in
the current flows with the Creditor/Debtor business roles.β
Reply to this email directly or view it on GitHub
#59 (comment).
-Shane
from webpayments.
+1 to Shane's comments (Adrian's idea): #59 (comment)
from webpayments.
+1 for debtor / creditor associated with common terms
from webpayments.
I think debtor and creditor is ok, but will but a tough sell in communicating this to existing merchants and payment providers, who will talk in terms of payer/payee or more commonly merchant and customer.
So +1 to @adrianhopebailie 's suggestion to use labels for clarity.
from webpayments.
I agree with @mountainhippo that debtor/creditor is likely to be pretty opaque for a certain slice of users. But the same will be true of any choice. The only way out here is to anchor in ISO 20022 and provide synonyms.
from webpayments.
+1 to ISO 20022 plus synonyms.
from webpayments.
+1 to ISO 20022 plus synonyms.
Cyril VIGNET
+33622040856
+33158400234
[email protected]
De : ianbjacobs [mailto:[email protected]]
EnvoyΓ© : mercredi 20 janvier 2016 17:51
Γ : w3c/webpayments
Cc : webpayments
Objet : Re: [webpayments] Terminology for payer/payee, user/merchant, debtor/creditor (#59)
+1 to ISO 20022 plus synonyms.
β
Reply to this email directly or view it on GitHubhttps://github.com//issues/59#issuecomment-173269511.
from webpayments.
+1 to ISO20022 plus synonyms;
So some example will be;
Creditor [Merchant/Payee]
Creditor Agent [Merchant/Payee's Payment Service Provider(PSP)]
Debtor [Shopper/Payer]
Debtor Agent [Shopper/Payer's Payment Service Provider(PSP)]
If we can shoot for a consensus agreement to this on tomorrow call, we can update the suggestions in the Wiki that Laurent kindly drafted post the call
https://github.com/w3c/webpayments/wiki/ISO-20022-definitions-mapping-on-flows
from webpayments.
-1 I think this is a really bad idea. The audience for the spec (Web Developers) don't know what a 'creditor agent' or even what a 'creditor' really means... appending it to "merchant (creditor)" is not good either because it puts aliases beside every term in the spec, making the spec that much harder to read. I suggest we instead do use ISO20022, but put the alias in the definition of what a "merchant" or a "payee" is.
That way, you get to align w/ ISO20022, you use terminology that Web developers are somewhat familiar with, and you don't make the spec text any more dense than it has to be.
from webpayments.
Closing as the related proposal was resolved on the call on 28 January.
from webpayments.
Related Issues (20)
- [Payment app] Should merchants be able to limit matching to trusted apps? HOT 1
- [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
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.