Help
1. What you need
- A phone with Android 14 or later.
- To verify a signature you only need the signed file; no key is needed.
- To sign: a key file and its password from your qualified trust service provider (КНЕДП), a screen lock (PIN, pattern or password) and an internet connection.
2. Supported key files
| File | What it is | Notes |
|---|---|---|
Key-6.dat | IIT key container (both variants) | Holds two keys; the app picks the signing key from the certificate. The file usually contains no certificate. |
.pfx, .p12 | PKCS#12 | Protected with GOST 28147, DSTU 7624 (Kalyna) or AES. |
.pk8 | Encrypted PKCS#8 | The certificate has to be looked up or imported separately. |
.jks | PrivatBank key store | Usually contains the certificate. |
Not supported: .zs2, .sk and other unknown formats; hardware tokens, the ID card and cloud keys; electronic seal keys (the app says that electronic seals are not supported yet).
If a certificate says that its key is held in a qualified signature creation device (a protected token) but you import the key from a file, the app refuses: such a file should not exist. See If your key is compromised.
3. Importing a key
- Set a screen lock if you have none: Android settings → Security → Screen lock.
- In the app open Keys → Add key and choose the key file in the file picker.
- Enter the key password: the one set when you received the key from your provider. It is not the phone’s PIN.
- The certificate. If the file contains it, the app takes it from there. If not, the app asks for permission to contact your provider’s certificate lookup service (HTTPS only). If the provider has no such service over HTTPS, the app shows the provider’s page where you can download your certificate (
.ceror.crt), and you import it in the same step. - The app checks the certificate chain and that the key really matches the certificate.
- Choose the protection: the key password (always) and, if you like, your fingerprint.
- The key appears in the list with its signature level, owner, provider and validity.
Keep the original key file somewhere off the phone. The app keeps neither the file nor the password, and keys are excluded from Android backups and are not moved to a new phone. The original file is your backup: you need it to import the key on a new phone or after the screen lock is turned off.
If you enter a wrong key password when signing, the app shows how many attempts are left from the 5th mistake. After the 10th, the password-protected copy of the key is deleted: you can then sign only with your fingerprint (if you turned it on), and to use the password again you have to import the key from its file.
4. Signature levels: УЕП and КЕП
The Law of Ukraine “On Electronic Identification and Electronic Trust Services” distinguishes several kinds of electronic signature. A qualified electronic signature (КЕП) can only be made with a qualified signature creation device: a protected device that holds the private key, such as a hardware token or a qualified provider’s cloud service. A key file on a phone is not such a device, whatever software library the app uses. A signature made with a key file and a qualified certificate is therefore «УЕП на кваліфікованому сертифікаті», and the app never calls it КЕП.
| Label in the app | Meaning | The app |
|---|---|---|
| «КЕП» | qualified electronic signature | verifies; does not create |
| «УЕП на кваліфікованому сертифікаті» | advanced electronic signature based on a qualified certificate for electronic signatures (Law 2155-VIII, Art. 1 item 59) | verifies; creates it from a key file, the highest level it creates |
| «Удосконалений ЕП (сертифікат не кваліфікований)» | advanced electronic signature with a certificate that is not qualified | verifies |
| «Електронний підпис» | electronic signature without the features of an advanced one | verifies |
| «Електронна печатка» | electronic seal of a legal entity | verifies only |
When only КЕП will do
- Transactions that need notarisation or state registration (Article 17, part 6 of the Law).
- Registration actions of state registrars and notaries, and signatures of the senior officials listed in Article 17, part 2 of the Law.
Other public authorities and officials may use УЕП on a qualified certificate. Cabinet of Ministers Resolution No. 1298 also accepts it for electronic public services unless a law requires КЕП. Whether a particular recipient accepts your signature depends on their requirements; if in doubt, ask in advance.
5. Signing
- Tap Open on the home screen, or send a file to Цифровий підпис from another app.
- After an unsigned file has been checked, tap Sign. For a package of unsigned files, tap Sign all.
- The app checks the certificate online and shows the review screen.
- Check what you are signing, then confirm with your fingerprint, or with the key password together with the screen lock.
- Save the result or share it.
- Basic signing result. One unsigned file, including PDF or XML, or a package of 2–29 unsigned files is placed in one ASiC-E container with an XAdES signature and a timestamp (B-T). The input files’ contents remain unchanged inside the container.
- The review screen shows the PDF pages, or the file’s name, type and size; its SHA-256 hash; the signer, organisation, partly hidden tax number, provider and validity; the format, level and time-stamping service. If a PDF contains comments, filled-in fields, attached files, scripts or earlier changes, the app lists them and asks you to confirm separately.
- One confirmation covers only the files on the review screen. Before handing over the result, the app verifies the signature it made; if that check fails, no result is produced.
- Basic signing limits: up to 29 files, up to 32 MiB per document, and a resulting container up to 32 MiB. The total content size is also checked during preparation.
6. Verifying signatures
- Open → a
.p7s,.asiceor.asicsfile, a signed PDF or XML. A detached.p7ssignature also needs the original file. - The result says “verified by the app” with the signature level. It is the app’s own check, not a qualified validation; a qualified validation is offered only by a qualified trust service provider. The app links to the check on the ЦЗО (Central Certification Authority) portal.
- Without online checks (the setting is “Never”, or there is no network) the result relies only on data in the file, and the app says so.
From the verification result you can save the report as PDF or print it through Android. The report contains the verification details and the file name and hash; it does not include the document itself. This is the app’s report, not a qualified validation.
7. Network use and consent
Before its first network request the app shows a consent screen with “Allow” and “Don’t allow”. What is sent:
- certificate serial numbers and issuer data, to the status services (OCSP, CRL) of the provider that issued the certificate;
- key identifiers, to the provider’s certificate lookup service (HTTPS only), when the key file has no certificate;
- a hash derived from the document and its signature, to a time-stamping service;
- trust data requests, to czo.gov.ua.
Documents, keys and passwords are never sent. Requests to some status and time-stamping services use plain HTTP because that is how those services work (the others get HTTPS); their answers are signed and the app checks them. Details are in the privacy policy.
Settings → “Verification and network”: online checks “Always”, “Ask” or “Never” (if no mode has been chosen, the default is “Always” with current recorded consent allowed, and “Ask” otherwise), mobile data on or off, and the trust data version, date and update. Signing always needs a status check and a time stamp; if the setting or a mobile network prevents them, the app explains this before signing and offers a one-time check.
8. The screen lock and your keys
- Importing needs a screen lock: imported keys are protected by Android Keystore, which is tied to the screen lock.
- If you turn off the screen lock, or it is forcibly reset (for example by a device administrator), Android destroys the Keystore keys that protect imported keys, and those keys become unusable. The key list then shows that the key must be imported again from its file («Потрібен повторний імпорт з файлу ключа»): import it again from the original file. A factory reset also erases everything.
- Changing your PIN, pattern or password without turning the lock off does not destroy keys.
- Adding a new fingerprint in Android settings, or removing all fingerprints, disables only the fingerprint copy of the key; you can still sign with the key password. To sign with a fingerprint again, turn it on for the key under Keys and confirm with the key password. Remove any fingerprints you do not recognise in Android settings first: every fingerprint enrolled at that moment will be able to sign.
9. Troubleshooting
Wrong password
- Enter the password of this particular key file, the one set when you received the key from your provider. It is not the phone’s PIN or a token PIN.
- Check the keyboard layout (Ukrainian or English) and capital letters: the password is case-sensitive.
- Make sure you picked the right file: your provider may have issued keys to you at different times.
- When signing, the number of attempts is limited; see Importing a key.
Certificate not found
- Most key files contain no certificate; the app looks it up with the provider’s service over HTTPS. Allow network requests on the consent screen.
- If the service is unavailable or the provider does not support HTTPS, download your certificate (
.ceror.crt) from the provider’s website (the app shows the link) and import it in the same step. - The certificate must belong to this key: a new key needs a new certificate.
- An expired certificate cannot be used for signing; ask your provider for a new one.
Provider unreachable
- Check the internet connection and Settings → “Verification and network”: is “Never” selected, is mobile data allowed?
- Some networks (corporate, public Wi-Fi, VPNs) block plain HTTP, which some status and time-stamping services use. Try another network.
- The provider’s service may be down for a while; try again later.
- Without the certificate status the app does not sign: Cabinet of Ministers Resolution No. 1298 forbids signing when the status cannot be obtained. Verification then shows that the status was not checked online.
- If the app says that a service address has changed and an update is needed, update the app on Google Play.
Wrong date or time
- The app compares the phone’s clock with the time of the provider’s and the time-stamping services. If they differ by more than 5 minutes, signing stops with a message that the phone’s date or time is wrong.
- Turn on automatic date, time and time zone: Android settings → System → Date & time. Then sign again.
Other messages
- Electronic seals are not supported yet: a seal key of an organisation cannot be imported in this version.
- A key from a protected token found in a file: see If your key is compromised.
- File too large: see the limits under Signing.
- Signing is turned off because the trust data is older than 180 days or a critical update is out: update the app on Google Play.
10. If your key is compromised
A key is compromised if the key file or its password may have reached someone else: the phone or a storage device was lost or stolen, someone knows the password, or signatures appeared that you did not make.
- Stop signing with this key.
- Tell the provider (КНЕДП) that issued the certificate without delay, and ask them to block or revoke the certificate. The app shows the provider’s contacts under Keys → the key → Key compromised; they are also on the provider’s website and in the list of providers on czo.gov.ua. How to do it (by phone, in an online account or in person) depends on the provider.
- Delete the key from the app (Keys → the key → Delete) and from other devices.
- Get a new key and certificate from your provider.
- Review documents signed after the possible compromise and tell the other parties if needed.
If your phone is lost: the key in the app is protected by the screen lock and the key password or your fingerprint, but still tell your provider, because the key file may exist elsewhere. You can erase the phone remotely with Google’s device finder (android.com/find); the imported keys are then destroyed.
Your duty under the law. Article 12 of the Law of Ukraine “On Electronic Identification and Electronic Trust Services” requires people who use electronic trust services to keep the private key secret, to tell their provider without delay about a suspected or actual compromise of the key, and not to use a key that is compromised or whose certificate is revoked or blocked.
Only the provider can block or revoke a certificate; StalkerSoft cannot.
11. Support
- support@stalkersoft.com: we reply within 3 working days. Please include the app version (Help in the app), your phone model and Android version, what you did and the error code; you may attach the diagnostics file, which contains no documents, names or keys.
- Never send us key files, passwords or documents.
- Vulnerabilities: security@stalkersoft.com; we acknowledge reports within 48 hours. See Security.
- We reply to Google Play reviews every week.