How Long Does EMV L3 Certification Take?
A standard single-scheme campaign, run in-house on a platform we already know, typically takes 2–4 weeks from kickoff to scheme submission. Multi-scheme work, an unfamiliar platform, or a queue at a shared lab can stretch that to months — here's what actually drives the difference.
The Timeline Depends on Four Things
Single vs. Multi-Scheme
Each scheme — Visa, Mastercard, Amex — is its own test plan and its own submission. A campaign covering three schemes isn't three times the work, but it isn't a flat 2–4 weeks either.
Familiar vs. New Platform
A terminal we've already certified comes with known EMV kernel behaviour. A new one needs that discovery work done first, before testing even starts.
Defect Volume & Complexity
A clean application sails through. One that fails TVR/TSI checks or has fallback-handling bugs means rework cycles — the least predictable part of any timeline.
In-House vs. Shared Lab
The single biggest lever, and the one least related to how ready your terminal actually is — see below.
Kickoff to Submission, In-House
Scope 1–2 days
Platform, EMV kernel version, target scheme(s) and certification level confirmed before work starts.
Execute 1–2 weeks
UL BTT and FIME test plans run across contact, contactless, fallback and PIN scenarios.
Analyze Concurrent
Field 55 deep dives and TVR/TSI interpretation as results come in, not after the full run finishes.
Fix & Retest Variable
Defects go straight back to the development team — same day when we built the application, fast when we didn't.
Submit 2–3 days
Evidence packaged and carried through scheme submission.
Steps 1, 2, 3 and 5 are fairly fixed. Step 4 is where a clean application finishes in two weeks and a defect-heavy one runs longer — and it's the step most affected by whether the certification team can fix code directly or has to hand it to someone else. More on that in why certification projects get delayed.
One thing this timeline doesn't include: scheme review time after submission. That's set by the scheme itself, not by the testing vendor, and it's worth planning for separately.