Cross-Border Contracts: How to Legally Sign International Agreements Online

The first time I tried to close a deal with a German manufacturer from my desk in Austin, I learned something embarrassing. I sent over a beautifully formatted PDF, dropped it into our e-signature tool, and felt pretty good about myself. Two weeks later, their legal team came back with a polite but firm note: "We will require a Qualified Electronic Signature for this." I had no idea what that meant. I'd been signing US contracts electronically for years and assumed the same workflow would just... work everywhere.

It doesn't. And if you're selling SaaS internationally, working with overseas freelancers, or onboarding distributors in three continents, you've probably hit your own version of that wall.

This is a practical, practitioner-level guide to signing international agreements online without getting yourself into a contract that's technically unenforceable. I'll talk through the four main legal frameworks, where they overlap, where they don't, and the specific traps that catch SMBs all the time. This isn't legal advice — for high-value deals, regulated industries, or anything where a mistake would actually hurt, talk to a real lawyer. But for most of what small businesses sign every week, this guide will keep you out of trouble.

Why cross-border contracts are weird

Here's the thing about e-signature law: every country wrote its own. There's no single global treaty that says "an electronic signature is valid worldwide." Instead you have dozens of national laws, a few regional frameworks, and a patchwork of mutual-recognition arrangements that mostly work but sometimes don't.

A signature that's bulletproof in Texas might be merely "presumed valid" in Berlin and entirely worthless in Sao Paulo. A clickwrap agreement that holds up in Singapore might fail in Mexico because the local Code of Commerce wants something more formal. The same PDF, the same signer, the same intent — different outcomes depending on where the dispute lands.

This isn't because lawmakers are being difficult. It's because each jurisdiction had to figure out, at some point between roughly 1999 and 2014, how to translate centuries of wet-ink contract law into the digital world. They each made slightly different choices about what counts as a signature, what counts as identity, and what records you need to keep.

If you want the deeper background on how electronic signatures work generally, I wrote a whole electronic signature legal guide that's a good companion piece to this one.

The four frameworks you actually need to know

Almost every cross-border contract you'll sign falls under one of four families of law. Let's go through them.

1. ESIGN and UETA (United States, since 2000)

The US has two laws that work together. The federal ESIGN Act (2000) says electronic signatures and records can't be denied legal effect just because they're electronic. UETA (the Uniform Electronic Transactions Act) is a state-level law adopted by 49 states that does roughly the same thing.

Both are technology-neutral. They don't care whether you used a fancy cryptographic certificate or just typed your name into a form. As long as the signer intended to sign and you have a reasonable record, you're good. This is wonderful for ease of use and absolutely terrifying for anyone trying to interpret it conservatively.

There are exceptions — wills, family law, some real estate, certain notices — but for ordinary B2B and B2C commerce, electronic signatures are fine.

2. eIDAS (European Union + UK kept its own version)

In 2014 the EU passed the eIDAS Regulation (Regulation 910/2014), which introduced a tiered system that's now the model most of the world copies in some form. The UK left the EU but kept a near-identical UK eIDAS in place, with a few procedural differences around trust service providers.

eIDAS recognizes three tiers:

• SES (Simple Electronic Signature): Basically the same as a US ESIGN signature. Type your name, click a box, draw with your mouse. Legally valid but you have to prove intent and identity if challenged.
• AES (Advanced Electronic Signature): Uniquely linked to the signer, capable of identifying them, created with means under their sole control, and tamper-evident. Most professional e-sign platforms produce AES by default if you enable identity verification.
• QES (Qualified Electronic Signature): AES plus a qualified certificate from a Trust Service Provider listed on the EU Trusted List, plus a qualified signature creation device. QES has the same legal weight as a handwritten signature across the EU and is presumed valid without any further proof.

The full breakdown is in our piece on the EU eIDAS regulation if you want the details.

3. The APAC patchwork

Asia-Pacific doesn't have a unified framework. Each country did its own thing, and they're surprisingly different.

• Singapore — Electronic Transactions Act (2010, updated 2021). Two-tier: electronic signatures and "secure" electronic signatures. Pragmatic and business-friendly.
• Japan — Act on Electronic Signatures and Certification Business (2001). Recognizes electronic signatures with a presumption of authenticity if certain conditions are met. Hanko (personal seals) culturally still matter for some domestic deals but international contracts work fine electronically.
• Australia — Electronic Transactions Act 1999. Tech-neutral, similar in spirit to ESIGN. Each state also has its own ETA mirror.
• India — Information Technology Act 2000. Recognizes "digital signatures" using asymmetric cryptography and certificates from licensed CAs. Stricter than most — typed names alone won't always cut it for formal documents.

