You connected your e-signature device, but your name does not appear on the transaction screen. This alone does not mean that your certificate is damaged, expired or unusable. Recognition of a USB device, reading its certificate in card management software, and listing that certificate in an institution's application are separate stages. Following that sequence helps you investigate without unnecessarily changing a working setup. This article provides a diagnostic plan rather than device-specific installation instructions.

Stage one: Does the computer recognise the device?

Start with the physical connection. If a card goes into a separate reader, check its position; if you use a USB-format device, check that it is properly seated. When a hub or adapter is involved, compare with another suitable connection. A lit indicator does not prove that data communication is working. Equally, a device without an indicator is not automatically faulty. Follow the manufacturer's explanation for the model you have.

On Windows, Device Manager can help establish whether a reader or unknown device is listed. Record any error code exactly. Consult your IT department before making driver changes that require administrator privileges on a work computer. Do not install a random driver without identifying the card or reader model. A package intended for another product may not solve the problem and can make diagnosis harder.

Stage two: Can the card software read the certificate?

If the operating system recognises the device, open the appropriate card management tool. Note separately whether the software sees the device but no certificate. When a certificate is visible, check its holder, issuer, validity dates and serial number. With several certificates present, knowing which one you examined is important. Deleting a certificate, formatting a card or resetting a device is not an appropriate diagnostic shortcut.

If a PIN is requested, do not repeatedly try codes you are unsure about. Device recognition and PIN access are different issues. When a block warning appears, stop guessing and follow the official PIN procedure. You do not need to send your PIN to a support agent in a message. Do not assume that investigating an installation issue requires another person to know your personal signing secret.

Stage three: What does the institution's application require?

A certificate can be visible in card management software while a browser transaction screen remains empty. The institution's signing component then needs investigation alongside the card connection. The component may need to be installed and running with a supported operating system and browser. A successful transaction in another service is useful evidence, but it does not establish that every service uses identical components.

Read the institution's current guide. Do not remove all Java installations or disable the firewall merely because an old video recommends it. Some current institutional signing tools include their own runtime, while other applications have different requirements. Identify the application and its version before applying a standard repair recipe to every computer with a similar error message.

Stage four: Make a controlled comparison

Where possible, test your own device on another computer you are authorised to use and whose setup is known. Change one variable at a time: first the connection, then the computer if necessary. Changing drivers, browsers and security settings together makes it difficult to identify what affected the result. Borrowing another person's signing device or PIN is not a safe comparison method.

How to record an observation

For example, the reader may appear in Windows and your name may appear in the card tool, while the institution offers no selectable certificate. Record those three results separately. Identify the empty screen rather than simply saying that the computer cannot detect the device. Add the connection you tested and its result. Stop if a test unexpectedly requests a PIN change or certificate deletion, and first establish what the screen is asking. Mention an approaching filing deadline in your support request, but do not treat that deadline as a guaranteed resolution time. The first error screen alone cannot establish whether replacement hardware or a new certificate is needed. Gather observations before requesting an assessment.

What should a support request include?

• The device and reader model, including any hub or adapter.
• Operating system, card software and institutional application versions.
• The stage at which the problem occurs and the exact error text.
• Recent changes to a previously working setup and steps already tried.

Use this information when contacting E-İmzaTR Online Support. Obtain current files from our software and documentation page. These links open Turkish pages. Certificate support and the institution's own application support may both be relevant. The first useful result is an accurate description of where the process stops.