Questions worth asking.

SimplySign and card signatures have 1, 2 or 3-year options. This refers to the certificate. We establish the intended use and requirements before ordering.

Certum cloud and card seals have 1, 2 or 3-year options. Read the actual validity start and end in the issued seal certificate.

SimplySign and card signature renewal offers 1, 2 or 3 years. You need a currently valid certificate and must complete the appropriate procedure.

Do not assume the same route. Seals can be issued for another 1, 2 or 3-year term; we establish the process after checking the format and organisational details. A signature renewal code is not automatically a seal product.

Start with your workflow and signing applications. The cloud needs suitable applications and Internet access; a card requires a compatible reader and software. I will help compare these requirements.

Contact me about a new certificate. Standard signature renewal requires an unexpired certificate. Buying a code alone does not restore an expired signature.

Do not calculate validity solely from the purchase date. Read the dates in the certificate. We establish activation timing and available settings in the relevant process.

No. A signature image does not prove a qualified signature was applied. The signature stored in the file and its validation result are what matter.

A seal identifies an organisation and confirms a document’s origin and integrity. It does not replace a person’s signature where their declaration is required.

A KSeF certificate has purposes within that system. Do not choose it as a replacement for a general qualified signature for contracts and other files.

Your enquiry, workflow, application name and whether your existing certificate is valid. Do not send identity scans, PINs, passwords or tokens.

Not having PESEL does not by itself exclude SimplySign. We check the identity document, its validity and your target system’s requirements before choosing. Tell me what you need to do.

SimplySign supports mobile use. We still check whether your particular task and application work on a phone; some systems require a computer.

It depends on compatibility between the reader, card and computer. Tell me the model. Replacing every component is not automatic; continued use needs checking.

Check the operating system, ports, installation permissions and target application requirements. Coordinate the workstation setup with IT before activation.

Issuance and application readiness are separate stages. Certificate installation or access activation may still be needed. Finish with a test signature and validation.

Timing depends on the selected route, complete information and available verification method. Tell me your deadline; a purchase alone does not establish completion.

Yes, with software and a format that support additional signatures. Pass on the current file with existing signatures and check the result after each operation.

Possible causes include the format, attachments, certificate data or permissions. Inspect signature validation and the portal message separately. Signing does not establish compliance with every recipient requirement.

They are not editable like ordinary document text. Describe the change so we can establish its effect on the certificate and the appropriate next steps.

Establish whether only the device is lost or signature access is also compromised. Suspected unauthorised access requires prompt use of the provider’s certificate procedure. Describe the situation without sending codes.

Renewal concerns the next certificate. Validation of an older file assesses its signature and available time evidence; the new certificate’s date is not a substitute.

Required organisational details, identifiers and the current verification route need checking. State the EPREL purpose before choosing.

Yes. We discuss users, roles, workflows and activation planning. Business terms and the support scope are arranged individually.