Make MATTR VII assets available
After verifying your custom domain, you must ensure the following assets are publicly available for your custom domain to work properly:
/.well-known/did.json
: This is your domaindid:web
DID document, which must be available for yourdid:web
to be resolvable. To make this asset available via your custom domain, it is recommended you host it on your custom domain. Refer to Self Hosting under Hosting a did:web for more information./manifest.json
: This file is required to provide digital wallet clients with information about your custom domain, such as its name and logo image. To make this asset available via your custom domain, redirect any calls tohttps://YOUR_CUSTOM_DOMAIN/manifest.json
tohttps://YOUR_TENANT_URL/manifest.json
. Don't forget to swapYOUR_CUSTOM_DOMAIN
andYOUR_TENANT_URL
with your specific details./.well-known/did-configuration
: This file is used to establish trust in the DID to domain linkage. This ensure any digital wallet clients can resolve DIDs from your custom domain and verify the DID-to-domain linkage. To make this asset available via your custom domain, redirect any calls tohttps://YOUR_CUSTOM_DOMAIN/.well-known/did-configuration
tohttps://YOUR_TENANT_URL/.well-known/did-configuration
. Don't forget to swapYOUR_CUSTOM_DOMAIN
andYOUR_TENANT_URL
with your specific details./.well-known/openid-credential-issuer
: This file only is required if your implementation uses OpenID credential provisioning. To make this asset available via your custom domain, redirect any calls tohttps://YOUR_CUSTOM_DOMAIN/.well-known/openid-credential-issuer
tohttps://YOUR_TENANT_URL/.well-known/openid-credential-issuer
. Don't forget to swapYOUR_CUSTOM_DOMAIN
andYOUR_TENANT_URL
with your specific details.
If any of the redirect paths are already used by your main website, you may need to create a separate subdomain for your MATTR VII custom domain.
What's next?
Once the above assets are publicly available, your custom domain is fully configured to work with your MATTR VII tenant.