Coder Social home page Coder Social logo

Comments (12)

adrianhopebailie avatar adrianhopebailie commented on August 25, 2024

πŸ‘ for debtor and creditor

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.

vkuntz avatar vkuntz commented on August 25, 2024

+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.

webpayments avatar webpayments commented on August 25, 2024

+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.

dlongley avatar dlongley commented on August 25, 2024

+1 to Shane's comments (Adrian's idea): #59 (comment)

from webpayments.

LaurentCastillo avatar LaurentCastillo commented on August 25, 2024

+1 for debtor / creditor associated with common terms

from webpayments.

mountainhippo avatar mountainhippo commented on August 25, 2024

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.

bifurcation avatar bifurcation commented on August 25, 2024

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.

ianbjacobs avatar ianbjacobs commented on August 25, 2024

+1 to ISO 20022 plus synonyms.

from webpayments.

webpayments avatar webpayments commented on August 25, 2024

+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.

mattsaxon avatar mattsaxon commented on August 25, 2024

+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.

msporny avatar msporny commented on August 25, 2024

-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.

adrianhopebailie avatar adrianhopebailie commented on August 25, 2024

Closing as the related proposal was resolved on the call on 28 January.

from webpayments.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.