W3C home > Mailing lists > Public > public-webpayments-ig@w3.org > March 2015

Proposal for forward motion: Aligning with X9/ISO work in Payments

From: David Ezell <David_E3@VERIFONE.com>
Date: Wed, 18 Mar 2015 13:33:56 +0000
To: "public-webpayments-ig@w3.org" <public-webpayments-ig@w3.org>
Message-ID: <54C00E24834FCE47B11EC129A84E7F78CCB0E55F@VF2WDEXMB1.verifone.com>
Dear IG members:

As we have been discussing for some time now, much of the work on payments in the standards area has been done either at X9 (ANSI) or at ISO.  The work done by these groups has the advantage of regulatory standing.  And there is a large body of outstanding work.   In order to advance our cause (acceptance of a payment standard for the web) I'd like to propose the following plan:

1) Review (and approve) ISO12812 - we can't exactly do this yet, since it is still out for vote and we can't see it in non-ISO-member space.  So this part of the proposal depends on our agreeing that it's going to work for us (TBD).

2) Review X9.119 pt. 2 - this standard is about "tokenization."  It is potentially about payment tokenization, but it includes >other uses for tokens as well.  This work is gaining wide traction.

3) Submit our resulting flows to ISO20022 "certification" (RNG) -  Let's take the flows defined in our use cases/payment agent work and refine and submit them to become an "accredited ISO20022 framework."

This modest plan gives us a defined target, leading to a model that might be much more easily accepted in the payment community, since we will be ISO20022 "certified."

There are literally dozens of ISO and X9 standards that might apply to corner cases of what we're doing, but I think a focused strategy that includes these three[1] standards listed above will help us reach our goal of producing credible recommendations for web payments in the near term.

There is substantial work implied in this proposal.  Discussion is encouraged.  It's important.

Best regards,
David

[1] This proposal does NOT imply that we will not support other standards.
________________________________
This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.
Received on Wednesday, 18 March 2015 13:34:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:08:33 UTC