Version 1.33 is a SaaS release that introduces skip quarantine for internal transfers, allowing organizations to streamline compliance workflows for transfers between trusted internal accounts.
Ripple Custody Version 1.33 introduces the ability to skip quarantine for internal transfers. This feature allows you to configure accounts to automatically bypass compliance quarantine when receiving transfers from other Ripple Custody accounts within your organization.
Internal transfers—movements between accounts you control—typically represent low-risk activity that does not require the same level of compliance scrutiny as external deposits. By configuring skip quarantine, you can:
- Reduce operational overhead — Eliminate manual release steps for routine internal movements
- Accelerate fund availability — Internal transfers proceed immediately without quarantine delays
- Maintain audit compliance — The system logs all quarantine decisions with
QuarantineAppliedandQuarantineSkippedevents
You configure skip quarantine at the account level using the skipQuarantineFrom property:
| Value | Behavior |
|---|---|
None | Default. All incoming transfers are quarantined normally. |
Domain | Skip quarantine for transfers from accounts in the same domain. |
Instance | Skip quarantine for transfers from any account in the same Ripple Custody instance, including child domains. |
Even with skip quarantine configured, the following transfers still go through quarantine:
- Transfers from external blockchain addresses (not managed by Ripple Custody)
- Transfers from accounts outside the configured scope
This feature is API-only in Version 1.33.
For more information, see:
Ripple progressively deploys Version 1.33 across SaaS environments starting April 3, 2026.
Ripple takes great care in testing its applications and ensuring that there are no regressions or breaking changes. Should you experience unexpected behavior, reach out to the Support team by creating a ticket on our Support Portal or contact your Customer Partner Engineer (CPE).