IDTECH ViVOpay VP3350

Questions and Answers

K
Kyle RamirezAug 15, 2025
How to fix an IDTECH ViVOpay VP3350 Card Reader that won't power on (no LEDs light up)?
- L
  laurenjacksonAug 15, 2025
  If your IDTECH Card Reader doesn't seem to power on, with no LEDs lighting up, the issue might be that the reader is not powered on or the battery is out of charge. Try these steps: * Connect the device to a PC via a USB cable, as the device could be set to automatically power on and enter charging mode. * Replace the device with another unit known to work to verify that the installed USB cable wiring works correctly.
D
David BrennanAug 18, 2025
What to do if LEDs don't light and the beeper is silent when using a card or fob with my IDTECH ViVOpay VP3350 Card Reader?
- K
  Kimberly BergerAug 18, 2025
  If the LEDs don't light up and the beeper is silent when presenting a card or fob to your IDTECH Card Reader, the problem could stem from several causes: * The card, fob, or phone not properly presented. * RF interference. * An unsupported card being used. * Incorrect firmware. Try these solutions: * Present the card, fob, or phone closer to the antenna, ensuring it is parallel to the reader's face. * Verify the card, fob, or phone is valid and current. * Ensure metal isn't interfering with the antenna. * Check if the card, fob, or phone is damaged. * Make sure the power cable plug is fully inserted. * Ensure the device is not set to Passthrough mode.
J
Jaime HartmanAug 21, 2025
How to resolve no data received or garbled data on IDTECH ViVOpay VP3350 Card Reader?
- J
  Jeffrey ThomasAug 22, 2025
  If you are experiencing no data received or garbled data with your IDTECH Card Reader, the cause might be faulty or incorrect cable connections. Check that the cable connection is secure and in the correct port on the device.
J
Juan WilsonAug 25, 2025
What to do if firmware loading software indicates “Open device failed” for IDTECH Card Reader?
- M
  Mr. Eric RamirezAug 25, 2025
  If the firmware loading software indicates “Open device failed” for your IDTECH Card Reader, the device is not fully connected to the PC. Check the cable connection and the device.
T
Tommy CarrollAug 27, 2025
How to fix 'Load firmware failed' error on IDTECH Card Reader?
- M
  morrisonjosephAug 27, 2025
  If the firmware loading software indicates “Load firmware failed” for your IDTECH Card Reader, this means that the device is not fully connected to the PC. Check the cable connections.
J
john47Aug 30, 2025
Why is Bluetooth pairing failing on my IDTECH Card Reader?
- R
  Robert DaughertyAug 30, 2025
  Bluetooth pairing on your IDTECH Card Reader might fail if the host device is running Android 6.x or earlier, or if the mobile device doesn't work in BLE security mode. To resolve this: * Make sure the host device is running Android 6.x or later. * Ensure the host device connects to the VP3350 in BLE Mode 1 and Level 4.
K
Krista WilliamsSep 2, 2025
Why does my IDTECH Card Reader read some cards but not others?
- M
  Michelle ThompsonSep 2, 2025
  If your IDTECH Card Reader reads some cards or fobs but not all, it could be due to a bad card or fob, an unsupported card being used, or wrong firmware. Check the card or fob for damage. Also, verify that the correct firmware is loaded on the reader.
A
Allison WoodSep 5, 2025
What does it mean when my IDTECH Card Reader fails to start a transaction and returns 0x0B?
- M
  Michael BellSep 5, 2025
  When your IDTECH Card Reader fails to start a transaction and returns 0x0B, it indicates the device is either in Passthrough mode or transaction mode. You need to exit Passthrough mode or cancel the transaction.
V
velazquezbarbaraSep 8, 2025
What to do if IDTECH ViVOpay VP3350 fails to start transaction and returns 0x04?
- C
  chenryanSep 8, 2025
  When your IDTECH Card Reader fails to start a transaction and returns 0x04, it means there is a missing key. Please re-start VP3350 and monitor the LEDs to confirm whether to Load LCL key or Data Key.
E
Eric MarshallSep 12, 2025
Why does my IDTECH ViVOpay VP3350 Card Reader fail to start a transaction and return 0x60?
- T
  Thomas AlvarezSep 12, 2025
  If your IDTECH Card Reader fails to start a transaction and returns 0x60, it means that there is no terminal data or application data. You need to load terminal data or application data for Contact EMV transactions.

Summary

Warranty Disclaimer

FCC Warning Statement

ISED Statement

Cautions and Warnings

Internal Rechargeable Battery Warning

Provides critical safety information and instructions regarding the internal rechargeable lithium-ion battery.

Introduction

Major VP3350 Features

Contactless NFC Features and Brand Certifications

Lists the various contactless NFC standards and brand certifications the VP3350 supports.

Other Agency Approvals and Compliances

Details the regulatory and compliance approvals from various agencies like CE, FCC, UL, and EMV.

Operation and Storage: Environmental Limits

Specifies the recommended operating and storage temperature and humidity ranges for the device.

Power Consumption

Outlines the device's power consumption rates for different transaction types.

24-Hour Device Reboot

Explains the mandatory 24-hour device reboot requirement for PCI compliance.

VP3350 Connectors and Interfaces

Bluetooth Pairing Instructions

Battery Charging Instructions

Instructions on how to charge the VP3350 battery using a USB cable and the LED indicators for charging status.

VP3350 LED and Sound State Indicators

Explains the meaning of different LED patterns and sound cues indicating device status and events.

Tamper and Failed Self-Check Indicators

Details how the device indicates tamper events or internal self-check failures through LEDs and buzzer.

iOS Connectivity: BLE and VP3350

Guides on connecting the VP3350 to iOS devices using Bluetooth Low Energy (BLE).

ID TECH Universal SDK

Updating VP3350 Firmware

Recommends updating the VP3350 firmware using the Universal SDK and specifies the connection method.

Universal SDK Demo App

Using the Demo Application

Provides step-by-step instructions on how to use the Universal SDK Demo application on Windows.

VP3350 Low-Level Commands

Activate Transaction Command (02-40)

Details the command to initiate a contactless EMV or MagStripe Card transaction.

Set CA Public Key (D0-03)

Describes the command to add a new public key to the reader's configuration.

Get Processor Type (09-02)

Explains how to retrieve the processor type of the VP3350 device.

Get Main Firmware Version (09-03)

Details the command to retrieve the main firmware version of the reader.

Get Hardware Information (09-14)

Describes the command to obtain information about the reader's hardware components.

Get Module Version Information (09-20)

Explains how to retrieve the reader's module-specific version information.

Get Serial Number (12-01)

Details the command to retrieve the 15-digit serial number stored in the reader's memory.

Contact Set ICS Identification (60-16)

Describes the command to set the reader's ICS terminal configuration number.

Contact Set Terminal Data (60-06)

Explains the command to create new terminal data based on provided TLVs.

Contact Set Application Data (60-03)

Details the command to configure the device's AID (Application ID) settings.

Basic Card Reading Data Flow

Example: Reading a Card via Firmware Commands

Provides an example workflow for reading a card using NEO 2 protocol firmware commands.

Example: Reading a Card via Universal SDK Methods

Illustrates the process of reading a card using Universal SDK methods.

Example: Reading a Card via the USDK Demo App

Guides on reading a card using the USDK Demo application on a PC.

Periodic Inspection Instructions

Decommissioning PCI-Certified Devices

Troubleshooting

Tamper Detection Codes

Lists tamper event types and their corresponding security log codes for troubleshooting.

For More Information