Re: [ubl-comment] Fwd: RE: [ubl-dev] Invitation to comment on UBL Payment Means Information V1.0 - ends August 28th

["Levine Naidoo" <levine.naidoo@au1.ibm.com>]

Dear David

Thank you for taking the time to review the payment means committee note and for your comments.

Please find our reply here https://www.oasis-open.org/committees/document.php?document_id=66136&wg_abbrev=ubl

many thanks
/Levine
(editor)


David Goodenough ---21/08/2019 07:46:09 pm------------- Forwarded Message ---------- Subject: RE: [ubl-dev] Invitation to comment on UBL Payment

From: David Goodenough <david.goodenough@broadwellmanor.co.uk>
To: "ubl-comment@lists.oasis-open.org" <ubl-comment@lists.oasis-open.org>
Date: 21/08/2019 07:46 pm
Subject: [EXTERNAL] [ubl-comment] Fwd: RE: [ubl-dev] Invitation to comment on UBL Payment Means Information V1.0 - ends August 28th

---

---------- Forwarded Message ----------

Subject: RE: [ubl-dev] Invitation to comment on UBL Payment Means Information V1.0 - ends August 28th
Date: Wednesday, 21 August 2019, 08:43:59 BST
From: Levine Naidoo <levine.naidoo@au1.ibm.com>
To: David Goodenough <david.goodenough@broadwellmanor.co.uk>
CC: ubl-dev@lists.oasis-open.org <ubl-dev@lists.oasis-open.org>

Hi David

Many thanks for your email.  Kindly submit to ubl-comment@lists.oasis-open.org for your comment to acknowledged and reviewed.

Thank you

Levine Naidoo
(Editor)


On 30 Jul 2019, at 03:20, David Goodenough <david.goodenough@broadwellmanor.co.uk> wrote:

A few items strike me:-

1) I realise that this may exist elsewhere, but either a link to that or if it does not exist the actual content of a mapping between UBL and ISO-20022
fields, and similarly between UBL and the OpenBanking API.

2) Certainly in the UK the address and even the institution name of the destination bank account are entirely unnecessary, at least when you make on online payment. Many of the sort codes are now virtual anyway, as branches have been closed and holder's home branch being moved to one of the few remaining branches while leaving the original sort code in place. In addition the payments these days never go anywhere near a branch, but are all dealt with centrally. I suppose it may be necessary for international transfers, in which case there may be need for two different means clauses.

3) In addition just as you mention that the actual account number in some cases may need to be obscured (although if the transaction is encrypted this becomes unnecessary), the address details might also be thought of as in need of obscuring as it simply provides information a scammer could use to misuse the banking data. Obviously end to end encryption would solve this problem.

Regards

David

On Monday, 29 July 2019 16:33:26 BST Chet Ensign wrote:
OASIS members and other interested parties,

OASIS and the OASIS Universal Business Language (UBL) TC are pleased to announce that UBL Payment Means Information Version 1.0 is now available for public review and comment.

This Committee Note provides examples of how implementers can support different means of payment using UBL.

The documents and related files are available here:

UBL Payment Means Information Version 1.0
Committee Note Draft 01 / Public Review Draft 01
26 June 2019

Editable source (Authoritative):
https://docs.oasis-open.org/ubl/UBL-Payment/v1.0/cnprd01/UBL-Payment-v1.0-cnprd01.docx

HTML:
https://docs.oasis-open.org/ubl/UBL-Payment/v1.0/cnprd01/UBL-Payment-v1.0-cnprd01.html

PDF:
https://docs.oasis-open.org/ubl/UBL-Payment/v1.0/cnprd01/UBL-Payment-v1.0-cnprd01.pdf

For your convenience, OASIS provides a complete package of the specification document and any related files in ZIP distribution files. You can download the ZIP file at:

https://docs.oasis-open.org/ubl/UBL-Payment/v1.0/cnprd01/UBL-Payment-v1.0-cnprd01.zip

How to Provide Feedback

OASIS and the UBL TC value your feedback. We solicit input from developers, users, and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.

The public review starts on 30 July 2019 at 00:00 UTC and ends 28 Augusts 2019 at 23:59 UTC.

Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be used by following the instructions on the TC's "Send A Comment" page (https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=ubl).

Comments submitted by TC non-members for this work and for other work of this TC are publicly archived and can be viewed at:

https://lists.oasis-open.org/archives/ubl-comment/

All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review, we call your attention to the OASIS IPR Policy [1] applicable especially [2] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification.

OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.

Additional information about the specification and the UBL TC can be found at the TC's public home page:

https://www.oasis-open.org/committees/ubl/

========== Additional references:

[1] http://www.oasis-open.org/who/intellectualproperty.php

[2] http://www.oasis-open.org/committees/ubl/ipr.php
https://www.oasis-open.org/policies-guidelines/ipr#RF-on-Limited-Mode
RF on Limited Terms Mode

--

/chet
----------------
Chet Ensign
Chief Technical Community Steward
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Mobile: +1 201-341-1393

-----------------------------------------