Re: [ubl-lcsc] Origin of CardTypeCode for Credit Cards

[Alan.Stitzer@marsh.com]

Is it important to know more than that a card is a debit card -- for
instance if it is a Visa Debit card.

If not, why wouldn't another "card type" of DebitCard be sufficient?



____________________
Alan Stitzer
AVP
Marsh USA Inc.
1166 Avenue of the Americas
New York, NY 10036-2774
Phone: (561) 743-1938
Fax: (561) 743-1993
Internet: Alan.Stitzer@marsh.com
____________________


<<< Memo from tmcgrath@portcomm.com.au@Internet on 27 January, 2004, 23:49
Tuesday >>>


tmcgrath@portcomm.com.au@Internet on 27 Jan 2004, 23:49 Tuesday

To:    ubl-lcsc
cc:      (bcc: Alan Stitzer)
Subject:    [ubl-lcsc] Origin of CardTypeCode for Credit Cards


Stephen Green has raised an issue about the BBIE CardTypeCode

The original intention of CardTypeCode was to denote the authority
responsible for the credit card.

It was taken from the CardTypeCode of xCBL3.0 which says...

This code identifies the type of card used for payment.

Value: Enumeration, including:

    * Other - Other Card Type
    * AMEX - American Express
    * VISA - VISA
    * MC - Master Card
    * Discover - Discover
    * JCB - JCB
    * Diners - Diners

However, the definition for CardTypeCode "the type of card used for
payment", could be misunderstood as being 'credit' or 'debit' card -
this was not its original intent.

So what is needed is better definition of CardTypeCode and perhaps a new
BBIE for AccountTypeCode?

My web research has revealed that the generic term for organisations in
the enumerated list above is 'networks'.  So perhaps the correct
Property Term for this is Network, rather than Type qualified by Card
(as it is at present).  That is we have NetworkCode.

But of course these are not really 'codes', to connect with another
debate - these are identifiers.  So another possibility is to call it
NetworkID.  This also complements IssuerID (identifies the organisation
issuing the card).  That is , we could have Network ID (identifies the
organisation managing the interchange of payment information).

any suggestions?

--
regards
tim mcgrath
phone: +618 93352228
postal: po box 1289   fremantle    western australia 6160


(See attached file: C.htm)


To:    ubl-lcsc@lists.oasis-open.org@Internet
cc:     (bcc: CN=Alan Stitzer/OU=NYC-NY/OU=US/OU=Marsh/O=MMC)
From:  tmcgrath@portcomm.com.au@Internet






Stephen Green has raised an issue about the BBIE CardTypeCode

The original intention of CardTypeCode was to denote the authority responsible
for the credit card.  

It was taken from the CardTypeCode of xCBL3.0 which says...

This code identifies the type of card used for payment.

Value: Enumeration, including:

• Other - Other Card Type
• AMEX - American Express
• VISA - VISA
• MC - Master Card
• Discover - Discover
• JCB - JCB
• Diners - Diners

However, the definition for CardTypeCode "the type of card used for payment",
could be misunderstood as being 'credit' or 'debit' card - this was not its
original intent.

So what is needed is better definition of CardTypeCode and perhaps a new
BBIE for AccountTypeCode?

My web research has revealed that the generic term for organisations in the
enumerated list above is 'networks'.  So perhaps the correct Property Term
for this is Network, rather than Type qualified by Card (as it is at present).
 That is we have NetworkCode.

But of course these are not really 'codes', to connect with another debate
- these are identifiers.  So another possibility is to call it NetworkID.
 This also complements IssuerID (identifies the organisation issuing the
card).  That is , we could have Network ID (identifies the organisation managing
the interchange of payment information).

any suggestions?

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160