Electronic signatures in JordanBuilt for business
in Jordan.

Electronic signatures in Jordan follow Electronic Transactions Law No. 15/2015. A European qualified signature is a separate Enterprise option, and it is not on Essential or Pro.

Simple electronic signature on Essential and Pro · QES for Europe is an Enterprise option

Service agreement

Signed

Example

Completed with the evidence record

Art. 17Evidential weight for a protected or authenticated signature

GazetteArticle 1: in effect on publication

15/2015Electronic Transactions Law

PDF + recordDownload the evidence

One flow. A clear record.

Confidence from send to signed.

A clear signing path that records intent, each action, and the evidence behind the agreement.

  1. 01

    Prepare and send

    Upload the document, place the fields, and name every signer.

    See how it works
  2. 02

    Accept and sign

    Each signer accepts the electronic process and signs the fields you placed.

    See how it works
  3. 03

    Prove and keep

    Download the completed PDF together with its evidence record.

    See how it works

Everyday agreements

Document types you can sign with inSigner

Upload a PDF and keep the completion record with the file. The completion record is the file and its SHA-256 hash. It does not issue a Jordanian electronic authentication certificate.

  • Sales

    1. Sales contracts
    2. Order forms
    3. Quotes
    4. Proposals
    5. Statements of work
    6. Master service agreements
    7. Change orders
    8. Renewal agreements
  • Customers

    1. Service agreements
    2. Onboarding packets
    3. Subscription agreements
    4. Acceptance forms
    5. Delivery receipts
    6. Project briefs
    7. Support agreements
    8. Customer addenda
  • Vendors

    1. Vendor agreements
    2. NDAs
    3. Purchase orders
    4. Consulting agreements
    5. Contractor agreements
    6. Supplier questionnaires
    7. Referral agreements
    8. Partnership agreements
  • People

    1. Offer letters
    2. Employment agreements
    3. Handbook acknowledgments
    4. Policy acknowledgments
    5. Commission plans
    6. Performance plans
    7. Equipment agreements
    8. Contractor packets
  • Property

    1. Letters of intent
    2. Offers
    3. Broker engagement letters
    4. Property management agreements
    5. Move-in checklists
    6. Maintenance addenda
    7. Parking agreements
    8. Work orders
  • Company

    1. Internal approvals
    2. Policy updates
    3. Meeting acknowledgments
    4. Access requests
    5. Travel approvals
    6. Expense approvals
    7. Confidentiality acknowledgments
    8. Project sign-offs

And many more.

Evidence, not just a signature

Every action leaves a clear record.

The completion record brings together who was invited, what they signed, and the hash of the final file.

Evidence record

Example
Status
Completed
Signers
The people you invited
Integrity
SHA-256 hash of the final file

If the file changes, the hash no longer matches. Download it with the PDF.

  1. 01

    Consent to sign

    The record keeps the acceptance of the electronic process.

  2. 02

    Signer attribution

    Name, email or phone, and the send, view, and sign events.

  3. 03

    Time-stamped events

    A chronological record from delivery to completion.

  4. 04

    Document integrity

    A SHA-256 hash shows whether the final file still matches.

Commercial agreements

One record. Many everyday documents.

The same completion record for commercial agreements that do not need the national signature this page describes. A European qualified signature is a separate Enterprise option.

  • Business

    Sales contracts

    Vendor agreements

    NDAs

  • Operations

    Proposals

    Orders

    Statements of work

  • People teams

    Offer letters

    Policy acknowledgments

  • More than one team

    The same flow

    In the languages you already use

Questions, answered

What teams in Jordan ask us.

The limits sit here, including the statute this page cites and the claims this page does not make.

Contact our team

What inSigner covers

The parts of an electronic signature flow in Jordan that the service offers today.

Are electronic signatures legal in Jordan?

