Browser + smart card
The Trpass / Tawqe3y desktop app connects approved websites to the user's USB token or smart card. The private key never leaves the token.
Digital signatures and ETA e-invoicing
Sign, seal, validate and e-invoice with one platform: smart cards in the browser, remote certificates on iOS and Android, and your company seal in an HSM.
ETA-approved e-invoicing
ITIDA-licensed signing
ISO 27001 certified
On-prem, hosted or white-label
Partner apps built on SignLayer: NTRA FEDIS
Prototype: customer logos will be added once approved.
Every way people sign
Let people sign where they already are, and seal documents automatically when no person needs to be involved.
The Trpass / Tawqe3y desktop app connects approved websites to the user's USB token or smart card. The private key never leaves the token.
The iOS and Android SDKs sign PDFs with an ITIDA remote certificate, confirmed by a one-time password. No token needed.
Seal invoices and documents automatically with your organisation's key, held in a hardware security module.
Integration advisor
Tell us who signs, what they sign and where. Our AI-powered advisor suggests the SignLayer channel and the documentation to start with.
ETA e-invoicing
SignLayer eInvoice turns your invoices into ETA's canonical format, seals them with your company key and submits them for you.
Signing API
The SignLayer Signing API is the engine behind every channel. One JSON API signs, validates and timestamps.
PDFs as PAdES, and any file or data as CAdES, CMS or a bare signature, with a token, a phone or a seal.
PDFs, Office files, CMS and CAdES signatures, and certificates, with revocation checks through OCSP and CRL.
Trusted RFC 3161 timestamps from your Timestamp Authority, for PDFs and any file.
A visible signature on the PDF page with your logo, position and wording.
Separate trust lists, timestamp settings, HSM and branding for each customer, in one deployment.
Every operation is logged per customer, with daily usage statistics for operators.
Architecture
Channels on the left, the SignLayer platform in the middle, trust services on the right. Private keys stay in tokens, in ITIDA's remote key store and in HSMs; the Signing API never holds them.
Solutions
Connect your ERP or accounting system to SignLayer eInvoice. Invoices are converted to ETA's canonical format, sealed with your company key in an HSM and submitted for you.
Book an e-invoicing demoAdd remote signing to your iOS and Android apps with ITIDA certificates and an OTP, and seal statements and letters automatically with your HSM.
Book a demoRun SignLayer on your own infrastructure. Citizens and staff sign with smart cards or remote certificates, and documents are sealed with the authority's key.
Talk to us about on-premUse the public Signing API and SDKs for web, iOS and Android. Ship signing inside your ERP, portal or app, under your brand or ours.
Read the docsHow it works
Connect your web app, mobile app or ERP to the SignLayer API. Run it on your servers or use the hosted API.
Smart card in the browser, remote certificate on the phone, or the company seal in your HSM.
Every operation is logged. Validate any signed document at any time.
For developers
Sign and verify with plain HTTP calls. Use the browser SDK for smart-card signing and the iOS and Android SDKs for remote signing.
# Seal data with the company key (CAdES, detached)
curl -X POST https://signing.your-domain.com/sign/data \
-H "Authorization: $SIGNLAYER_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "signer": { "type": "hsm" },
"input": { "data": "SGVsbG8gV29ybGQ=" },
"output": { "format": "cades", "mode": "detached" } }'
# Verify it
curl -X POST https://signing.your-domain.com/verify \
-H "Authorization: $SIGNLAYER_API_TOKEN" -d @verify.json// Call from your backend. Never ship the API token to browsers or apps.
const res = await fetch(`${SIGNLAYER_URL}/sign/data`, {
method: 'POST',
headers: {
Authorization: process.env.SIGNLAYER_API_TOKEN,
'Content-Type': 'application/json'
},
body: JSON.stringify({
signer: { type: 'hsm' },
input: { data: Buffer.from(invoiceXml).toString('base64') },
output: { format: 'cades', mode: 'detached' }
})
});
const { statusCode, error, result } = await res.json();# Validate every signature in a PDF
import base64, os, requests
with open("contract-signed.pdf", "rb") as f:
pdf = base64.b64encode(f.read()).decode()
r = requests.post(
f"{os.environ['SIGNLAYER_URL']}/documents/pdf/validate",
headers={"Authorization": os.environ["SIGNLAYER_API_TOKEN"]},
json={"file": pdf},
)
print(r.json()["result"])Security and compliance
User keys stay on the smart card or token. Seal keys stay inside the HSM.
PDF signing runs as a separate internal service behind an encrypted channel.
Single-file server builds that install on current and older enterprise Linux, inside your network.
Egyptian root and intermediate CAs by default. Add or remove trusted CAs per customer.
Approved for Egyptian Tax Authority e-invoicing
Licensed for electronic-signature services
Certified information-security management
Certificate names, numbers and scope to be confirmed before launch.
FAQ
Qualified certificates from licensed Egyptian CAs on smart cards and USB tokens, ITIDA remote certificates on the phone, and your company seal certificate in an HSM.
Yes. SignLayer eInvoice builds the ETA canonical document, seals it with your company key and submits it. It can also fetch, cancel and reject documents.
Yes. The services install on your own Ubuntu or RHEL-family Linux servers, x86-64 or arm64. A hosted API is also available.
PDFs (PAdES), any file or data (CAdES, CMS or a bare signature), and ETA e-invoices. You can also validate PDFs, Office files and signatures.
Yes. Remote-signing SDKs are available for both iOS and Android.
As an on-premises licence per server, as a hosted API, or as a white-label build under your brand.
Pricing depends on channels, volumes and deployment. Book a demo and we will send a quote.
Book a demo
Tell us what you need to sign. A solutions engineer replies within one working day.