# Travel Rule

Manage Travel Rule compliance for cryptocurrency transfers using the Ripple Custody API.

## Overview

The Travel Rule (FATF Recommendation 16) requires Virtual Asset Service Providers (VASPs) to exchange customer information for cryptocurrency transfers above certain thresholds. Ripple Custody integrates with Notabene to automate Travel Rule compliance.

Travel Rule and transaction screening (Chainalysis/Elliptic) can be used independently or together. When both are enabled, transactions must pass both checks—if both are approved the transaction is authorized; if either is rejected, the transaction is rejected.

## Prerequisites

Before using Travel Rule APIs, complete the [Travel Rule setup](/products/custody/v1.34/resources/guides/travel-rule-setup):

- Connect your Notabene account to Ripple Custody
- Register wallet addresses with Notabene


## Workflows

### Outgoing transfers

| Workflow | Description |
|  --- | --- |
| [Send without PII](/products/custody/v1.34/api/accounting/travel-rule/outgoing-no-pii) | Outgoing transfer when PII is not required |
| [Send with PII](/products/custody/v1.34/api/accounting/travel-rule/outgoing-with-pii) | Outgoing transfer when PII is required and submitted before creating the intent |


### Incoming transfers

| Workflow | Description |
|  --- | --- |
| [Receive assets](/products/custody/v1.34/api/accounting/travel-rule/incoming) | Incoming transfers are detected, funds quarantined, and released when compliance checks pass |


## Related topics

- [Travel Rule concepts](/products/custody/v1.34/concepts/compliance/travel-rule) — Architecture and compliance logic
- [Travel Rule setup](/products/custody/v1.34/resources/guides/travel-rule-setup) — Configuration instructions
- [Send assets](/products/custody/v1.34/api/accounting/send-assets) — Standard asset transfer workflows