Create your account
Your Notabene account gives your organization a DID, its identity on the Notabene network, built from your domain and your jurisdiction.
Done by Notabene
With your work email, your organization and its jurisdiction: 1. Sign up.
The domain your DID document will be hosted on: 2. Choose your domain.
It becomes a path in your did:web: 3. Select your jurisdiction.
From your domain and your jurisdiction: Notabene creates your did:web.
There is nothing for you to publish: 4. In production, host your DID document.
At the address your did:web points to: 4. In production, host your DID document.
From your Account Manager, or [email protected]: 5. Request activation.
Create an API credential and check that everything works: Then check that it works.
1. Sign up
Sign up with your work email, your organization’s details and its jurisdiction, at sandbox.notabene.id for sandbox and at www.notabene.id (placeholder) for production. Sandbox and production are separate accounts, so create the one you need, or both.
2. Choose your domain
By default, Notabene uses the domain of your email address for your did:web. If your DID document has to be hosted on another domain or on a subdomain, enter that domain instead. Either way, pick a domain where your team can publish a file over HTTPS.
| You | Your domain |
|---|---|
| Signed up as [email protected] | example.com |
| Host on static.example.com | static.example.com |
| You | Your domain |
|---|---|
| Signed up as [email protected] | example.com |
| Host on static.example.com | static.example.com |
Set the domain while you create the account, because otherwise your did:web may point to a place where you cannot publish your DID document.
3. Select your jurisdiction
Your jurisdiction becomes a path in your did:web, written as its country code, for example pt for Portugal. It also decides which Travel Rule requirements apply to you, and the dashboard shows it as Applied jurisdiction under Authorization Rules › Travel Rule.
Notabene creates your did:web
Notabene builds your DID from your domain and your jurisdiction, and the DID in turn sets the exact address where your DID document must be hosted. The dashboard shows your DID under Settings › My Organization.
| Your DID | Where its document is hosted |
|---|---|
did:web:example.com:pt | https:/ |
did:web:static.example.com:pt | https:/ |
| Your DID | Where its document is hosted |
|---|---|
did:web:example.com:pt | https://example.com/pt/did.json |
did:web:static.example.com:pt | https://static.example.com/pt/did.json |
4. In production, host your DID document
Publish your DID document at the address your did:web points to, as described in Host your DID document. Counterparty institutions read your public keys from it, so a production account does not work until it is there. In sandbox, Notabene hosts it for you.
5. Request activation
To have your account activated, contact your Notabene Account Manager, or write to [email protected] if you do not have one. Notabene activates accounts on request, in sandbox as in production, and activation does not wait for your DID document.
Until your account is active, you cannot create production API credentials, and other institutions on the Notabene network cannot see you.
Then check that it works
Create an API credential for your backend under Settings › API Credentials and use it to request access tokens, as described in Authentication. Then check that:
- Notabene resolves your DID document, as the dashboard shows under My Organization › Capabilities › Network health.
- You can request an access token with your API credentials.
- In production, your account is visible in the Notabene network.
Updated about 6 hours ago