Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

TRUST

You can view and edit your TRUST configuration under the 'TRUST' tab.

For initial setup, follow the TRUST Onboarding guide before saving these settings. It covers registration with TRUST, selecting the pre-production environment, and preparing the certificates and keys required below.

Configure your VASP

VASP Configuration Settings

VASP LEI

The LEI (Legal Entity Identifier) field is a unique identifier for your VASP, you can register for this on the Global Legal Entity Identifier Foundation (GLEIF) website or, for testing purposes, use the 21 Analytics LEI Generator. The owner of the VASP or a representative should present you with their LEI; however, the LEI registry is also public.

Note that this needs to match the value that you provided to TRUST during your onboarding. Your VASP's legal name is then taken from the bulletin board entry registered for this LEI, which is the name counterparties match against. Saving the settings fails if the bulletin board holds no such entry.

Default Counterparty Status

When VASPs are fetched from the TRUST network for the first time, they will receive this counterparty status. "Trusted" means you will be able to transact with them without manual vetting. "Blocked" means you will have to approve them on an individual basis after having performed counterparty due diligence.

TLS Server Identity (optional)

The TLS Server Identity is the PEM-encoded identity used by your TRUST PII server for incoming mTLS connections. It must include a certificate chain and exactly one private key, and the certificate must be valid for server authentication. During initial setup you must provide it; on later updates you can leave it empty to keep the existing server identity. See Obtaining Certificates for a basic certificate ordering guide.

mTLS Client Identity (optional)

The mTLS Client Identity is the PEM-encoded identity used for outgoing TRUST connections (for example to the TRUST bulletin board). It must include a certificate chain and exactly one private key, and the certificate must be valid for client authentication. During initial setup you must provide it; on later updates you can leave it empty to keep the existing client identity. If the certificate signals suitable combined client and server authentication, this may be identical to the Server Identity above. See Obtaining Certificates for a basic certificate ordering guide.

Decryption Key (optional)

The PII payloads other VASPs send to you are encrypted with the public key that you submitted to the TRUST bulletin board. Upload the corresponding private key here. This key is separate from the private keys in your TLS identities.

If you don't supply one in the initial configuration, a keypair will be generated for you. Its public key must then be registered with TRUST before counterparties can send payloads you can decrypt. If you already submitted a public key during onboarding, supply its matching private key instead. On later updates, leaving this field empty keeps the existing decryption key. Use Copy Encryption Public Key to retrieve the public key after saving.

Beneficiary Name Matching

Choose how strict or lenient you want to be regarding beneficiary name matching. The options work as described for TRP and hold their own values here, independent of the TRP tab.