Appearance
Offboarding
Offboarding removes customers or individual wallet addresses from BRRR monitoring. Once removed, BRRR stops evaluating on-chain activity and will not issue further RISK_ASSESSMENT webhooks for the affected entity.
Choosing the right endpoint
Customer has multiple addresses?
│
┌─────┴─────┐
│ Yes │ No
▼ ▼
Remove Remove
address customer
only (+ all addresses)| Situation | Use |
|---|---|
| Customer has multiple addresses; remove only one | POST /api/v4/partner/customer/remove-address |
| Customer has a single address, or you want to remove the customer entirely | POST /api/v4/partner/customer/remove |
Single-address constraint
If a customer has only one registered address, that address cannot be removed independently — the entire customer entity must be removed instead. Attempting to remove the sole address of a customer returns a 400 error.
Endpoints
| Endpoint | Description |
|---|---|
POST /api/v4/partner/customer/remove | Remove a customer and all of their associated wallet addresses |
POST /api/v4/partner/customer/remove-address | Remove a specific wallet address from an existing customer |
What happens after offboarding
Once a customer or address is removed:
- Monitoring stops — BRRR no longer tracks on-chain activity for the removed entity
- No further webhooks —
RISK_ASSESSMENTevents will not fire for removed addresses - Settlement blocked — removed addresses cannot be included in new settlement quotes
- Address freed — a removed address can be re-registered to the same or a different customer in the future
Re-registering an address
If you need to resume monitoring a previously removed address, register it again using POST /api/v4/partner/customer/add-address. BRRR will perform a fresh risk assessment after re-registration.
In-flight settlements
Removing a customer or address does not cancel settlements that are already in progress. Any settlement with status CONFIRMED, PROCESSING, or SENT will continue to completion. Only new settlement quotes are blocked for removed entities.
