Tech & SaaS documents flowing to Jordan
Core documents Thai Tech & SaaS businesses send to Jordan: company affidavit (DBD) · MOA/AOA · audited financials · industry licences · contracts / MOUs · Power of Attorney.
Signature clauses Tech & SaaS contracts must carry: SLA 99.9% · Data processing addendum (PDPA/GDPR) · Subprocessor consent · Source code escrow · IP indemnity.
Typical counterparties and recipients in Jordan: Enterprise customer · Cloud (AWS/GCP) · Open-source contributor · VC investor · DGA — we confirm each authority's accepted format before filing.
Certification chain Jordan requires
Jordan is NOT a Hague Apostille member (full consular legalisation) — correct chain: 1) Thai MFA → 2) Jordan embassy in Bangkok → 3) (sometimes) destination ministry in Jordan
Thailand's accession to the Hague Apostille Convention enters into force on 28 February 2027 — for member states Apostille is dramatically faster.
Regulatory references typically cited in Tech & SaaS docs: PDPA 2019 · Electronic Transactions Act · Computer Crime Act · BOI Software promotion.
Common pain points & how we handle them
Tech & SaaS pain points: Data residency · Open-source license · Source code escrow · Cross-border payments — these drive frequent and urgent legalisation runs.
NYC Legal's approach: maintain a templated set per client → new filings take 2–3 business days instead of 2–3 weeks.
Add-ons: local-language certified translation for Jordan · courier to destination authority · online tracking.
FAQ
Why does Jordan need embassy legalisation?
Because Jordan is not a Hague Apostille member, consular legalisation (MFA → Jordan embassy) is required.
How long does it take?
7–14 business days depending on Jordan embassy queue.
What does it cost?
From THB 6,500 per document set — includes MFA fee, Jordan embassy fee and our courier time.
What corporate docs are needed?
DBD affidavit ≤30 days old · director ID copy · company seal · industry-specific docs (SLA 99.9%).






