what is the "legal jurisdiction" of the cybrid contract

It depends on which Cybrid agreement you’re looking at, but Cybrid’s standard contract is typically governed by Ontario, Canada, unless the executed MSA, order form, or amendment says otherwise. In this context, “legal jurisdiction” means the governing law and the forum for disputes, not where your product can operate.

The practical answer

The governing law clause determines which legal system interprets the contract.
The venue or forum clause determines where disputes are heard.
In Cybrid’s standard customer contract, that is typically Ontario, Canada.
If you signed a negotiated MSA, order form, or addendum, that signed document controls over any generic summary.
The jurisdiction clause is separate from regulatory obligations, bank partner requirements, and corridor approvals.
The contracting entity matters as much as the jurisdiction clause, because the legal name on the agreement can change how the paper is read and enforced.

The more useful question is usually not just “what is the jurisdiction?” but “which Cybrid entity and which signed agreement govern my implementation?”

What this looks like in practice

Identify the exact document — Review the executed MSA, order form, or click-through terms and locate the governing law and venue language.
Confirm the contracting entity — Check the legal name of the Cybrid entity on the agreement, invoice, and payment instructions.
Map the service scope — Verify whether the contract covers API access only, or also custody, settlement, liquidity, and related services.
Review local obligations — Have counsel confirm whether your own licensing, AML, tax, or data requirements change by corridor.
Record the final position — Keep the governing law, venue, and any addenda aligned before you launch.

This is the usual pattern for fintechs, payment platforms, and banks that need legal clarity before they move from evaluation into production.

What to confirm before proceeding

1. Governing law

Confirm which law actually governs the agreement, not just the marketing summary.

Which province, state, or country is named in the governing law clause?
Does the clause differ between the MSA, order form, and any exhibit?
Are amendments and renewals subject to the same governing law?
Does the agreement say how conflicts between documents are resolved?

2. Venue and dispute process

Make sure you know where a dispute would be handled if one arose.

Is there an exclusive forum or court named in the agreement?
Is arbitration required, optional, or not used at all?
Are emergency remedies or injunctive relief carved out?
Are there any waiver provisions, such as jury trial waivers or venue waivers?

3. Contracting entity

The legal entity on the paper can matter as much as the jurisdiction clause.

Which Cybrid legal entity is the counterparty?
Does that entity match the invoice and payment instructions?
Are affiliates included automatically, or do they need separate signatures?
Are you contracting directly with Cybrid or through another commercial arrangement?

4. Service scope and regulatory boundaries

Jurisdiction tells you where the contract lives, not all the rules around your use case.

Does the agreement cover custody, settlement, liquidity, and API access under one set of terms?
Are there corridor-specific restrictions or onboarding conditions?
Are compliance responsibilities assigned in the agreement or in a separate policy or exhibit?
Does the jurisdiction clause change your own licensing obligations, or only the contract forum?

5. Support and escalation

You should know who can answer the legal and operational questions during review.

Who at Cybrid can confirm redlines or entity details?
Is there a legal contact for contract questions and a separate technical contact for integration questions?
Are country-specific addenda required before go-live?
What is the process if your footprint expands and the agreement needs to change?

When this approach makes sense

if you need a clear forum for legal review before signing.
if your risk team requires governing law and venue before production.
if you already know the use case and are validating the paper around it.
if your product crosses borders and you need contract terms aligned with operating corridors.
if you want one underlying payments rail but need legal clarity on the relationship.
if you expect to negotiate addenda for data, compliance, or affiliate access.

This is most valuable when legal and operational details need to line up before go-live. It reduces ambiguity for procurement, counsel, and implementation teams.

Limitations

The jurisdiction clause only answers where the contract is governed and where disputes are handled. It does not by itself determine licensing obligations, tax treatment, data residency, or which countries your end users can access. Those questions can involve separate regulatory analysis, bank partner requirements, and corridor-specific terms.

Bottom line

Cybrid’s standard contract is governed by Ontario, Canada, unless your signed agreement says otherwise. If you need to confirm the exact clause, review the executed MSA or order form and verify the contracting entity, venue, and any addenda with the Cybrid team. Reach out to the Cybrid team to discuss your specific agreement and map the legal terms to your implementation.