Create your account

Your Notabene account gives your organization a DID, its identity on the Notabene network, built from your domain and your jurisdiction.

Sandbox
Production
Steps
Sandbox
Production

Done by Notabene

← → the step before and after · Esc all steps
Step 1
1Sign up
You, on the sign-up page

With your work email, your organization and its jurisdiction: 1. Sign up.

← → the step before and after · Esc all steps
Step 2
2Check your domain
You, at sign-up

From your sign-up email, with an optional suffix: 2. Check your domain.

← → the step before and after · Esc all steps
Step 3
3Select your jurisdiction
You, at sign-up

It becomes a path in your did:web: 3. Select your jurisdiction.

← → the step before and after · Esc all steps
Step
Notabene creates your did:web
Notabene, when the account is created

From your domain and your jurisdiction: Notabene creates your did:web.

← → the step before and after · Esc all steps
Step 4
4Request activation
Notabene, on your request

From your Account Manager, or [email protected]: 4. Request activation.

← → the step before and after · Esc all steps
Sandbox
Notabene hosts your DID document
Notabene, for sandbox accounts

There is nothing for you to publish: 5. In production, host your DID document.

← → the step before and after · Esc all steps
Production · Step 5
5Host your DID document
You, on your web server

Once your account is active, at the address your did:web points to: 5. In production, host your DID document.

← → the step before and after · Esc all steps
Last step
Ready for API credentials
You

Create an API credential and check that everything works: Then check that it works.

← → the step before and after · Esc all steps
  1. Sign up (You, on the sign-up page). With your work email, your organization and its jurisdiction: 1. Sign up.
  2. Check your domain (You, at sign-up). From your sign-up email, with an optional suffix: 2. Check your domain.
  3. Select your jurisdiction (You, at sign-up). It becomes a path in your did:web: 3. Select your jurisdiction.
  4. Notabene creates your did:web (did:web:{domain}:{jurisdiction}, Notabene, when the account is created). From your domain and your jurisdiction: Notabene creates your did:web.
  5. Request activation (Notabene, on your request). From your Account Manager, or [email protected]: 4. Request activation.
  6. Sandbox: Notabene hosts your DID document (Notabene, for sandbox accounts). There is nothing for you to publish: 5. In production, host your DID document.
  7. Production: Host your DID document (You, on your web server). Once your account is active, at the address your did:web points to: 5. In production, host your DID document.
  8. Ready for API credentials (You). Create an API credential and check that everything works: Then check that it works. Continues in: Authentication.

1. Sign up

Sign up with your work email, your organization’s details and its jurisdiction, at sandbox.notabene.id for sandbox, and at eu-a.notabene.id or us-a.notabene.id for production in the EU or the US. Sandbox and production are separate accounts, so create the one you need, or both.

2. Check your domain

Notabene takes your domain from your sign-up email, so [email protected] gives example.com. For another domain, sign in with an email address on it. You can also add a suffix such as payments, which becomes a path in your DID.

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

Your DID sets the address of your DID document. In sandbox, Notabene hosts it on a sandbox.notabene.id address, and in production you host it on your own domain.

SandboxHosted by Notabene

Your DID

did:web:examplecom-4f2a9.sandbox.notabene.id:pt

Its document

https://examplecom-4f2a9.sandbox.notabene.id/pt/did.json

ProductionHosted by you

Your DID

did:web:example.com:pt

Its document

https://example.com/pt/did.json

Production, with a suffixHosted by you

Your DID

did:web:example.com:payments:pt

Its document

https://example.com/payments/pt/did.json

AccountYour DIDIts document
Sandboxdid:web:examplecom-4f2a9.sandbox.notabene.id:pthttps://examplecom-4f2a9.sandbox.notabene.id/pt/did.json
Productiondid:web:example.com:pthttps://example.com/pt/did.json
Production, with a suffixdid:web:example.com:payments:pthttps://example.com/payments/pt/did.json

The dashboard shows your DID under My Organization › My Organization.

4. 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.

5. In production, host your DID document

Once your account is active, read your DID document through the API and publish it 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.

Then check that it works

Create an API credential for your backend under Developers › API Credentials and use it to request access tokens, as described in Authentication. Then check that:

  • Notabene reaches your DID document, as the dashboard shows under My Organization › My Organization, in DID Document reachability on the Capabilities tab.
  • You can request an access token with your API credentials.
  • In production, your account is visible in the Notabene network.

Did this page help you?