USE CASE — Use Case

EMV Payment Modernization for Public Transport

Open-loop contactless payment validators with NFC, secure element, and ITxPT compliance — replacing proprietary closed-loop cards and unlocking €10-40M public transit contracts.

THE PROBLEM

Transit Validators Still Use Proprietary Cards — and Are Losing EU Tenders

European public transport is undergoing a payment revolution. EU Regulation 2021/782 and national digitalization mandates increasingly require open-loop payment acceptance — allowing passengers to pay with standard EMV contactless cards (Visa, Mastercard) or mobile wallets (Apple Pay, Google Pay) instead of proprietary transit cards.

Transit validator manufacturers that still rely on closed-loop MIFARE-based systems are being disqualified from tenders worth €10-40M per city deployment. The EMV open-loop requirement is no longer a "nice-to-have" — it is a mandatory technical criterion in 60-70% of new European transit tenders. Companies without certified EMV validators cannot even submit bids.

The engineering challenge is substantial. EMV contactless payment requires Level 1 (NFC hardware) and Level 2 (EMV kernel) certification from payment networks. The validator must integrate a secure element or HSM for transaction processing, support transit-specific schemes (cEMV, ITSO, Calypso), comply with ITxPT architecture standards for vehicle integration, and operate reliably at -20C to +55C in ruggedized enclosures. This combination of payment security, embedded hardware, and transit-domain expertise is rare — and exactly what Promwad delivers.

60-70%
EU Tenders Requiring Open-Loop
€10-40M
Typical City Deployment Contract
14-18%
Contactless Transit Market CAGR
6-12 months
EMV Certification Timeline
THE SOLUTION

Open-Loop EMV Validator with NFC and Secure Element

Promwad designs and certifies a complete open-loop payment validator for public transit — from NFC antenna design through EMV kernel integration to ITxPT-compliant vehicle connectivity. The validator supports both contactless EMV (tap-to-pay) and legacy closed-loop cards during the transition period.

The architecture prioritizes security and certification speed. A dedicated secure element handles all payment processing in a tamper-resistant environment, while the application processor manages transit logic, fare calculation, and vehicle integration. This separation allows the payment core to be certified independently, reducing the recertification burden when transit-specific features are updated.

L1
NFC Reader Module
NXP PN5180 or ST25R3916 NFC controller. Custom antenna design optimized for transit environment (metal housings, passenger flow). EMV Level 1 certified contactless interface. ISO 14443 A/B and ISO 15693 support for legacy cards. Read range 40-50mm for reliable tap-and-go.
L2
Secure Core
Infineon SLE 97 or NXP SE050 secure element for EMV transaction processing. EMV Level 2 kernel (Visa payWave, Mastercard PayPass, UnionPay QuickPass). PCI PTS point-of-interaction compliance. Tamper-resistant key storage with FIPS 140-2 Level 3 equivalent.
L3
Transaction Engine
ARM Cortex-A7/A53 application processor. Transit fare calculation engine supporting flat-fare, zone-based, and best-fare-capping algorithms. Offline transaction storage (10,000+ transactions). Aggregation and batch upload to payment backend. cEMV transit scheme support.
L4
Backend & Fleet Integration
ITxPT-compliant vehicle communication (MQTT/AMQP over Ethernet). GPS-based zone detection for fare calculation. Fleet management API for validator monitoring and remote configuration. Payment backend integration (acquirer interface, reconciliation). OTA firmware update with secure boot chain.
BEFORE vs. AFTER

Before vs. After: Transit Payment Systems

Dimension
Before
After
Payment Acceptance
Proprietary cards only (MIFARE/Calypso)
EMV contactless + mobile wallets + legacy cards
Tender Eligibility
Excluded from 60-70% of new EU tenders
Qualified for all open-loop tender requirements
Passenger Experience
Must purchase and load proprietary card
Tap any bank card or phone to ride
Fraud & Revenue Leakage
Card cloning, fare evasion with expired cards
Bank-grade security, real-time transaction validation
Operational Cost
Card issuance, top-up infrastructure, cash handling
Zero card issuance cost, automated reconciliation
IMPLEMENTATION

Implementation Roadmap

1
NFC Module & Hardware
4 months
NFC reader hardware design with custom antenna
EMV Level 1 contactless interface testing
Secure element integration (hardware + firmware)
Ruggedized enclosure prototype (IP54, -20C to +55C)
Basic transit validator PCB with application processor
2
EMV Certification
10 months
EMV Level 1 certification (contactless interface)
EMV Level 2 kernel integration and certification
PCI PTS compliance testing
Transit fare engine (flat, zone, capping algorithms)
Offline transaction storage and batch processing
ITxPT architecture compliance testing
3
Fleet Deployment
16 months
Production hardware with DFM optimization
Payment backend integration (acquirer APIs)
Fleet management platform (remote monitoring, OTA)
Pilot deployment on 50-100 vehicles
Performance validation and fare reconciliation audit
CE marking and type approval for EU markets
EXPECTED OUTCOMES

Expected Outcomes

80%+ more bids
Tender Eligibility Increase
€10-40M per city
Contract Value Access
70-90%
Fraud Reduction
100% eliminated
Card Issuance Cost Savings
40-60% in Year 1
Passenger Adoption (Open-Loop)
10 months
Time to EMV Certification
FREQUENTLY ASKED

Can the validator support both old proprietary cards and new EMV during the transition?

Yes. The NFC reader supports ISO 14443 A/B (MIFARE, Calypso) alongside EMV contactless. Transit operators typically run both systems in parallel for 2-3 years during migration. The fare engine handles both card types with unified trip accounting.

How long does EMV certification take?

EMV Level 1 (contactless interface) typically takes 2-3 months. EMV Level 2 (kernel certification) takes 4-6 months. PCI PTS compliance adds 2-3 months. Total certification timeline is 6-12 months depending on test lab availability and first-pass success rate. Promwad's experience with payment hardware accelerates the process by avoiding common certification pitfalls.

What about mobile ticketing and QR codes?

The validator architecture supports QR code reading via an optional camera module for barcode-based mobile tickets. However, the primary value proposition is EMV open-loop — which is the requirement driving tender eligibility. QR ticketing can be added as a secondary feature without affecting EMV certification.

Does Promwad handle the payment backend as well?

Promwad designs the validator hardware and firmware, including the secure transaction processing and offline storage. The payment backend (acquirer integration, reconciliation, settlement) is typically provided by a payment processor partner. Promwad delivers the acquirer API integration on the validator side.

RELATED
Start a Pilot →