feat: support full MIR BIN range 2200–2204#183
Open
S3os wants to merge 1 commit intocaseyryan:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added missing MIR BIN codes
2201,2202, and2203to the card system data.This completes support for the full MIR BIN range
2200-2204.Previously, some valid MIR card numbers were not recognized correctly due to incomplete BIN coverage.
Source
According to official MIR documentation, the first 4 digits of a card number must be in the range
2200-2204(see p.11):https://cdn.bspb.ru/Rukovodstvo_dlya_sotrudnikov_TSP_PS_MIR_04a412b7b2.pdf
Tests
Added tests covering MIR BINs
2200-2204, including:Result
MIR cards within the full BIN range are now correctly recognized, validated, and formatted.