Security, custody and human control
Value moves only on proof, within the authority you set.
Before you let a provider hold your value pending release, you need a documented regulatory perimeter, evidenced segregation, and a release that binds to a verified counterparty. This page states what Fideleo controls at the point of release, who is accountable, and where the perimeter still requires regulatory confirmation.
Controls at the point of release
What must be true before any value leaves custody.
These controls sit at the boundary of every release. They are the checks a compliance and risk officer needs in order to defend onboarding a value-holding provider to auditors and the regulator.
- DIFC-aligned compliance path
- DFSA licence — intended, perimeter to be confirmed
- KYC/AML at every release
- Segregation of held value
A documented regulatory perimeter
Fideleo pursues a DIFC-aligned compliance path rather than operating as an unregulated intermediary. The intended perimeter is a DFSA Category 3D (Providing Money Services) licence; where the ledger custodies value pending release, client-money obligations may push toward a Category 3C licence. The exact perimeter requires DFSA legal confirmation.
Segregation of held value
Value held pending release is treated as segregated. Where custody obligations apply, they are treated as a regulatory requirement to be met, not engineered around.
Payment bound to verified counterparty identity
Counterparty impersonation in the payment instruction is the dominant fraud vector. Fideleo binds a release to a verified counterparty identity, with KYC/AML checks, so a vendor-imposter instruction is defeated at the point of release rather than pursued after loss.
A tamper-evident audit trail
Every release produces an auditable record of the conditions met, the evidence validated, the policy applied and any human decision taken — suitable for dispute resolution and compliance review.
Human authority is enforced, not advised.
Fideleo is designed so that no material or irreversible value movement occurs without either an explicit policy authorisation you set in advance or a real-time human approval. Automation is bounded to within-policy releases. Everything above a value threshold, everything irreversible, and anything flagged as ambiguous is held for a human decision.
What AI colleagues do
AI colleagues run the operational core. They monitor fulfilment conditions against agreed terms, ingest and validate delivery artefacts and oracle confirmations, reconcile balances across escrow accounts, and route exceptions.
Releases that fall within your pre-set policy limits execute automatically. Releases that breach a threshold, are irreversible, or are ambiguous are held and passed to an accountable human with the transaction and its evidence attached.
What accountable humans do
Named human governors define policy-as-code, approve threshold breaches and irreversible releases, adjudicate contested cases, and own the fiduciary and regulatory obligations for what their agents commit to.
Delegated-authority and dual-approval limits are enforced as mandatory controls, not advisory hints. A release cannot exceed the limits you set, because the limit is checked before value moves.
Release fires on proof, not on a timer
Release is conditioned on validated fulfilment evidence — delivery artefacts, oracle confirmations, or mutual sign-off — not on a mechanical timeout or notice. A payment does not go out on an elapsed clock when delivery is unproven.
Questions before onboarding
What a risk, treasury or finance owner asks first.
Are you a regulated custodian today?
Fideleo is pre-launch and is pursuing a DIFC-aligned compliance path rather than operating as an unregulated intermediary. The intended perimeter is a DFSA Category 3D (Providing Money Services) licence at base capital of USD 200,000, with the DFSA Innovation Testing Licence sandbox as a staged entry route. If the ledger custodies value pending release, client-money and asset-holding obligations may push toward a Category 3C licence at base capital of USD 500,000. The exact perimeter requires DFSA legal confirmation, and we state it as intended rather than achieved.
How is a release bound to a verified counterparty identity?
Payment is bound to a verified counterparty identity, subject to KYC/AML checks, before any value moves. Because the check sits at the point of release, an instruction that impersonates a known vendor is defeated at release rather than clawed back after loss.
Which releases require my explicit human approval?
Any release that exceeds a value threshold, is irreversible, or breaches a delegated-authority limit is held and routed to an accountable human with the transaction and its evidence. That person approves or rejects before value moves, so material movements carry an accountable sign-off. Routine, within-policy cases clear automatically under the rules you configured.
How are approval-matrix and dual-approval limits enforced?
You configure spend limits, transaction-type rules and approval thresholds as policy-as-code with guided validation. These are enforced as mandatory controls, not advisory hints: a release cannot exceed a limit you set. The aim is that routine within-policy cases clear without a manual bottleneck, while material movements still require the sign-off your approval matrix demands.
What happens to held value if a condition is never met, or a case is contested?
Value held pending release is treated as segregated. If fulfilment conditions are not met, the release does not fire. Contested cases are adjudicated by an accountable human governor, and every step is recorded in a tamper-evident audit trail suitable for dispute resolution and compliance review.
Can a release fire on a timeout rather than on delivery?
No. Release is conditioned on validated fulfilment evidence rather than on an elapsed clock or a mechanical notice. Delivery artefacts and oracle confirmations are ingested and validated so that release fires on proof of fulfilment.
Review the perimeter and controls with us.
If you are assessing Fideleo as a settlement counterparty, we will walk through the intended regulatory perimeter, the segregation and identity controls at release, and the human approval gates — including where confirmation is still pending.