Sign with Turkish ID card
Customers sign with the chip on their ID card and a PIN, without buying a qualified certificate.
Process management for signatures made with a Turkish ID card or qualified certificate under Law 5070. RFC 3161 timestamps, PAdES-B-LTA archiving and verification links.
Overview
Sign is a platform that manages the electronic signing of contracts and forms that used to need a wet signature, and their archiving as e-documents, under Turkish Electronic Signature Law No. 5070. Customers sign with their chip-enabled Turkish ID card (TCKK) and PIN, so they don't have to buy a certificate. The organisation's authorised signatories sign with a qualified electronic certificate (NES).
Sign Bilişim is not an electronic certificate service provider and does not issue electronic certificates. Qualified electronic certificates are issued by electronic certificate service providers authorised by Türkiye's Information and Communication Technologies Authority (BTK). Sign Bilişim runs and oversees the electronic signature and e-documentation processes for signatures made with those certificates. Signing order, signer requirements, timestamp and archive steps and the verifiability of the document are controlled within that process.
Each signature gets an RFC 3161 compliant timestamp, and the document is upgraded automatically to the PAdES-B-LTA long-term archive level. The certificate chain and the validity and revocation evidence are embedded in the file, so the signature can still be verified years after the certificates expire. The private key stays on the card, and the server only prepares the document hash.
Ready-made flows cover single-customer standard contracts, doorstep signing in the field and multi-party corporate agreements. Internet service providers and other organisations, more than 89 in total, run the signing of their subscription and contract paperwork on Sign. A REST API and webhooks connect it to your existing CRM and subscription systems.
Compliance & standards
Sign
Customers sign with the chip on their ID card and a PIN, without buying a qualified certificate.
Authorised signatories sign with a NES obtained from an authorised provider. The signature value is created on the card, so the private key never reaches the server.
Every signature gets an RFC 3161 compliant timestamp and the document moves up to PAdES-B-LTA automatically.
Any number of signers sign in a fixed order, each with its own NES or TCKK requirement, and the next one gets a link, SMS or email automatically.
Every signed document gets its own shareable verification page and a QR code for quick checks.
REST API, Swagger documentation, a Postman collection and a webhook on every status change.
Send the contract from the portal or through the API. Set the signers, their order and whether each one signs with TCKK or NES.
The customer signs with ID card chip and PIN, and the authorised signatory with NES. The next signer is notified by link, SMS or email.
Each signature gets an RFC 3161 compliant timestamp and the document is upgraded to the PAdES-B-LTA long-term archive level.
The signed document goes to your chosen destination automatically. Anyone can check it through the shareable link or QR code.
Ecosystem
ISP & SME Management: CRM, Pre-Accounting & WiRadius
Cetvel cloud CRM and pre-accounting, with WiRadius ISP subscriber management on top: RADIUS sync, TR-069, BTK reports and a field app.
Learn moreOmnichannel Customer Messaging & AI Assistant
WhatsApp, Instagram, Messenger, Telegram, WebChat and phone in one inbox, with an AI assistant that answers from your CRM records.
Learn moreB2B/B2C Network & Fiber Optic Store
B2B/B2C store for network, Wi-Fi, GPON and fiber optic products from MikroTik, Ubiquiti, V-SOL and other brands, for resellers and end users.
Learn moreNo. Sign Bilişim is not an electronic certificate service provider and does not issue qualified electronic certificates. Qualified certificates are obtained from electronic certificate service providers authorised by BTK. Sign Bilişim runs and oversees the electronic signature and e-documentation processes for signatures made with those certificates and with Turkish ID cards.
No. Customers sign with their chip-enabled Turkish ID card and PIN. A qualified electronic certificate (NES) is only used where the flow calls for it, for example for the organisation's authorised signatories.
The evidence needed to verify it is stored inside the file. At PAdES-B-LTA level the certificate chain, validity and revocation evidence and an archive timestamp are embedded, so the signature still checks out after the certificates expire. Each document also has a shareable verification link and QR code.
No. The server only prepares the document hash and the signature value is generated inside the card, so signing on the server is technically impossible. PINs are never logged at any layer.
Yes. Upload the PDF to the free document analysis tool to see whether its signatures, certificate chain and timestamps are valid.
Yes. There is a REST API with Swagger (OpenAPI) documentation and a Postman collection, and a webhook fires on every status change. You can send documents for signing from your own panel and build custom signing chains through the API.
Yes. New portal accounts get 20 free contracts for the first month. No installation or credit card is needed, and there is no obligation if you stop.
Tell us briefly what you want to set up, or give us a call. We'll pass it to the right team.