Specifications include, but are not limited to: System Capabilities: 1. Online real-time validation of contactless payment cards 2. Revenue risk controls at payment targets including, but not limited to, the following: a. Offline data authentication (ODA) b. Validation checks on locally-cached risk lists at devices that allow offline credentialchecking that have been seen previously c. Bank Identification Number (BIN) lookup to permit or block acceptance of specific card issuers or card types d. Expiry date check e. Pass-back check 3. Support advanced fare policy features including, but not limited to, fare capping. The configuration to support these fare policy features shall be configurable by WMATA. 4. The solution shall provide reporting capabilities supporting transaction, revenue, and financial reconciliation. 5. Support for Mass Transit Transaction (MTT) processing models including, but not limited to: a. Known Fare Transaction Model b. Aggregated Transaction Model 6. The open payment solution shall include the MTT processing models as a configurable risk model, which shall be updateable per the variances between new card scheme risk rules as necessary. 7. Full support for MTT functionality including, but not limited to, the following functionality: a. Fare aggregation b. Refunds c. Deny list check d. Nominal authorization / Account verification request checks on new card or card not recently seen e. Deferred authorization f. Deny list management and distribution g. Debt recovery (including tap driven, merchant initiated (scheduled), cardholder) h. Zero value debt clearing i. Clearing/Settlement 8. The open payment solution shall be fully Level 1, 2, and 3 certified at the time of proposal from the appropriate authority. 9. Ensue secured platform open payment transactions that is EuroPay, Mastercard, and Visa (EMV) compliant and Payment Application Data Security Standard (PA-DSS) certified. 10. Ability for WMATA customers to view travel history with the amount charged.
