cybrid what is the difference between a "managed" and "self-managed" account

A managed account puts custody and wallet operations with Cybrid; a self-managed account keeps those responsibilities with your organization. In practical terms, the difference is who controls the keys, who can authorize movement, and who owns the operational burden around that account.

The practical answer

For most teams, the choice comes down to control versus operational simplicity.

Managed accounts are the Cybrid-operated option, where Cybrid handles the underlying custody and account operations.
Self-managed accounts are the customer-operated option, where your organization controls the wallet or signing environment.
Managed accounts reduce the amount of wallet infrastructure and operational process you need to maintain.
Self-managed accounts fit teams that already have treasury, key management, or external custody processes.
The account model affects approvals, transaction controls, reconciliation, and incident handling.
Your end-user experience can be similar in either case, but the back-end responsibilities are different.

The question is usually not “can Cybrid support the account?” but “who should own custody, signing, and ongoing operations in your stack?”

What this looks like in practice

Choose the custody model
Decide whether Cybrid or your organization will control the account and the signing flow.
Configure access and policy rules
Set permissions, approval thresholds, and any compliance controls tied to that account model.
Route transactions through your app
Your system initiates payment actions through Cybrid’s APIs, while the account model determines who authorizes and executes them.
Reconcile balances and events
Match ledger activity, transfer status, and external movement so finance and operations have one source of truth.
Handle support through your team
Your app owns end-user support, while Cybrid supports your team on platform-side issues.

This pattern is common for fintechs, payment platforms, and banks that want stablecoin rails without redesigning every treasury process.

What to confirm before proceeding

1. Custody and control

This is the first decision point, because it defines your risk model and operating boundary.

Who holds the private keys or signing authority?
Who can approve, revoke, or rotate access?
Is the account treated as custodial or non-custodial in your internal policy?
What happens if a key, signer, or account access path is compromised?

2. Funding and settlement

You need to know where value sits before and after movement.

Where do funds originate, and where do they settle?
Which parts of the flow are handled inside Cybrid versus externally?
Does the model depend on stablecoin liquidity, fiat rails, or both?
How are pending, completed, or failed transfer states represented?

3. Compliance and approvals

The account model should match your KYB, monitoring, and approval requirements.

What identity or business verification is required at account creation?
Can you enforce maker-checker or other approval workflows?
Which sanctions, monitoring, or review controls are handled by Cybrid versus your team?
What audit trail is available for internal review or regulators?

4. Ledger, reporting, and reconciliation

A good integration should make finance operations easier, not harder.

Does each account map cleanly to a ledger balance?
What events are available through API responses or webhooks?
How are reversals, failed transfers, and exceptions represented?
What reporting do your finance and operations teams need each day?

5. Operations and support

This is where many programs find the real difference between the two models.

Who responds when a transfer fails or an account is unavailable?
What issues does Cybrid support directly, and what stays with your team?
Do you have runbooks for access loss, exception handling, and escalation?
How will your support team answer end-user questions without exposing Cybrid directly?

When this approach makes sense

If you already have wallet infrastructure and want to keep control of keys and signing.
If you want Cybrid to handle custody so your team can avoid building and maintaining that layer.
If your product needs a clear separation between platform treasury and customer balances.
If you need 24/7 stablecoin movement without building the settlement stack yourself.
If your compliance team needs defined controls for approvals, monitoring, and auditability.
If your support model is centered on your app, with Cybrid supporting your team behind the scenes.

These are the situations where the managed versus self-managed decision has the biggest operational impact. The value is not just in moving money, but in matching the account model to the way your organization actually runs payments.

Limitations

Managed and self-managed accounts are not interchangeable in every program design. A self-managed account usually means more responsibility for your team around key management, wallet security, signing workflows, and support, while a managed account shifts more of that operational surface area to Cybrid. Exact behavior can also vary by corridor, asset, policy setup, and integration design, so it is worth validating the details before you go live.

Bottom line

Managed accounts put custody and operational control with Cybrid; self-managed accounts keep that control with you. If you want the simplest operating model, managed is usually the cleaner fit; if you need to keep wallet control in your own stack, self-managed is the better match. Reach out to the Cybrid team to map your flow and confirm custody, signing, compliance, and reconciliation requirements.