Has anyone worked out the updates to TR_CARDTYPE that are needed to respond to Mastercards New Card Range.
We were told the following by Bank of America First Data:
Effective October 14, 2016, MasterCard will introduce a new Bank Identification Number (BIN) range beginning with a ‘2’ (222100-272099). Transactions on MasterCard card numbers beginning with a ‘2’ must be accepted and follow the same logic and handling as MasterCard card numbers within the existing 510000-559999 range.
--Tom
This is the first I've heard of this update to MasterCard. Any assistance on changes we may have to make would be helpful.
Christopher Cuhel
The 5th Avenue Theatre
Actually, the numbers in TR_CARDTYPE don't seem to be used actively anywhere. I think it might be obsolete.. SQL Search can't find any reference to it outside itself, except for a FKish field in TR_ACCOUNT_TYPE, which is not in use (all values NULL)
The function that looks like it handles card validation (dbo.FS_VALIDATE_ACCOUNT) only refers to TR_ACCOUNT_TYPE. That one has a field .card_prefix, which can have multiple, variable length values for one cardtype, comma separated. So I would think the minimum change needed would be to change that from "5" to "5,2".
Although the system table Guidelines does say Do not change values for 1 (Visa) 2 (MasterCard) and 3 (American Express), so that might be a bit Brave, before TN give us a go-ahead.
And there may be others, of course...
Ken
Hi Tom
AFAIK, nobody's ever told us about it, but when I saw your
There's plenty of time for us to prepare, I suppose, but you might have thought that MC would have made some effort to make all of its merchants aware by now. People with less flexible systems than Tessitura might need a substantial lead time.
K