Skip to main content

[V2.1] Key Terms

The words you meet in the v2.1 dashboard, explained for compliance teams.

H
Written by Herculano Costa

The dashboard uses a small set of words with exact meanings, and several of them look alike. Here is what each one means when you meet it on screen.

People and institutions

  • Customer: a person or business your organization has a direct relationship with. In a transfer, your customer is the originator or the beneficiary.

  • Originator: the customer who sends the funds, a customer of the sending institution.

  • Beneficiary: the customer who receives the funds, a customer of the receiving institution.

  • Counterparty institution: the institution on the other side of a transaction. Regulations and older Notabene material call it a VASP.

  • Intermediary: a business acting on behalf of someone else in a transaction. An exchange or a bank is an intermediary for its customers.

  • Counterparty customer: a customer of the counterparty institution, the person or business your customer transacts with.

  • DID: short for Decentralized Identifier, an institution's identity on the network. Counterparty institutions use your DID to reach you.

Wallets

  • Hosted wallet: a wallet whose keys an institution or a wallet provider holds for the customer.

  • Self-hosted wallet: a wallet whose keys the customer holds themselves, with no institution behind it. Other material calls it an unhosted or non-custodial wallet.

  • Proof of ownership: evidence that a customer controls a self-hosted wallet address.

  • Address confirmation: the receiving institution confirms that its customer controls the receiving address. Your customer's personal data is sent only after it, and the confirmation is kept for later transfers to the same address.

Transactions and the Travel Rule

  • Transaction: any movement of value the dashboard tracks.

  • Transfer: a crypto or stablecoin transaction between two customers, through their institutions. Every transfer is a transaction.

  • Travel Rule: the rule that makes institutions exchange information about the originator and the beneficiary of a transfer above a threshold.

  • Threshold: the amount above which the Travel Rule applies in a jurisdiction.

  • Travel Rule data: the information about the originator and the beneficiary that the two institutions exchange. It travels separately from the funds.

  • Settlement: the movement of the funds on the blockchain, recorded by its transaction hash. It is a separate step from the compliance decision.

Policies and requirements

  • Policy: a rule your organization sets that approves, flags or rejects a transaction. When several policies apply, the strictest outcome wins, so one rejection rejects the transaction.

  • Flag: your policies' verdict that holds a transaction for a person on your team to review. It is a step on the way, not an outcome.

  • Not reviewed: anything you haven't reviewed yet, such as a new institution, customer or wallet. You set a default for it, so it is approved, flagged or rejected automatically.

  • Requirement: one obligation that must be met before an institution can authorize a transaction, such as sending Travel Rule data or confirming an address.

  • Skipped: a requirement that timed out, so the transaction moved on. Every skip is recorded in the audit trail.

  • Requirements preset: the starting point for your requirements. With straight-through processing your side doesn't wait for the counterparty, and with counterparty coordination it waits for up to a minute.

Statuses

Every transaction shows two statuses, because each institution keeps its own decision.

My Status is where your organization stands:

  • Pending: your policies haven't decided yet, a flag waits for review, or a requirement isn't met.

  • Authorized: your policies approved the transaction and every requirement is met or skipped.

  • Rejected: your organization rejected the transaction.

  • Canceled: the originator's institution withdrew the transaction.

Transaction status is where the transaction stands across every institution and the blockchain:

  • Active: at least one institution is still Pending.

  • Ready to settle: every institution has authorized the transaction, so the funds can be sent.

  • Rejected or Canceled: at least one institution rejected or canceled it.

  • Settled: the funds moved and every institution has authorized the transaction.

  • Settled Incomplete: the funds moved while an institution hadn't authorized yet. It becomes Settled once every institution has.

A requirement has its own status too: Pending, Satisfied, Partially satisfied, Skipped, Rejected or N/A.

Jurisdictions

Each country carries a status: Trusted, Watched, Banned or Not Reviewed. A status has no effect on transactions until a policy uses it, and your policies decide what each one means. Watched is a property of a country, and Flagged is a policy verdict on a transaction, so the two never mean the same thing.

For the API fields behind these terms, see the Glossary in the developer docs.

Did this answer your question?