Certificate-based signatures
Each signature uses an X.509 certificate issued by your workspace’s own certificate authority and is embedded in the PDF as a PAdES signature.
Create contracts, send them for signature and track every step. Signers confirm a one-time code sent to their email and sign in the browser; every signed PDF carries a certificate-based signature and an RFC 3161 timestamp.
Free · No credit card required
End-to-end solution from creation, signing, to contract management.
Each signature uses an X.509 certificate issued by your workspace’s own certificate authority and is embedded in the PDF as a PAdES signature.
Each workspace keeps its contracts separate and has its own certificate authority. Invite your team and give each member a role.
Create, track status, and store all contracts centrally on the cloud platform.
Send signing links to external partners, verify via OTP — no system account needed.
Upload a PDF or DOCX, or start from a DOCX template with variables. DOCX files are converted to PDF for signing.
Organization and platform seals, an RFC 3161 timestamp and a hash-chained audit trail: any change after signing shows up on verification.
Signing electronic contracts has never been this easy.
Draft or choose from existing templates
Upload PDF or DOCX
Invite relevant parties to sign
Confirm with an email code and sign in the browser
eContract is designed to flexibly meet the contract signing needs of various industries.
Centralized contract management, save on printing and paper storage costs.
Keep the signing history and a hash-chained audit trail for every contract.
Sign confidential contracts with patients, suppliers, and research partners.
Sign lecturer contracts, student agreements, and international collaborations remotely.
Quickly sign contracts with suppliers, agents, and distribution partners.
Several workspaces, team roles, a REST API and webhooks to connect your own systems.
Connect eContract to your own systems and AI tools.
Create, send and track contracts with an API key or OAuth 2.1. Webhooks tell your systems when a signer views, signs or declines.
AI agents connect over MCP to prepare and send contracts. A person always signs.
Suggests a title, summary and signers, and analyzes contracts. 30 requests per user per day.
Responsive web app: sign on a phone, tablet or computer. No app to install.
Every feature included, with fair-use limits. No credit card required.
What happens when someone signs, and how anyone can check it later.
The signer opens the signing link and confirms a one-time code sent to their email address before signing.
The signature is made with an X.509 certificate issued by the workspace’s own certificate authority and embedded in the PDF as a PAdES signature.
The organization seal of the workspace and the eContract platform seal are added to the signed PDF.
A timestamp authority records when the document was signed.
Each event — sent, viewed, signed — is logged with the time, IP address and browser, and linked to the previous event by a hash.
Anyone can upload a signed PDF on the verification page to check its signatures, certificates and timestamp. Changes after signing show up there.
eContract’s certificates come from its own internal PKI, not from a government-accredited certificate authority.
Automate the contract workflow: create a contract from a file or template, send it, follow its status and download the signed PDF and audit trail.
Documented with OpenAPI. Authenticate with an API key or an OAuth 2.1 access token.
Apps act in a workspace only after a user approves the requested scopes.
Connect an MCP-compatible AI client to the server URL below and sign in with OAuth.
Signed notifications when a contract is sent, viewed, signed, declined or completed.
MCP server URL
https://api.econtract.online/mcpAI agents prepare and send contracts. A person always signs.
Setup guides for:
eContract is a web platform for contracts and electronic signatures, operated by eContract.online. Teams create contracts from PDF or DOCX files or from templates, send them for signature and track their status; signers sign in the browser.
Yes. Every feature is free to use, with fair-use limits such as 30 AI requests per user per day. No credit card is required. If paid plans are introduced later, you will be told at least 30 days in advance.
Signers confirm a one-time code sent to their email. Each signature uses an X.509 certificate issued by the workspace’s own certificate authority and is embedded in the PDF as a PAdES signature with an RFC 3161 timestamp. Organization and platform seals and a hash-chained audit trail are added.
It depends on the jurisdiction and the type of transaction: some documents need a specific form or a signature from an accredited provider. eContract’s certificates come from its own internal PKI, not from an accredited certificate authority. Check with a legal adviser for your case.
Yes. AI agents can connect to the MCP server at https://api.econtract.online/mcp, or use the REST API with an API key or OAuth 2.1. Agents can prepare and send contracts and follow their status, but they cannot sign: a person always signs.
The interface is available in 17 languages: English, Vietnamese, Thai, Indonesian, Japanese, Korean, Chinese (Simplified and Traditional), German, French, Spanish, Italian, Dutch, Polish, Russian and Portuguese (Brazil and Portugal).
Open econtract.online/verify and upload the PDF. The page checks each signature, the certificate chain and the timestamp, and shows whether the file changed after signing. No account is needed.
Each workspace’s contracts are kept separate from other workspaces. Inside a workspace, access follows member roles, and signers see only the documents sent to them. The AI assistant processes document content with an external AI provider. The Privacy Policy explains how personal data is handled.
Create a free account and send your first contract for signature. No credit card required.