Electronic signatures in Jordan follow Electronic Transactions Law No. 15/2015. Article 1, in the Central Bank Arabic text and in the Bank's English text, brings the law into effect on the date of its publication in the Official Gazette. Article 17 gives the evidential weight of an ordinary bond to an electronic record that carries a protected or authenticated electronic signature. That protected and authenticated status is not every electronic mark. inSigner is not a Jordanian licensed authentication party. A European qualified signature is a separate Enterprise option, and it is not on Essential or Pro.

What does the statute do?

Electronic Transactions Law No. 15/2015 is available in the Central Bank of Jordan Arabic text and in the Bank's English text. Article 1 says the law enters into effect on the date of its publication in the Official Gazette. Article 15 deems an electronic signature protected only when all of these are met: it is uniquely connected to the signatory and distinguishes that person; it identifies its owner; the private key is under the signatory's control at the time of signing; and it is connected to the electronic record so that the record cannot be modified after signing without a change to the signature. Article 16 deems the signature authenticated when Article 15 is met and the signature is connected to an electronic authentication certificate issued at the time of creation by a licensed electronic authentication party, an accredited electronic authentication party, a government body authorized by the Council of Ministers that meets the Telecommunications Regulatory Commission requirements, the Ministry of Information and Communications Technology, or the Central Bank for banking or financial electronic operations. Article 17(a) gives an electronic record that carries a protected electronic signature the evidential weight of an ordinary bond, which the parties may rely on. Article 17(b) gives that weight to a record that carries an authenticated electronic signature, which the parties and others may rely on. Article 17(c) says that, in other cases, a record that carries an electronic signature has that weight against the parties, and if the signature is denied the burden is on the party who relies on the record. inSigner is not a Jordanian licensed or accredited electronic authentication party and does not issue a Jordanian authentication certificate.

How does the record show who signed and what they signed?

Each person signs the fields you placed in the document you sent. The evidence record keeps their name and email address or phone number, when the document was sent, viewed, and signed, the IP address, the device details, and the authentication used.

Can I download evidence for a completed document?

Yes. You can download the completed PDF and the evidence record, including a SHA-256 hash of the final file. If a single byte changes, the hash no longer matches.

What inSigner does not cover

The limits, including the claims this page does not make.

Is the standard signature a qualified electronic signature?

No. The standard inSigner signature is not a protected or authenticated electronic signature under Law No. 15/2015, and it does not have the Article 17(a) or 17(b) effect. A European qualified signature is an Enterprise option. It is not a protected or authenticated electronic signature under Law No. 15/2015, and it is not included on Essential or Pro.

Can every document go through inSigner?

No. A protected signature under Article 15, and an authenticated signature under Article 16, require every stated condition, including control of the private key and, for authentication, a certificate from one of the listed parties. Article 17(c) leaves the burden on the party who relies on another electronic signature if it is denied. inSigner does not issue a Jordanian authentication certificate.

Does inSigner make our workflow GDPR compliant?

No. Jordan is not in the European Union, and the GDPR does not apply as Jordanian law. For the documents you send, you are the controller and Nubesti is the processor under the data processing agreement, which includes the EU Standard Contractual Clauses where that agreement uses them. inSigner does not decide whether your workflow meets the personal-data rules that govern it, and it does not write your notices. Nubesti is the controller for the account, billing, security, support, and marketing.

Does inSigner cover clinical consent, account opening, or round-the-clock regulated workflows?

No. This page does not offer patient forms, clinical consent, account opening, or credit agreements as a regulated program. Identity checks such as KYC are add-ons priced separately, not the default. inSigner does not publish an uptime percentage or a public status page, and it does not decide the legal effect of a document.

This page is general information about electronic signatures in Jordan, not legal advice. The signature policy in the legal center is the binding text. Responsibilities for electronic signatures

Your next agreement in Jordan starts here

Send it. Sign it. Prove it.

Create an account and send a commercial agreement with its completion record.

Start signing free