CPT 3000v3ML
The mobile and SWP configuration of CPT. An SWP reader lets you verify payment applets on a UICC or SIM in a closed loop, without a real handset. NFC testing uses a configuration that includes real devices.
The testing problems this solves
CPT 3000v3ML addresses issuance data verification in mobile and SWP environments. An SWP reader lets you check payment applets on a UICC or SIM in a closed loop, without a real handset. Systematic testing removes the gaps, reliance on individuals and lack of reproducibility that tend to appear at this stage.
Scope of verification
Uses an SWP reader to verify payment applets on a UICC or SIM in a closed loop, without a real handset.
| Aspect | Coverage |
|---|---|
| What SWP is | Single Wire Protocol: the communication between the secure element on a phone's UICC or SIM and the NFC controller |
| Closed-loop testing | Simulates the UICC or SIM, the phone-side behaviour and the contactless terminal behaviour, so testing needs no real handset |
| NFC testing | Uses a configuration that includes real handsets |
| When an SWP reader is needed | Optional for Mastercard Mobile PayPass; required for full Visa VMPA and VMCPS testing |
| Base functionality | Includes the personalisation verification functions of CPT |
| Interface | NFC, SWP, contact and contactless |
Supported terminals and environments
Intended for mobile issuance environments using NFC and SWP. The device requirements are confirmed at quotation.
Example test configuration and licences
These configurations and licence names are examples based on public information. Current SKUs, the hardware options required and specification versions are confirmed at quotation.
| Category | Example |
|---|---|
| Multi-layer | Multi-layer protocols |
From the Barnes International range. Some entries derive from an older configuration table.
What is verified
| Mobile payment applications | Verified with the test scripts for Visa VMCPS, Mobile Mastercard PayPass and Amex ExpressPay Mobile |
|---|---|
| Interface | NFC+SWP |
Choosing between the CPT and CAT series
CPT checks whether a card matches a defined specification; CAT lets you develop the checking logic itself. The certification modules are additional software that runs on CPT or CAT, not standalone products.
| Product | Main role | Interfaces covered | Custom script development |
|---|---|---|---|
| CPT 3000v3 | PVT for contact EMV cards and magnetic stripe | Contact IC and magnetic stripe | Generally none; QuickTest settings are used instead |
| CPT 3000v3CL | PVT including contactless and dual interface | Contact, contactless, magnetic stripe and NFC devices | Generally none |
| CPT 3000v3ML | Verification of mobile payment and SIM/UICC | NFC, SWP, contact and contactless | Generally none |
| CAT 3000v3 / CL / ML | CPT functionality plus custom test script development | Depends on the configuration | Yes (Tcl) |
| Certification test modules | Scheme-specific PVT and certification testing | Through modules | Defined by the scheme |
| G2V2 Tachograph Card Test Tool | Verification of digital and smart tachograph cards | ISO/IEC 7816 contact | — |
Platform generations (v3 and v4)
Please confirm this at procurement. According to Barnes support information, the current core version of CPT 3000v3 and CAT 3000v3 is 3.71.0 (31 March 2026), and for CPT v4 it is 4.3.1.239 (15 May 2026). The v3 line continues to receive current versions for the Visa Europe Self-Service and other scheme certification modules and for quality control. The Mastercard, Visa Global Self-Service, JCB and Discover certification modules, however, are provided on CPT v4. Supported modules, library versions and certification schemes are re-confirmed at the time of deployment.
| Situation | What we recommend |
|---|---|
| You are continuing to inspect existing cards on an installed CPT 3000v3 | Continuing maintenance on v3 may be possible |
| New deployment | In principle CPT v4 should be considered first |
| You use an older module for a particular scheme | We check v3 compatibility case by case |
| The latest Visa or Mastercard self-certification | This configuration is likely to require v4 |
| You have existing custom CAT scripts | We check whether migration to v4 is possible, Tcl compatibility, and conversion cost |
| You own a reader dedicated to v3CL or v3ML | We check whether it can be reused with v4 |
Buying the base unit does not by itself enable certification for every scheme. The base unit, the CL and ML functions, the scheme modules, Host Simulation, the HSM connection, the reader, and maintenance and script updates may each be a separate licence or option. For new proposals we recommend v4 as the base platform, with the required modules configured individually.
v3ML dates from a time when mobile payment was largely UICC and SIM based. If you need to evaluate what is common now — HCE, OEM wallets, embedded secure elements, tokenisation and cloud-based lifecycle management — v3ML alone may not cover the required scope. Before proposing a configuration we establish which of HCE, eSE or UICC is in scope; whether testing is against a real wallet or the secure element applet alone; whether token requestor and TSP-side testing is included; whether CDCVM, device binding and token cryptograms are in scope; and how the work connects to approval flows such as Visa VTS and Mastercard MDES.
Example configurations
Which elements you need depends on the use case. At quotation we always confirm the interface scope of the reader and the licences.
| Use | Components |
|---|---|
| Standard configuration for EMV cards | CPT v4 or CPT 3000v3, a Barnes 3K7 Triple Interface Reader, the PVT scripts for the schemes concerned, the certification module for those schemes, and annual maintenance with script updates |
| Configuration including cryptographic verification | The above plus the Host Simulation Module and issuer keys, or the HSM Interface and the HSM concerned |
| Developing your own card application | CAT 3000v3CL or its successor, Tcl Script Development, contact and contactless readers, and Host Simulation or an HSM if required |
| Mobile and UICC | The ML configuration of CPT or CAT, an SWP reader, an NFC reader, real handsets, and the mobile scheme scripts concerned |
| Tachograph card | The G2V2 Tachograph Card Test Tool, an ISO/IEC 7816 reader, the G1, G2V1 and G2V2 test suites, the licence for the card types concerned, test certificates and key sets, and an HSM if required |
Where it is used
- Setting up card issuance and QC verification for a new development
- Regression after a configuration change or update
- Coverage checks ahead of certification
Relationship to certification
What this product performs is a conformance check on the issued card. It can be used for pre-certification testing before submission to the scheme, but passing here does not guarantee passing formal certification.