Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 25 Apr 2016 11:14:12 +0000 (UTC)
From: "Tim Deboer (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12957514.1460268799000.22669.1461582852957@Atlassian.JIRA>
In-Reply-To: <JIRA.12957514.1460268799000@Atlassian.JIRA>
References: <JIRA.12957514.1460268799000@Atlassian.JIRA>
 <JIRA.12957514.1460268799782@arcas>
Subject: [jira] [Commented] (VALIDATOR-392) Mastercard Series 2 bin ranges -
 active as of October 2016
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/VALIDATOR-392?page=3Dcom.atlass=
ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1=
5256218#comment-15256218 ]=20

Tim Deboer commented on VALIDATOR-392:
--------------------------------------

Hi Sebb,

Your suggestion sounds good. The same methodology is use with diners and di=
scover cards.=20

In regards to the timing of the new ranges there are many options. Here are=
 a couple:
1) provide an override mechanism where the reg expression can be passed in =
manually. This way those who need this functionality on the required date c=
an override the default. In a future release you can add the new range into=
 the default settings.
2) move the bin range config into a properties file in the jar file. Do it =
in such a way as to make all cards configurable. Therefore you can add/remo=
ve schemes or change ranges at will by putting any custom config in the cla=
sspath.
3) Release a jar closer to the October date and don't provide an override m=
echanism. Might be hard for applications using this library to update their=
 application to use this new jar if you leave it for too long. I know in my=
 case it takes months for a release to be made and then for it to hit produ=
ction.

In my use case i'd rather the change be made early and a release cut asap. =
We only use it as a first level check prior to sending the card to a back e=
nd system. This would not apply to everybody though.

> Mastercard Series 2 bin ranges - active as of October 2016
> ----------------------------------------------------------
>
>                 Key: VALIDATOR-392
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-392
>             Project: Commons Validator
>          Issue Type: Improvement
>          Components: Routines
>    Affects Versions: 1.5.0
>            Reporter: Tim Deboer
>            Priority: Minor
>
> Mastercard is releasing new series 2 bin ranges. Quote from their informa=
tion sheet is:
> "To help ensure that MasterCard and its customers are best positioned to
> enable the next generations of payments, MasterCard is expanding the
> Bank Identification Number (BIN) range by introducing a new range of 2
> series BINs (222100=E2=80=93272099) that will be processed in the same ma=
nner as the MasterCard 51=E2=80=9355 series BINs are processed today."


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)