If you're closing deals across APAC, expect to think about each country individually.

4. The LATAM patchwork

Latin America is similar — no unified framework, lots of national variation.

• Brazil — MP 2.200-2/2001 created ICP-Brasil, a national PKI. Signatures using ICP-Brasil certificates have full legal equivalence to handwritten ones. Other electronic signatures are valid if both parties agree.
• Mexico — The Codigo de Comercio (Commercial Code) recognizes electronic signatures since 2000, with the FIEL (now e.firma) as the qualified equivalent for tax and government use.
• Argentina, Chile, Colombia, Peru — All have their own digital signature laws. Most distinguish between simple electronic signatures and qualified/digital ones backed by certificates.

LATAM tends to favor PKI-based qualified signatures for anything formal. Simple click-to-sign is usually fine for commercial agreements between private parties, but government or notarized documents almost always need the qualified flavor.

Quick comparison table

Mutual recognition: the good news

Here's the part that surprises people: mutual recognition between these frameworks mostly works, especially for B2B.

If a US company and a German company sign a contract using a normal e-signature platform, both sides can typically enforce it in their home courts. Why? Because most modern legal systems will recognize a foreign electronic signature as long as:

1. Both parties agreed to use electronic signatures
2. The signature reliably identifies the signer
3. The document hasn't been tampered with after signing
4. There's a clear audit trail

That's the practical reality for everyday business. The catches come when you hit specific document types that have local requirements.

Where it breaks: document types with local rules

Some contracts can't be signed electronically at all, or require a specific tier in specific countries. Common examples:

• Germany: Some employment-related documents (notice of termination, fixed-term employment contracts under certain conditions) require either a wet signature or a Qualified Electronic Signature. Sending a standard SES, even from a US ESIGN-compliant platform, isn't enough. This bit me on the deal I mentioned at the top.
• France: Real estate transfers, mortgages, and certain consumer agreements have form requirements that often need notarization or QES.
• Brazil: Anything submitted to government, courts, or notaries needs an ICP-Brasil certificate.
• India: Documents that need to be registered (property, certain commercial agreements) require physical execution or specific government-approved digital signatures.
• Most countries: Wills, divorce, and adoption papers usually require wet signatures or notarization.

The lesson: just because a country allows electronic signatures generally doesn't mean every document type can be e-signed. When in doubt, ask local counsel.

Choice of law clauses: small text, big impact

This is one of the most important clauses in any cross-border contract and it's often treated as boilerplate. Don't.

A choice of law clause says which country's laws will be used to interpret the contract. A jurisdiction clause says which country's courts will hear disputes. They're usually paired but they're not the same thing.

Why does this matter for e-signatures? Because if you choose California law and a California venue, then California's e-signature rules govern enforceability. If you choose German law, eIDAS rules apply. If you don't choose at all, the courts will pick — using rules that vary widely and rarely favor whoever drafted the contract.

For SMBs signing international agreements, my rule of thumb: pick the legal system you understand best, and that you'd realistically be willing to litigate in. If you're a US company, US law and a US venue is usually safer than picking somewhere exotic. If you're EU-based, your home country plus arbitration in a major hub (London, Paris, Singapore) is reasonable.

The other party will sometimes push back. That's fine — it's a negotiation. Just don't let it become an afterthought.

Governing language: the binding text

If your contract is bilingual, one of the languages is usually designated as the "binding" or "official" version. Translations are reference material, not law.

This is huge. I once saw a deal where the English version said "exclusive distributor" and the Spanish translation accidentally said "preferred distributor." The Spanish-language party argued the Spanish was binding because the contract was performed in Mexico. They lost — but only because the contract had a clear English-binding clause. Without that clause, courts often default to the language of the country of performance, which can wreck you.

Pick a binding language. Say it explicitly. Make sure both versions actually match (this is where decent translators earn their fee).

Time zones in timestamping

Tiny detail but it bites people. When a signature platform timestamps a signing event, what time zone does it use? Most use UTC or the server's local time. The signer's claimed location might be elsewhere.

For most contracts, this is fine — the audit trail records the absolute moment of signing, and that's enough. But for time-sensitive deals (option exercises, deadline-driven agreements, regulatory filings) you want the timestamp to be unambiguous. Use UTC or include timezone explicitly. And if you're filing something with a regulator, check what time standard they expect.

The notarization problem: apostilles don't cross borders for free

