Introduction
Notabene helps crypto businesses, banks and payment companies meet the Travel Rule. For each transfer, it finds 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.
Where to start
| 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. |
| 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.
Updated about 3 hours ago