Introduction
Notabene helps crypto businesses, banks and payment companies meet the Travel Rule. For each transfer, it tries to find the institution on the other side, says which data the rules require and exchanges that data with it before the funds move. The decision on every transfer stays with your own policies.
How a transfer works
Assess
Your policies
Coordinate
With the counterparty
Your institution
The counterparty
Settle
On-chain
You send the funds and give Notabene the transaction hash.
- Assess. Your policies, such as those for a jurisdiction, a counterparty institution or an amount, approve the transfer.
- Coordinate. Notabene sends the transfer details to the counterparty, and sends your customer’s personal data once the counterparty confirms that the destination address belongs to its customer.
- Settle. Once both sides are Authorized, the transfer is ready to settle: you send the funds and give Notabene the transaction hash.
Where to start
Evaluating Notabene
Policies for what Notabene does and what you decide, Transfers for how a transfer works, and Security and status for how Notabene protects data.
The engineer who integrates
Authentication, Transfers, then Withdrawals and Deposits.
In compliance
Policies, Data collection for which data each jurisdiction requires, Integrations for screening, Encryption and the Glossary.
In operations or support
Statuses, Webhooks, Errors, Rate limiting, Security and status for support, and Notabene IPs.
Moving from v2
| You are | Start with |
|---|---|
| Evaluating Notabene | Policies for what Notabene does and what you decide, Transfers for how a transfer works, and Security and status for how Notabene protects data. |
| The engineer who integrates | Authentication, Transfers, then Withdrawals and Deposits. |
| In compliance | Policies, Data collection for which data each jurisdiction requires, Integrations for screening, Encryption and the Glossary. |
| In operations or support | Statuses, Webhooks, Errors, Rate limiting, Security and status for support, and Notabene IPs. |
| Moving from v2 | Moving from v2 to v2.1. |
How an integration fits together
Integrating with Notabene
Set up once, then collect customer data as needed in your withdrawal and deposit flows.
Once
Then register your customers and add a webhook, as Integration setup explains.
Once
Access token for every backend call to Notabene. Stays on your server.
Delegate token for your frontend, scoped to one customer.
Whenever customer data is needed
Collect the Travel Rule data you’re missing directly from your customer, in the withdrawal or deposit flow.
Sending
Customer requests a withdrawal
Amount, asset and destination address.
Collect beneficiary details
Who and where the funds are going, with Data collection.
Create the transfer
Always send the Travel Rule data before executing on-chain.
Wait until it is ready to settle
Send the funds once every institution has authorized the transfer, which your webhook tells you as each one does.
Send the funds and record the transaction hash
The transfer is complete.
Receiving
A deposit comes in
Its Travel Rule data or its funds arrive first.
Data first
The Travel Rule data arrives
Confirm the address, then review the personal data and run name matching.
Funds first
The funds arrive with no data
Find out who sent them, then request the data from the sending institution or ask your customer.
Decide on the deposit
Your policies approve, flag or reject it. Once it is authorized, credit your customer.
- Account setup, once: create your account, get your credentials and host your DID document, then register your customers and add a webhook, as Integration setup explains.
- Authentication, once: your backend uses an access token for every call to Notabene and keeps it on your server, and your frontend uses a delegate token, scoped to one customer.
- Data collection, whenever customer data is needed: collect the Travel Rule data you’re missing directly from your customer in the withdrawal or deposit flow, with Notabene Embedded (drop-in components such as Withdrawal Assist, which collect and validate the data for you) or with your own screens that call the Travel Rule APIs with a delegate token.
- Withdrawals, when sending: your customer requests a withdrawal with an amount, an asset and a destination address, and you collect the beneficiary details and create the transfer, always before executing on-chain. Once every institution has authorized it, which your webhook tells you as each one does, it is ready to settle: you send the funds and record the transaction hash.
- Deposits, when receiving: the Travel Rule data or the funds arrive first. When the data comes first, confirm the address, review the personal data and run name matching; when the funds come first, find out who sent them, then request the data from the sending institution or ask your customer. Your policies then approve, flag or reject the deposit, and once it is authorized you credit your customer.
Your integration type
Every integration registers its customers, and a webhook endpoint is recommended. The rest depends on these three choices.
Direction
Withdrawals, deposits or both. For deposits, you also register each deposit address you give a customer. See Withdrawals, Deposits and Wallets.
Wallets
In a self-managed integration, you register your addresses yourself. In a wallet-managed integration, a wallet provider such as Fireblocks, DFNS, Zodia or Utila registers them for you. See Integrations.
Data collection
The embedded components in your web app, Withdrawal Assist and Deposit Assist, or your own screens. See Data collection.
| Choice | Options |
|---|---|
| Direction | Withdrawals, deposits or both. For deposits, you also register each deposit address you give a customer. See Withdrawals, Deposits and Wallets. |
| Wallets | In a self-managed integration, you register your addresses yourself. In a wallet-managed integration, a wallet provider such as Fireblocks, DFNS, Zodia or Utila registers them for you. See Integrations. |
| Data collection | The embedded components in your web app, Withdrawal Assist and Deposit Assist, or your own screens. See Data collection. |
All setup steps are listed in Go live.
Updated 11 days ago