Ripple Custody Version 1.30 is a SaaS release that introduces Travel Rule compliance through integration with Notabene, and support for Securosys HSMs.
The Travel Rule (FATF Recommendation 16) requires Virtual Asset Service Providers (VASPs) to collect, verify, and share customer information when transferring digital assets above certain thresholds. This regulation applies in the US, EU, Singapore, and other jurisdictions, with thresholds that vary by jurisdiction.
Ripple Custody v1.30 integrates with Notabene, a Travel Rule network that connects VASPs for secure information exchange. When a transfer exceeds the configured threshold, Ripple Custody enables customers to:
- Create a Travel Rule message with the counterparty VASP.
- If PII is required, collect it from the end user and submit via the API.
- Create a transfer intent using the returned
suggestedIntentId. - System runs screening first, then Travel Rule check (sequential).
- Transaction executes when configured checks pass.
This integration works within the existing Ripple Custody API.
See also:
- Travel Rule introduction
- Travel Rule pre-requisites — Notabane registration and configuration guide.
- Travel Rule workflows — API examples for incoming and outgoing transfers.
| API Operation | Endpoint |
|---|---|
| Create a Travel Rule message for a transfer | POST /v1/domains/{domainId}/compliance/travel-rule/providers/{provider}/messages |
| Get a travel rule transfer by ID | GET /v1/domains/{domainId}/compliance/travel-rule/providers/{provider}/messages/{travelRuleId} |
| Append PII to a travel rule message | POST .../messages/{travelRuleId}/pii |
| Present end-to-end encrypted PII to a travel rule message without policy | POST .../messages/{travelRuleId}/encrypted-pii |
| Append end-to-end encrypted PII to a travel rule message | POST .../messages/{travelRuleId}/policies/{travelRulePolicyId}/encrypted-pii |
- Bi-directional compliance: Travel Rule checks for outgoing withdrawals and incoming deposits.
- Threshold-based activation: Configured in Notabene per jurisdiction and currency.
- Unified decisioning: Combines risk screening and Travel Rule outcomes; both must approve if both are configured.
- PII options: Submit plaintext (Notabene encrypts) or pre-encrypted for end-to-end encryption.
- Supported blockchains: See Supported blockchain ledgers.
- Register as a VASP with Notabene and set up your DIDdoc.
- Provide Notabene credentials to your Ripple partner engineer.
- Wallet addresses are registered with Notabene (can also be done by customer).
Travel Rule is opt-in and disabled by default. Requires Notabene credentials to activate.
- Incoming transfers without Travel Rule data are flagged for manual review.
Ripple Custody v1.30 adds support for Securosys HSMs. For more information, see Securosys Primus HSM integration.
Version 1.30 deploys to SaaS environments starting December 17, 2025, with production environments on December 26, 2025.
For issues, create a ticket on the Support Portal or contact your Customer Partner Engineer.