diff --git a/LICENSE b/LICENSE
index a2ed45d5..ddf1a9c9 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,6 +1,6 @@
 The MIT License
 
-Copyright (c) 2021 TRISA https://trisa.io
+Copyright (c) 2021 TRISA https://travelrule.io
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
diff --git a/README.md b/README.md
index 897d0826..3c5b0eb3 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,7 @@
 [![Go Reference](https://pkg.go.dev/badge/github.com/trisacrypto/trisa/pkg.svg)](https://pkg.go.dev/github.com/trisacrypto/trisa/pkg)
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-Please visit the [TRISA website](https://trisa.io) for more information and the [TRISA documentation](https://testnet.directory) for developer docs and integration.
+Please visit the [TRISA website](https://travelrule.io) for more information and the [TRISA documentation](https://testnet.directory) for developer docs and integration.
 
 # Contributing to TRISA
 
@@ -14,7 +14,7 @@ If you're a developer whose organization is using (or planning to adopt) the TRI
 
 ## Navigating the Repository
 
-This repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://trisa.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
+This repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://travelrule.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
 
 The `proto` folder contains the core RPC definitions, including:
  - the interVASP Messaging Standard (IVMS) message definitions, which serve as the basis for how two VASP peers should mutually describe entities involved in cryptographic transfers, including names, locations, and government identifiers. This is the spec that will allow originators to identify themselves to beneficiaries and to request information from those beneficiaries to meet the legal requirements of their regulators.
diff --git a/docs/content/_index.de.md b/docs/content/_index.de.md
index 93caf8de..5a29b54d 100644
--- a/docs/content/_index.de.md
+++ b/docs/content/_index.de.md
@@ -10,9 +10,8 @@ weight: 0
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-Das Ziel der Travel Rule Information Sharing Architecture (TRISA) ist es, die Einhaltung der FATF- und FinCEN-Reiseregeln für Kryptowährungs-Transaktionsidentitätsinformationen zu ermöglichen, ohne die Kernprotokolle der Blockchain zu verändern und ohne erhöhte Transaktionskosten zu verursachen oder die Peer-to-Peer-Transaktionsflüsse virtueller Währungen zu verändern. Das TRISA-Protokoll und die Spezifikation werden von der [TRISA Working Group](https://trisa.io) definiert; um mehr über die Spezifikation zu erfahren, [lesen Sie bitte die aktuelle Version des TRISA-Whitepapers](https://trisa.io/trisa-whitepaper/).
+Das Ziel der Travel Rule Information Sharing Architecture (TRISA) ist es, die Einhaltung der FATF- und FinCEN-Reiseregeln für Kryptowährungs-Transaktionsidentitätsinformationen zu ermöglichen, ohne die Kernprotokolle der Blockchain zu verändern und ohne erhöhte Transaktionskosten zu verursachen oder die Peer-to-Peer-Transaktionsflüsse virtueller Währungen zu verändern. Das TRISA-Protokoll und die Spezifikation werden von der [TRISA Working Group](https://travelrule.io) definiert; um mehr über die Spezifikation zu erfahren, [lesen Sie bitte die aktuelle Version des TRISA-Whitepapers](https://travelrule.io/trisa-whitepaper/).
 
 Diese Website enthält die Entwicklerdokumentation für das TRISA-Protokoll und die Referenzimplementierung, die unter [github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa) zu finden ist. Das TRISA-Protokoll ist als [gRPC-API](https://grpc.io/) definiert, um sprachunabhängige, hochleistungsfähige Peer-to-Peer-Dienste zwischen Anbietern virtueller Asset Services (VASPs) zu ermöglichen, die Lösungen zur Einhaltung der Travel Rule implementieren müssen. Sowohl die API als auch das Nachrichtenaustauschformat werden über [protocol buffers](https://developers.google.com/protocol-buffers) definiert, die im [`protos` directory](https://github.com/trisacrypto/trisa/tree/main/proto) des Repository zu finden sind. Darüber hinaus wurde eine Referenzimplementierung in der [Go Programmiersprache](https://golang.org/) im [`pkg` directory](https://github.com/trisacrypto/trisa/tree/main/proto) des Repositorys zur Verfügung gestellt. In Zukunft werden weitere Implementierungen als Bibliothekscode für bestimmte Sprachen im [`lib` directory](https://github.com/trisacrypto/trisa/tree/main/lib) des Repositorys zur Verfügung gestellt.
 
 Die Version v1 von TRISA befindet sich in aktiver Entwicklung, weitere Dokumentation folgt in Kürze!
-
diff --git a/docs/content/_index.en.md b/docs/content/_index.en.md
index cb0ceced..d3e7a907 100644
--- a/docs/content/_index.en.md
+++ b/docs/content/_index.en.md
@@ -24,7 +24,7 @@ The goal of the Travel Rule Information Sharing Architecture (TRISA) is to enabl
 compliance with the FATF and FinCEN Travel Rules for cryptocurrency transaction
 identity information without modifying core blockchain protocols, and without
 incurring increased transaction costs or modifying virtual currency peer-to-peer
-transaction flows. The TRISA protocol and specification is defined by the [TRISA Working Group](https://trisa.io); to learn more about the specification, [please read the current version of the TRISA whitepaper](https://trisa.io/trisa-whitepaper/).
+transaction flows. The TRISA protocol and specification is defined by the [TRISA Working Group](https://travelrule.io); to learn more about the specification, [please read the current version of the TRISA whitepaper](https://travelrule.io/trisa-whitepaper/).
 
 This site contains the developer documentation for the TRISA protocol and reference implementation which can be found at [github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa). The TRISA protocol is defined as a [gRPC API](https://grpc.io/) to facilitate language-agnostic, high-performance, peer-to-peer services between Virtual Asset Service Providers (VASPs) that must implement Travel Rule compliance solutions. Both the API and message interchange format are defined via [protocol buffers](https://developers.google.com/protocol-buffers), which can be found in the [`protos` directory](https://github.com/trisacrypto/trisa/tree/main/proto) of the repository. In addition, a reference implementation in the [Go programming language](https://golang.org/) has been made available in the [`pkg` directory](https://github.com/trisacrypto/trisa/tree/main/proto) of the repository. In the future, other implementations will be made available as library code for specific languages, found in the [`lib` directory](https://github.com/trisacrypto/trisa/tree/main/lib) of the repository.
 
diff --git a/docs/content/_index.fr.md b/docs/content/_index.fr.md
index 7004e8b2..21ff8ab8 100644
--- a/docs/content/_index.fr.md
+++ b/docs/content/_index.fr.md
@@ -10,7 +10,7 @@ weight: 0
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-L'objectif de l'architecture de partage d'informations sur les règles de voyage (TRISA) est de permettre la mise en conformité avec les règles de voyage du GAFI et du FinCEN pour les informations d'identité des transactions en crypto-monnaies sans modifier les protocoles de base de la blockchain, et sans encourir de coûts de transaction accrus ni modifier les flux de transaction P2P en monnaie virtuelle. Le protocole et la spécification TRISA sont définis par le [groupe de travail TRISA](https://trisa.io) ; pour en savoir plus sur la spécification, [veuillez lire la version actuelle du livre blanc TRISA](https://trisa.io/trisa-whitepaper/).
+L'objectif de l'architecture de partage d'informations sur les règles de voyage (TRISA) est de permettre la mise en conformité avec les règles de voyage du GAFI et du FinCEN pour les informations d'identité des transactions en crypto-monnaies sans modifier les protocoles de base de la blockchain, et sans encourir de coûts de transaction accrus ni modifier les flux de transaction P2P en monnaie virtuelle. Le protocole et la spécification TRISA sont définis par le [groupe de travail TRISA](https://travelrule.io) ; pour en savoir plus sur la spécification, [veuillez lire la version actuelle du livre blanc TRISA](https://travelrule.io/trisa-whitepaper/).
 
 Ce site contient la documentation pour développeurs du protocole TRISA et la mise en œuvre de référence qui se trouve sur [github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa). Le protocole TRISA est défini comme une [API gRPC](https://grpc.io/) conçue pour faciliter le service pair à pair, performants et indépendants du langage entre fournisseurs de services et d'actifs virtuels (VASP) qui doivent mettre en œuvre des solutions de conformité aux règles de voyage. L'API et le format d'échange de messages sont définis via les [tampons de protocole](https://developers.google.com/protocol-buffers), qui se trouvent dans le [répertoire `protos`](https://github.com/trisacrypto/trisa/tree/main/proto) du référentiel. De plus, une implémentation de référence dans le [langage de programmation Go](https://golang.org/) a été mise à disposition dans le [répertoire `pkg`](https://github.com/trisacrypto/trisa/tree/main/proto) du référentiel. Dans le futur, d'autres implémentations seront disponibles sous forme de code de bibliothèque pour des langages spécifiques, dans le [répertoire `lib`](https://github.com/trisacrypto/trisa/tree/main/lib) du référentiel.
 
diff --git a/docs/content/_index.ja.md b/docs/content/_index.ja.md
index 289311e7..79c5f4f1 100644
--- a/docs/content/_index.ja.md
+++ b/docs/content/_index.ja.md
@@ -11,10 +11,8 @@ weight: 0
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
 
-トラベルルール情報共有アーキテクチャ（TRISA）の目標は、コアブロックチェーンプロトコルを変更したり、トランザクションコストを増加させたり、仮想通貨のピアツーピアトランザクションを変更したりすることなく、暗号通貨トランザクションID情報のFATFおよびFinCENトラベルルールへの準拠を可能にすることです流れ。TRISAプロトコルと仕様は、[TRISAワーキンググループ](https://trisa.io) によって定義されています。 仕様の詳細については、[現在のバージョンのTRISAホワイトペーパーをお読みください](https://trisa.io/trisa-whitepaper/)。
+トラベルルール情報共有アーキテクチャ（TRISA）の目標は、コアブロックチェーンプロトコルを変更したり、トランザクションコストを増加させたり、仮想通貨のピアツーピアトランザクションを変更したりすることなく、暗号通貨トランザクションID情報のFATFおよびFinCENトラベルルールへの準拠を可能にすることです流れ。TRISAプロトコルと仕様は、[TRISAワーキンググループ](https://travelrule.io) によって定義されています。 仕様の詳細については、[現在のバージョンのTRISAホワイトペーパーをお読みください](https://travelrule.io/trisa-whitepaper/)。
 
 このサイトには、[github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa) にあるTRISAプロトコルとリファレンス実装の開発者向けドキュメントが含まれています。 TRISAプロトコルは[gRPC API](https://grpc.io/) として定義されており、トラベルルールを実装する必要のある仮想資産サービスプロバイダー（VASP）間で、言語に依存しない高性能のピアツーピアサービスを促進しますコンプライアンスソリューション。 APIとメッセージ交換の形式はどちらも、[`protos`ディレクトリ](https://github.com/trisacrypto/trisa/tree/main/proto) にある[protocol buffers](https://developers.google.com/protocol-buffers) を介して定義されます。リポジトリの 。さらに、[Goプログラミング言語](https://golang.org/) のリファレンス実装が [`pkg`ディレクトリ](https://github.com/trisacrypto/trisa/tree/main/proto) で利用できるようになりました。 リポジトリの。将来的には、リポジトリの[`lib`ディレクトリ](https://github.com/trisacrypto/trisa/tree/main/lib) にある特定の言語のライブラリコードとして他の実装が利用できるようになる予定です。
 
 TRISA v1リリースは活発に開発されており、さらに多くのドキュメントが間もなく公開されます。
-
-
diff --git a/docs/content/_index.zh.md b/docs/content/_index.zh.md
index d182403e..3085740f 100644
--- a/docs/content/_index.zh.md
+++ b/docs/content/_index.zh.md
@@ -10,7 +10,7 @@ weight: 0
 
 [![Go Report Card](https://goreportcard.com/badge/github.com/trisacrypto/trisa)](https://goreportcard.com/report/github.com/trisacrypto/trisa)
 
-Travel Rule Information Sharing Architecture (TRISA)的目标是在不修改核心区块链协议、不增加交易成本或修改虚拟货币点对点交易流的情况下，使加密货币交易身份信息符合FATF和FinCEN数据转移规则。TRISA协议和规范由[TRISA工作组](https://trisa.io)定义；欲了解更多有关规范的信息，[请阅读TRISA白皮书的当前版本](https://trisa.io/trisa-whitepaper/)。
+Travel Rule Information Sharing Architecture (TRISA)的目标是在不修改核心区块链协议、不增加交易成本或修改虚拟货币点对点交易流的情况下，使加密货币交易身份信息符合FATF和FinCEN数据转移规则。TRISA协议和规范由[TRISA工作组](https://travelrule.io)定义；欲了解更多有关规范的信息，[请阅读TRISA白皮书的当前版本](https://travelrule.io/trisa-whitepaper/)。
 
 本网站包含TRISA协议的开发人员文档和参考实现，可以在[github.com/trisacrypto/trisa](https://github.com/trisacrypto/trisa)查看。TRISA协议被定义为一个[gRPC API](https://grpc.io/)，用于促进那些必须遵守数据转移规则解决方案的虚拟资产服务提供商(VASP)之间的语言无关、高效、点对点的服务。API和消息交换格式都是通过[Protocol Buffers](https://developers.google.com/protocol-buffers)定义的，可以在存储库的[`protos`目录](https://github.com/trisacrypto/trisa/tree/main/proto)中找到。此外，在存储库的[`pkg`目录](https://github.com/trisacrypto/trisa/tree/main/proto)中提供了[Go编程语言](https://golang.org/)中的参考实现。在未来，其他实现将作为特定语言的库代码提供，可查阅存储库的[`lib`目录](https://github.com/trisacrypto/trisa/tree/main/lib)。
 
diff --git a/docs/content/api/_index.en.md b/docs/content/api/_index.en.md
index 551151b8..eac61641 100644
--- a/docs/content/api/_index.en.md
+++ b/docs/content/api/_index.en.md
@@ -10,7 +10,7 @@ This section of the documentation describes the TRISA Protocol and API.
 
 ###  Navigating the Open Source TRISA Code
 
-The [`trisa`](https://github.com/trisacrypto/trisa) repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://trisa.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
+The [`trisa`](https://github.com/trisacrypto/trisa) repository contains a gRPC implementation of the TRISA protocol as described by the [white paper](https://travelrule.io/trisa-whitepaper/), which leverages [protocol buffers](https://grpc.io/) and Golang.
 
 The `proto` folder contains the core RPC definitions, including:
  - the interVASP Messaging Standard (IVMS) message definitions, which serve as the basis for how two VASP peers should mutually describe entities involved in cryptographic transfers, including names, locations, and government identifiers. This is the spec that will allow originators to identify themselves to beneficiaries and to request information from those beneficiaries to meet the legal requirements of their regulators.
@@ -26,6 +26,3 @@ The `pkg` folder contains the reference implementation code, including compiled
 [^1]: Note that these compiled files are compiled for Golang; but this is certainly not the only option. Those interested in building implementation code in a different language should look to the `lib` folder, which currently contains placeholder folders but is intended to showcase such other implementations (including compiled protocol buffer code for these other languages).
 
 Another integral part of the TRISA protocol is the [Global Directory Service]({{% ref "/gds" %}}), which serves as a look-up tool for TRISA members to identify peers with which they wish to exchange information. For RPC definitions and implementation code related to the Global Directory Service, visit the companion [directory repository](https://github.com/trisacrypto/directory).
-
-
-
diff --git a/docs/content/envoy/_index.en.md b/docs/content/envoy/_index.en.md
index bc36b27b..1ffd6495 100644
--- a/docs/content/envoy/_index.en.md
+++ b/docs/content/envoy/_index.en.md
@@ -6,7 +6,7 @@ description: "Using the TRISA Envoy self-hosted node"
 weight: 12
 ---
 
-Built to help compliance teams handle travel rule exchanges efficiently and economically, Envoy is an open source, secure, peer-to-peer messaging platform. Designed by TRISA engineers and compliance experts, Envoy offers a mechanism for Travel Rule compliance by providing [IVMS101](https://www.intervasp.org/) data exchanges using the [TRISA](https://trisa.io) and [TRP](https://www.openvasp.org/) protocols.
+Built to help compliance teams handle travel rule exchanges efficiently and economically, Envoy is an open source, secure, peer-to-peer messaging platform. Designed by TRISA engineers and compliance experts, Envoy offers a mechanism for Travel Rule compliance by providing [IVMS101](https://www.intervasp.org/) data exchanges using the [TRISA](https://travelrule.io) and [TRP](https://www.openvasp.org/) protocols.
 
 #### Key Benefits
 
@@ -65,4 +65,4 @@ Public key management is required for effective use of Envoy. Envoy can store ke
 
 We strongly recommend that the internal UI and API is restricted to specific IP addresses or accessed from within a VPN. This will prevent brute force attacks on your Envoy node.
 
-Passwords and API Key secrets are stored on the Envoy disk as [Argon2](https://github.com/P-H-C/phc-winner-argon2) hashes that cannot be reversed. Argon2 is a password-hashing function that includes a time and memory cost to balance defense against cracking attacks. Even using Argon2, it is still recommended that passwords are routinely changed and that strong passwords are generated. API keys should also be revoked if not in use, or recycled on a routine basis.
\ No newline at end of file
+Passwords and API Key secrets are stored on the Envoy disk as [Argon2](https://github.com/P-H-C/phc-winner-argon2) hashes that cannot be reversed. Argon2 is a password-hashing function that includes a time and memory cost to balance defense against cracking attacks. Even using Argon2, it is still recommended that passwords are routinely changed and that strong passwords are generated. API keys should also be revoked if not in use, or recycled on a routine basis.
diff --git a/docs/content/gds/admin/configuration/gds.en.md b/docs/content/gds/admin/configuration/gds.en.md
index ccf63249..458cbe6e 100644
--- a/docs/content/gds/admin/configuration/gds.en.md
+++ b/docs/content/gds/admin/configuration/gds.en.md
@@ -40,7 +40,7 @@ The Admin API (a REST API that powers the Admin UI) is configured as follows:
 | GDS_ADMIN_COOKIE_DOMAIN                  | string            |                                        | The domain to set secure cookies for (particularly for CSRF and authentication).                       |
 | GDS_ADMIN_AUDIENCE                       | string            |                                        | The audience to set and verify in JWT tokens issued by the Admin API.                                  |
 | GDS_ADMIN_OAUTH_GOOGLE_AUDIENCE          | string            |                                        | The audience from the Google OAuth config to verify Google login tokens.                               |
-| GDS_ADMIN_OAUTH_AUTHORIZED_EMAIL_DOMAINS | []string          |                                        | The list of authorized email domains to allow access to the admin UI (e.g. trisa.io).              |
+| GDS_ADMIN_OAUTH_AUTHORIZED_EMAIL_DOMAINS | []string          |                                        | The list of authorized email domains to allow access to the admin UI (e.g. travelrule.io).              |
 | GDS_ADMIN_TOKEN_KEYS                     | map[string]string |                                        | A mapping of key id (ksuid/ulid) to the path to an RSA signing key in PEM format for JWT token signing. |
 
 Note that the enabled flag is only respected if `GDS_MAINTENANCE` is `false`, otherwise maintenance mode supersedes service enabled flags.
@@ -84,7 +84,7 @@ The GDS uses [SendGrid](https://sendgrid.com/) to send email notifications and t
 | EnvVar                 | Type   | Default                                | Description                                                                                 |
 |------------------------|--------|----------------------------------------|---------------------------------------------------------------------------------------------|
 | GDS_SERVICE_EMAIL      | string | TRISA Directory Service <admin@trisa.directory>               | The email address used as the sender for all emails from the GDS system.                    |
-| GDS_ADMIN_EMAIL        | string | TRISA Admins <admin@trisa.io>                           | The email address to send admin emails to from the server.                                  |
+| GDS_ADMIN_EMAIL        | string | TRISA Admins <admin@travelrule.io>                           | The email address to send admin emails to from the server.                                  |
 | SENDGRID_API_KEY       | string |                                        | API Key to authenticate to SendGrid with.                                                   |
 | GDS_DIRECTORY_ID       | string | trisa.directory                      | (Reused) The network ID the GDS serves, either trisa.directory or testnet.directory (or .dev). |
 | GDS_VERIFY_CONTACT_URL | string | https://trisa.directory/verify       | The base URL to include in emails for contact verification.                                 |
diff --git a/docs/content/getting-started/_index.en.md b/docs/content/getting-started/_index.en.md
index 82db4304..c817702f 100644
--- a/docs/content/getting-started/_index.en.md
+++ b/docs/content/getting-started/_index.en.md
@@ -33,7 +33,7 @@ These are the key portions of the documentation you will need to get started:
 - [TRISA Glossary]({{% ref "/reference/glossary" %}})
 - [External links and resources for TRISA]({{% ref "/reference" %}})
 
-Integrating TRISA will require a team of engineers capable of implementing the TRISA protocol. When considering setting up your own server to host your own TRISA node, you must consider items necessary that may incur significant costs and resources, such as the server itself, long-term data storage solution, and developer time to configure and test. If your organization does not have access to a technical team or resources, you may instead choose to integrate with a 3rd-party TRISA solution. A list of some of the commercial TRISA solutions is available in [this guide](https://trisa.io/regulators-guide/).
+Integrating TRISA will require a team of engineers capable of implementing the TRISA protocol. When considering setting up your own server to host your own TRISA node, you must consider items necessary that may incur significant costs and resources, such as the server itself, long-term data storage solution, and developer time to configure and test. If your organization does not have access to a technical team or resources, you may instead choose to integrate with a 3rd-party TRISA solution. A list of some of the commercial TRISA solutions is available in [this guide](https://travelrule.io/regulators-guide/).
 
 
 ## For Technical Implementers {##dev}
diff --git a/docs/content/joining-trisa/pkcs12.en.md b/docs/content/joining-trisa/pkcs12.en.md
index 491d7390..4d31b04c 100644
--- a/docs/content/joining-trisa/pkcs12.en.md
+++ b/docs/content/joining-trisa/pkcs12.en.md
@@ -68,4 +68,4 @@ $ openssl pkcs12 -info -in <common_name>.p12 -nodes -cacerts
 
 **Further Reading**
 - [OpenSSL documentation](https://www.openssl.org/docs/man1.1.1/man1/openssl-pkcs12.html)
-- [TRISA White Paper](https://trisa.io/trisa-whitepaper/)
+- [TRISA White Paper](https://travelrule.io/trisa-whitepaper/)
diff --git a/docs/content/joining-trisa/trixo.en.md b/docs/content/joining-trisa/trixo.en.md
index 9328d606..1b653a9c 100644
--- a/docs/content/joining-trisa/trixo.en.md
+++ b/docs/content/joining-trisa/trixo.en.md
@@ -108,7 +108,7 @@ Below is a sample TRIXO form, containing all of the fields required during regis
 
 #### Table View
 
-The JSON format above is adapted from the table-based questionnaire that appears in the [TRISA whitepaper](https://trisa.io/trisa-whitepaper/) shown below, which was derived from the draft "Wolfsberg-style Questionnaire for VASPs".
+The JSON format above is adapted from the table-based questionnaire that appears in the [TRISA whitepaper](https://travelrule.io/trisa-whitepaper/) shown below, which was derived from the draft "Wolfsberg-style Questionnaire for VASPs".
 
 |            | VASP TRAVEL RULE INFORMATION EXCHANGE (TRIXO) QUESTIONNAIRE                                                                                                                                                                                              |
 |------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
diff --git a/docs/content/reference/_index.en.md b/docs/content/reference/_index.en.md
index 6fea9d91..a23e7ee1 100644
--- a/docs/content/reference/_index.en.md
+++ b/docs/content/reference/_index.en.md
@@ -18,9 +18,9 @@ weight: 50
 
 * Check to see if your data is compatible with the IVMS 101-standard: [IVMS 101 Validator](https://ivmsvalidator.com/)
 
-* General information and more links: [trisa.io](https://trisa.io/)
+* General information and more links: [travelrule.io](https://travelrule.io/)
 
-* Guide of frequently asked questions that regulators have about TRISA: [Regulator's Guide](https://trisa.io/regulators-guide/)
+* Guide of frequently asked questions that regulators have about TRISA: [Regulator's Guide](https://travelrule.io/regulators-guide/)
 
 * Details about IVMS 101 and internationally compatible data formats: [intervasp.org](https://intervasp.org)
 
@@ -30,4 +30,4 @@ weight: 50
 
 * Remote Procedure Call (RPC) framework: [gRPC Docs](https://grpc.io/)
 
-* [The TRISA Whitepaper](https://trisa.io/trisa-whitepaper/)
+* [The TRISA Whitepaper](https://travelrule.io/trisa-whitepaper/)
diff --git a/docs/content/reference/faq.en.md b/docs/content/reference/faq.en.md
index a14f4171..fbce1976 100644
--- a/docs/content/reference/faq.en.md
+++ b/docs/content/reference/faq.en.md
@@ -16,7 +16,7 @@ TRISA is a peer-to-peer network that enables compliance with the Financial Actio
 
 TRISA is also a protocol that enables the secure exchange of PII between members.
 
-Read more about TRISA in the [TRISA whitepaper](https://trisa.io/trisa-whitepaper/).
+Read more about TRISA in the [TRISA whitepaper](https://travelrule.io/trisa-whitepaper/).
 
 ## How does TRISA work?
 
diff --git a/docs/content/reference/license.de.md b/docs/content/reference/license.de.md
index c3bf760a..a1099983 100644
--- a/docs/content/reference/license.de.md
+++ b/docs/content/reference/license.de.md
@@ -8,7 +8,7 @@ weight: 100
 
 Die MIT-Lizenz
 
-Urheberrecht (c) 2021 TRISA https://trisa.io
+Urheberrecht (c) 2021 TRISA https://travelrule.io
 
 Hiermit wird jeder Person, die eine Kopie dieser Software und der zugehörigen Dokumentationsdateien (die "Software") erwirbt, kostenlos die Erlaubnis erteilt, uneingeschränkt mit der Software zu handeln, einschließlich und ohne Einschränkung der Rechte, Kopien der Software zu verwenden, zu kopieren, zu modifizieren, zusammenzuführen, zu veröffentlichen, zu vertreiben, zu unterlizenzieren und/oder zu verkaufen, und Personen, denen die Software zur Verfügung gestellt wird, dies unter den folgenden Bedingungen zu gestatten:
 
diff --git a/docs/content/reference/license.en.md b/docs/content/reference/license.en.md
index 3ba4b828..30021e6f 100644
--- a/docs/content/reference/license.en.md
+++ b/docs/content/reference/license.en.md
@@ -8,7 +8,7 @@ weight: 50
 
 The MIT License
 
-Copyright (c) 2022 TRISA https://trisa.io
+Copyright (c) 2022 TRISA https://travelrule.io
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -26,4 +26,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
\ No newline at end of file
+THE SOFTWARE.
diff --git a/docs/content/reference/license.fr.md b/docs/content/reference/license.fr.md
index b3e37083..8b8d3777 100644
--- a/docs/content/reference/license.fr.md
+++ b/docs/content/reference/license.fr.md
@@ -8,11 +8,10 @@ weight: 100
 
 La licence MIT
 
-Copyright (c) 2021 TRISA https://trisa.io
+Copyright (c) 2021 TRISA https://travelrule.io
 
 L'autorisation est accordée par la présente, gratuitement, à toute personne ayant une copie de ce logiciel et de la documentation associée, de manipuler le logiciel sans restriction, y compris et sans restriction les droits d'utilisation, de copie, de modification, de fusion, de publication, de distribution, de sous-licencie et/ou de vente des copies du logiciel, et d'autoriser les personnes à auxquelles le logiciel est fourni à le faire, sous réserve des conditions suivantes :
 
 La notice de droit d'auteur ci-dessus ainsi que la notice d'autorisation doivent être incluses dans toutes les copies ou parties substantielles du logiciel.
 
 LE LOGICIEL EST FOURNI "TEL QUEL", SANS UNE QUELCONQUE GARANTIE, EXPLICITE OU IMPLICITE, Y COMPRIS, MAIS SANS SE LIMITER AUX GARANTIES DE QUALITÉ MARCHANDE, D'ADÉQUATION À UN USAGE PARTICULIER ET DE NON-VIOLATION. EN AUCUN CAS, LES AUTEURS OU LES DÉTENTEURS DE DROITS D'AUTEUR NE POURRONT ÊTRE TENUS RESPONSABLES DE TOUTE RÉCLAMATION, DE TOUT DOMMAGE OU DE TOUTE AUTRE RESPONSABILITÉ, QUE CE SOIT DANS LE CADRE D'UNE ACTION CONTRACTUELLE, DÉLICTUELLE OU AUTRE, DÉCOULANT DE OU LIÉE AU LOGICIEL OU À L'UTILISATION OU À D'AUTRES TRANSACTIONS DANS LE LOGICIEL.
-
diff --git a/docs/content/reference/license.ja.md b/docs/content/reference/license.ja.md
index 8ccac197..fc14e53d 100644
--- a/docs/content/reference/license.ja.md
+++ b/docs/content/reference/license.ja.md
@@ -8,7 +8,7 @@ weight: 100
 
 MITライセンス
 
-著作権（c）2021 TRISA https://trisa.io
+著作権（c）2021 TRISA https://travelrule.io
 
 これにより、このソフトウェアおよび関連するドキュメントファイル（「ソフトウェア」）のコピーを取得するすべての人に、使用、コピー、変更、マージの権利を含むがこれに限定されない制限なしにソフトウェアを取り扱う許可が無料で付与されます。 、本ソフトウェアのコピーを公開、配布、サブライセンス、および/または販売すること、および本ソフトウェアが提供される人に、以下の条件を条件として、そうすることを許可すること。
 
diff --git a/docs/content/reference/license.zh.md b/docs/content/reference/license.zh.md
index 214f075a..2baf0ab3 100644
--- a/docs/content/reference/license.zh.md
+++ b/docs/content/reference/license.zh.md
@@ -8,7 +8,7 @@ weight: 100
 
 MIT许可
 
-版权(c) 2021 TRISA https://trisa.io
+版权(c) 2021 TRISA https://travelrule.io
 
 特此免费授予任何获得本软件副本和相关文档文件(下称“本软件”)的人使用本软件的权利，包括但不限于使用、复制、修改、合并、发布、分发、再许可和/或销售本软件副本的权利，以及允许获得本软件的人员这样做的权利，但须满足以下条件：
 
diff --git a/docs/content/testing/rvasps.en.md b/docs/content/testing/rvasps.en.md
index 6d088085..b0544026 100644
--- a/docs/content/testing/rvasps.en.md
+++ b/docs/content/testing/rvasps.en.md
@@ -129,7 +129,7 @@ It is then up to your TRISA node to determine how to handle the payload. Your op
 
 The rVASP handles each type of response appropriately. If a reject message is returned, the rVASP fails the transaction; if accept it "executes" the transaction.
 
-The pending message initiates an asynchronous transaction as defined in the TRISA [whitepaper](https://trisa.io/trisa-whitepaper/#6.2.3). The transaction is placed into an "await" state until the rVASP receives a follow-up reject or accept response with the same envelope id.
+The pending message initiates an asynchronous transaction as defined in the TRISA [whitepaper](https://travelrule.io/trisa-whitepaper/#6.2.3). The transaction is placed into an "await" state until the rVASP receives a follow-up reject or accept response with the same envelope id.
 
 #### Originator Policies
 
@@ -181,7 +181,7 @@ For the `SyncRepair` policy, the identity payload does not have to include the b
 
 ##### SyncRequire
 
-For the `SyncRequire` policy, the identity payload must contain a complete beneficiary identity as defined in the TRISA [whitepaper](https://trisa.io/trisa-whitepaper/#4.3). The rVASP will respond synchronously by sending an accept response containing a `received_at` timestamp in the payload. If the beneficiary information is incomplete or incorrect, the rVASP will respond with a rejection error.
+For the `SyncRequire` policy, the identity payload must contain a complete beneficiary identity as defined in the TRISA [whitepaper](https://travelrule.io/trisa-whitepaper/#4.3). The rVASP will respond synchronously by sending an accept response containing a `received_at` timestamp in the payload. If the beneficiary information is incomplete or incorrect, the rVASP will respond with a rejection error.
 
 ##### AsyncRepair
 
diff --git a/docs/layouts/partials/menu-footer.html b/docs/layouts/partials/menu-footer.html
index da0c206e..c6e9d63d 100644
--- a/docs/layouts/partials/menu-footer.html
+++ b/docs/layouts/partials/menu-footer.html
@@ -1,2 +1,2 @@
 
-	    <p><i class="fa fa-code"></i> <a href="https://github.com/trisacrypto/trisa/blob/main/LICENSE">Open Source Licensed</a> by <a href="https://trisa.io/">TRISA</a></p>
\ No newline at end of file
+	    <p><i class="fa fa-code"></i> <a href="https://github.com/trisacrypto/trisa/blob/main/LICENSE">Open Source Licensed</a> by <a href="https://travelrule.io/">TRISA</a></p>
diff --git a/pkg/trisa/gds/api/v1beta1/testdata/alice-trixo.json b/pkg/trisa/gds/api/v1beta1/testdata/alice-trixo.json
index c27d434a..6735de8d 100644
--- a/pkg/trisa/gds/api/v1beta1/testdata/alice-trixo.json
+++ b/pkg/trisa/gds/api/v1beta1/testdata/alice-trixo.json
@@ -41,17 +41,17 @@
   "contacts": {
     "technical": {
       "name": "Benjamin Bengfort",
-      "email": "benjamin@trisa.io",
+      "email": "benjamin@travelrule.io",
       "phone": "+1-701-456-5555"
     },
     "legal": {
       "name": "John Jefferies",
-      "email": "jj@trisa.io",
+      "email": "jj@travelrule.io",
       "phone": "+1-202-789-5555"
     },
     "administrative": {
       "name": "Laura Montoya",
-      "email": "laura@trisa.io",
+      "email": "laura@travelrule.io",
       "phone": "+1-310-123-5555"
     },
     "billing": {
@@ -88,4 +88,4 @@
     "must_safeguard_pii": true,
     "safeguards_pii": true
   }
-}
\ No newline at end of file
+}