View source for TachoSync Company Card Authenticator

[[Category:TachoSync]] 
<!--- FOR EDITORS
PER PREZENTACIJĄ EVALDAS DARĖ VEIKSMUS PER WINDOWS SERVICES – PARAŠYTI ČIA?
--->
==Overview==
The '''Company Card Authenticator (CCA)''' is a software bridge that makes a tachograph company card accessible for remote downloads.

*Tachograph files can only be decrypted and downloaded if the company card is periodically present during the authentication process.
*CCA ensures that the tachograph server can “see” the card over the internet, even though the card itself is physically inserted into a card reader somewhere (either at the provider or the end-client).
*CCA does not store tachograph files themselves. It only provides the “live presence” of the company card to the system.


==PC Requirements for CCA==
For CCA to work properly with TachoSync, the PC on which CCA is installed '''must always be turned on and online'''.

PC Requirements for CCA:
* OS: Windows 10; Windows 11.
* CPU: Intel or AMD processor with 64-bit support.
* Disk Storage: 500 MB of free disk space.
* Internet connection: Required for downloading and operation.

'''TachoSync authentication service IP address and port:
* '''Address: https://tacho.teltonika.lt (3.126.35.133)
* '''Port: 7066


==How to Install CCA==
[[File:CCA.png|right]]
# Go to '''[https://tacho.teltonika.lt TachoSync]'''.
# Go to "Settings" in the top menu and select '''"Company Card Authenticator"'''.
# A window opens. Select the latest version and click '''“Download"'''. 
# Open the downloaded file and install CCA.
# Run CCA.
Your card reader is now able to remotely authorize tachograph data downloads.

For more information on how to add company cards, please refer to [https://wiki.teltonikagps.com/view/TachoSync_Interface#Adding_a_Company_Card Adding a company card]

<div style="clear:both;"></div>

== Latest official CCA version can be also downloaded here ==

{| class="wikitable"
!Version!!Release Date!!Link
!Release Notes
|-
|'''1.2.1'''||'''2025-09-15'''||[[File:Download_zip.png|x60px|link=Special:Redirect/file/Company Card Authenticator v1.2.1.zip]]
|<ul style="margin:1;">
* Fixed a rare issue where some smart card readers (PC/SC) did not retrieve ATR command correctly.
* Fixed an issue with Lisle devices where a card slot could appear occupied, but the card information was missing. The system now re-checks the slot to ensure the card is properly recognized.

</ul>
|-
|1.2.0||2025-09-11||
|<ul style="margin:1;">
* Improved authentication speed when using Lisle Hyper Card racks – authentication is now 3–4 times faster compared to the previous version.
* Fixed a problem in larger Lisle Hyper Card rack setups (50+ company cards) where some cards were not identified correctly when inserted or after a service restart. The initial card reading mechanism has been improved to ensure all cards are detected reliably.
* Fixed an issue where smart card readers (PC/SC) were released too early in some cases, which would cause unexpected errors during communication with company cards.
</ul>
|-
|1.1.0||2025-07-04||
|<ul style="margin:1;">
* Disabled internal logging to internal.log, keeping only the main application logs. This prevents uncontrolled file growth and simplifies troubleshooting.
* Updated the Card ID logic to use the full ICC (Integrated Circuit Card) value instead of CardExtendedSerialNumber, ensuring better uniqueness and alignment with tachograph standards.
* Improved connection reliability between the CCA application and the TachoSync server.
* Applied minor stability improvements throughout the application.
</ul>
|-
|1.0.0||2025-04-25||
|<ul style="margin:1;">
* Reduced memory usage to improve performance and stability.
* Added TLS 1.3 encryption for communication with the TachoSync server.
* Added a new 'Card number' column to the CCA monitor view, displaying the official company card number used.
</ul>
|-
|}

==CCA Interface==
[[File:Company Card Authenticator interface window.png|link=Special:Redirect/file/Company Card Authenticator interface window.png|frame|200px|alt=Company Card Authenticator interface|Company Card Authenticator interface]]

The CCA provides the name of the connected smartcard reader(s) and the following information in a table:
* Card slot - identifier of card slot in the reader.
* Card ID - a unique identifier assigned by the smart card chip - '''copy this ID to TachoSync when adding a new company card - see [[TachoSync Interface#Companies|“Companies”]] for more information'''.
* Card Number - card serial number that is printed on the card (and encoded electronically) that uniquely identifies the card.
* Status - card status.
* Company - name of the company.
* Valid from - validity start date.
* Valid until - validity end date.

==Hosting Models==
'''1. Centralized Card Management (Provider-hosted CCA)

*The service provider (our direct client) collects physical company cards from its customers (end-clients, e.g., transport companies).
*These cards are stored in card hotels / hyper-racks (hardware racks that can host many cards at once).
*The CCA software runs on the provider’s infrastructure, making all stored cards available to the tachograph server.

'''Key highlights:
*End-clients do not need to install anything.
*Provider must handle logistics (collecting cards, renewing expired ones, securing them).
*Works best for providers serving many small transport companies that do not want local IT hassle.

'''2. Local Deployment (End-client hosted CCA)
*The end-client (transport company) keeps the company card on-site, usually in a single-slot USB smart card reader connected to a PC.
*The CCA application is installed on that PC.
*The CCA ensures that the tachograph server can access the card remotely, but the card never leaves the company’s premises.
'''Key highlights:
*Security-sensitive clients prefer this, because the card never leaves their office.
*No logistics of sending cards away.
*The provider doesn’t need to maintain a card hotel.

==FAQ Company Cards==
====What is the best way to sync daily 200 vehicles at one company account with many company cards?====

:The best approach is to use '''multiple company cards''' within the same company account. TachoSync allows you to '''assign specific vehicles to be authorized by specific cards''', which helps distribute the load efficiently.

:Additionally, you can optimize the download process by '''splitting the schedule into two groups''':

:*Schedule the first 100 vehicles to sync at 08:00
:*Schedule the remaining 100 vehicles to sync at 15:00

:This method prevents overloading the system, ensures more stable performance, and allows all vehicles to complete their downloads successfully within the day.

====Do I need to split each company card into separate companies?====

:No, it’s not necessary to separate each Company Card into different companies.

:TachoSync allows multiple Company Cards under the same company account. '''You just need to make sure each card is properly authenticated''' and assigned within the same company environment.

====Does TachoSync support more company cards under one company account?====

:Yes, TachoSync supports multiple Company Cards''' within a single company account. 
:This is a common setup for large fleets. Each Company Card can authenticate downloads for vehicles assigned to the same company, provided the cards are properly configured in the system.

====Is it possible to download from many vehicles at one company at the same time using multiple company cards?====

:'''Yes, simultaneous downloads are supported.'''

:If multiple Company Cards are connected (via local CCA or hosted solution), the system can initiate parallel downloads from multiple vehicles within the same company. This significantly improves performance and reduces the time required to sync large fleets.