Here's something a lot of people don't know: notarized documents don't automatically work in other countries.

If a document is notarized in the US and you need to use it in, say, Brazil, you usually need an apostille — a certificate issued under the Hague Convention of 1961 that authenticates the notary's seal for international use. Without the apostille, the foreign authority won't accept the notarization.

This matters for cross-border deals involving:

• Powers of attorney
• Corporate authorization documents
• Certain commercial registrations
• Real estate involving foreign buyers or sellers
• Some loan and security documents

E-notarization is starting to exist (the US, India, and a handful of other countries allow it in some forms) but cross-border recognition of e-notarized documents is still inconsistent. If you need notarization for international use, plan for the apostille step. It can take days or weeks.

Real-world SMB scenarios

Let's get specific about how this hits actual small businesses.

SaaS sold internationally. You're a US-based SaaS selling to companies in Germany, Japan, and Brazil. Your standard online subscription agreement, click-accepted at signup, is fine for nearly all of them. ESIGN/UETA handles the US side. The other side is bound because they consented to electronic terms when they signed up. The exceptions are if your contract triggers regulated industries (financial services, healthcare) or if you're selling to a government entity, where local procurement rules can demand specific signature types.

Freelancers with global clients. If you're a freelancer in the Philippines billing clients in the US, EU, and Australia, your master services agreement signed via a normal e-signature platform is enforceable everywhere that matters. Pick a choice of law clause (your home country is fine for low-value work) and stop worrying.

Distributors and resellers. This is where it gets dicier. Distribution agreements often include exclusive territories, IP licensing, and termination rights that are heavily regulated in some countries. Some jurisdictions require certain distributor protections that override your choice of law clause. Get local advice before signing.

NDAs with overseas vendors. NDAs are usually low-stakes enough that a basic e-signature works fine. But remember: enforcing an NDA against someone in another country is hard regardless of how it's signed. Your real protection is who you trust, not the signature tier.

The SES/AES/QES decision for cross-EU work

If you're working with EU counterparties, here's the practical playbook:

• Standard B2B contracts (services, supply, NDAs): SES is fine. AES is better.
• Real estate, employment, anything needing "written form" under local law: Use QES. Always.
• Consumer contracts in regulated areas (financial, insurance): Check the specific country's rules — often QES is required.
• You're not sure: Use AES. It's the safest middle ground and most platforms support it without much extra friction.

The German B2B trap: even when both parties are corporations and one is non-EU, certain documents under German law still want QES. Cross-border doesn't get you out of it.

For more on the difference between digital signatures (the cryptographic kind) and electronic signatures broadly, see digital signature vs electronic signature.

Common pitfalls (the greatest hits)

After years of watching SMBs trip over this stuff, here are the mistakes I see again and again:

1. Assuming US ESIGN works everywhere. It doesn't. Germany, France, Brazil, and India will all give you headaches if you use a basic SES for the wrong document type.
2. Ignoring local language requirements. Some countries require contracts to be in the local language to be enforceable against local consumers, or require a translation appendix.
3. Skipping the apostille on notarized docs. I've seen six-figure deals stall for two weeks because the apostille step got forgotten.
4. Using the wrong tier for the document. Just because your platform offers QES doesn't mean you have to use it for everything — but for the documents that need it, SES isn't a substitute.
5. Treating choice of law and venue as boilerplate. It's not. It determines which court hears your dispute and which laws apply.
6. Not keeping the audit trail. If you ever need to prove a contract is real, the audit trail (IP address, timestamps, signer identity, document hash) is your evidence. Don't lose it.

What this means in practice

Here's the short version. For most international deals SMBs sign every day:

• Use a real e-signature platform that produces a complete audit trail
• Choose a sensible governing law and venue and put it in writing
• Pick a binding language explicitly if the contract is bilingual
• Use AES or QES if any part of the deal touches a regulated jurisdiction or document type
• Plan for apostilles when notarization is involved
• Keep your records — for years, not weeks

And for anything where a mistake would really hurt: get a lawyer involved. The cost of an hour of advice up front is always cheaper than the cost of an unenforceable contract.

If you want a tool that handles SES and AES out of the box, with proper audit trails and tier flexibility for international work, give CanUSign a try. We built it specifically because the existing options were either too expensive (DocuSign) or too thin (basic free tools) for SMBs that need real cross-border enforceability without paying enterprise prices.

Last thing — and I'll say it again because it matters: this is general information, not legal advice. Your situation is yours. Talk to a lawyer for the deals that count.