7.3.0

Auto-discovery of Counterparty VASPs

The manual addition of VASPs via TRP has been revoked to reduce workload and risk of errors. You will now see the following when you click on the 'Add VASP' button:

You can see the full auto-discovery flow in our tour.

Support for multiple risk score providers

21 Travel Rule now supports risk scores from Chainalysis and, most recently, Beosin, out-of-the-box. Moreover, any other provider can be added via integration with the API.

Improvements on Emails

Emails have been subject to a few improvements. Your automated emails will now have your VASP name and VASP LEI in the email body. We also now use HTML instead of plain text on emails, so this allows for styling of the emails, which has been improved. Our emails still use encryption for the transaction data, keeping the channel of communication secure.

TRP now supports Legal Persons

TRP now supports the option to add Legal Persons as customers. This is an addition to the previous option of adding a Natural Person as a customer. This is useful for VASPs that are subject to stricter Travel Rule requirements in their jurisdiction.

You can add Legal Person customers to your Address Book.

Now, with TRP, you can also send transactions to Legal Persons at your counterparty VASPs:

Expected Address option for AOPP Proofs

When making AOPP proofs, you now have the option to add an expected address. Not only does this concretely tie an address to a name, but it can also be used to reduce customer errors; for example, in the event of multiple wallet addresses, your customer may attempt to prove ownership over an unintended address.

More

Other technical improvements have been added to this release, such as:

• A /healthcheck endpoint to all services
• BlueWallet now allows the user to submit an xPub key through the AOPP Portal
• IDs have been improved by banning characters that could cause issues in URLs
• The ID field for registering expected AOPP proofs has been deprecated. Users should rely on customer_id instead
• The AOPP Portal wallet SVGs have been fixed for Safari
• The sha256 hash is now displayed for Ledger on the AOPP Portal, relevant for older Ledger firmware versions
• Various improvements to logging messages
• Postgres client connections now support TLS
• Fixed RUSTSEC-2024-0399
• bun now uses a text-based lockfile