MasterCard Bin 2 Series In Play: Declines and Fines

Posted on by

Previously, MasterCard announced a new card number BIN series, requiring everyone in the payment ecosystem to update in order to support the new card acceptance. Merchants need to update software and or terminals to comply by the June 30, 2017 mandate deadline. The consequences are both transaction declines and heavy fines.

Credit card processing:

  • Traditional countertop terminals may need a software download, contact your processor.

    Verifone vx520 emv terminal

    Verifone vx520

  •  Point of Sale solutions or the payment gateway that drives terminals need to be updated. This may occur seamlessly in the background with no impact to merchants and nothing to download.
    verifone MX915 EMV terminal

    Verifone MX915 EMV chip terminal

    Equipment & Payment Gateway NOT affected:

    • Authorize.net
    • BridgePay
    • Cayan
    • CenPOS
    • Clover
    • Ingenico w/ EMV Chip Card Technology
    • First Data w/ EMV Chip Card Technology
    • Future POS (Version 5.0.96.30)
    • Gravity Gateway
    • Lavu
    • Merchant Link
    • Micros
    • NMI
    • Payeezy
    • Paytrace
    • Shift 4
    • Shopkeep
    • Swipe Simple
    • USAePay/Gravity Link

    Credit Card Terminals Requiring a Software Update:

    • Apriva cellular terminal
    • FD 50 TI (Non EMV Chip Card)
    • FD 100 TI (Non EMV Chip Card)
    • FD 130 (Non EMV Chip Card)
    • FD 200 TI (Non EMV Chip Card)
    • Ingenico (Non EMV Chip Card)
    • Verifone VX520

    Credit Card Terminals Requiring Replacement: These terminals are end of life and cannot be updated.

    • All Hypercomm Terminals
    • Fd 50 (non TI)
    • FD 100 (non TI)
    • FD 200 (non TI)
    • FD 300 (non TI)
    • VX 510
    • VX 570

    Consequences for non-compliance with MasterCard Bin 2 Series

  • Mastercard Transactions for cards beginning with a 2 in the range of 222100-272099 will be declined.
  • If you do not update your software before the deadline, you will fall into a status of non-compliance. A non-compliant occurrence is defined as any attempted and failed transaction that is confirmed as failed due to a merchant’s lack of readiness to support 2-Series BIN transactions.
    • $2,500 per occurrence in the first 30 days.
    • Escalating up to $10,000 in the next 60 days.
    • Up to $20,000 per occurrence for the subsequent violations.

    These fines may be assessed per merchant location per failed transaction for not implementing support of the new cards.

    Fines will be pushed to acquirers. If acquirers are compliant, but the merchant is not, the fines will be passed down. If you’re sitting on old software and terminals, now is the time to change! It’s simple for MasterCard to identify non-compliance.  Contact us for immediate help- keep your merchant account, get new compliant credit card processing technology.

Disclaimer: This list and accompanying information may be out of date at any time. Check with your acquirer for the most current information.

 

Leave a Reply