FCA Crypto Customer Asset Safeguarding: Contracts, Segregation and Reconciliation

By CRYPTOVERSE Legal Consultancy

A crypto custody firm checks its wallets on Monday morning. The assets are there, its security systems report no incident and withdrawals appear to be functioning normally.

But the finance team finds a discrepancy: customer records show more tokens than the firm can account for.

The operations team believes a transfer is still pending. The technology team suspects a duplicated deposit entry. Nobody has yet established the cause.

The immediate question is not simply whether the wallets are secure. It is whether the firm can establish what each customer is entitled to, identify the assets supporting those entitlements and resolve the difference.

Effective cryptoasset safeguarding connects legal rights, asset segregation, reliable records and reconciliation. Strong wallet security is one component of that framework.

Establish which safeguarding requirements apply

The expanded UK regime includes safeguarding qualifying cryptoassets and relevant specified investment cryptoassets, together with arranging safeguarding. The perimeter assessment considers the firm’s actual control and role if you need a UK Crypto Licence.

Begin by identifying:

• The assets supported.
• The contracting entity.
• Who can initiate or approve transfers.
• Recovery and administrative powers.
• The role of third-party providers.
• Whether the firm safeguards or arranges safeguarding.

The applicable customer asset rules also require classification. CASS 17 addresses qualifying cryptoasset safeguarding, while relevant specified investment cryptoassets and associated client money require assessment under the relevant CASS provisions. 

Do not apply one custody checklist indiscriminately to every token and cash balance.

Start with what the customer is legally entitled to

For UK Crypto FCA Staking authorisation a customer-facing balance should reflect an identifiable legal arrangement.

Review the customer contract alongside the custody architecture. Establish:

• What service the firm promises.
• Which entity owes the obligation.
• Whether assets are held for the customer.
• How instructions are authorised.
• How fees are charged.
• What happens during an incident or withdrawal delay.
• How assets will be returned when the relationship ends.

These are suggested review questions, rather than an exhaustive statement of contractual requirements.

Avoid terms that describe segregated custody while operational arrangements permit unrestricted use of customer assets. Equally, a clause stating that assets “belong to customers” needs a legal and operational framework supporting that statement.

Understand the trust framework and its exceptions

The final CASS 17 framework contains trust requirements and specified exceptions. Where a trust is required, CASS 17.3.14R requires its creation and operation in accordance with applicable UK Crypto lending FCA yield regulation trust law, with clearly documented terms.

This calls for more than inserting the word “trust” into customer terms.

A useful legal review should identify:

• The assets and entitlements covered.
• The trustee and beneficiaries.
• How the trust is constituted.
• The relationship between trust documents and customer terms.
• How assets enter and leave the arrangement.
• Whether any exception is relied upon and why.

Document the analysis before implementation. Exceptions should be applied to their actual conditions rather than treated as general permission to avoid customer asset protections.

Segregation requires a workable asset map

Segregation should be considered through the applicable legal requirements and actual wallet arrangements.

Prepare a register identifying:

The question is whether the arrangement satisfies the relevant rules and permits reliable identification of entitlements—not simply whether each customer has a separate address.

The final trust framework addresses segregation objectives under CASS 17.3.17R. Omnibus arrangements require assessment against those objectives and the supporting recordkeeping requirements.

Separate the customer entitlement from the asset resource

A custody firm needs to establish both:

1. What it is required to safeguard for customers.
2. What it actually safeguards.

CASS 17.5.2R–17.5.4R address records and systems enabling those distinctions and the identification of discrepancies.

For practical preparation, distinguish:

• Customer entitlement records.
• Wallet and custody-provider balances.
• Pending movements.
• Fees and adjustments.
• Relevant trust and asset classifications.

A wallet balance alone cannot allocate every customer’s rights. An internal ledger alone cannot establish that supporting assets are present.

In our scenario, the firm should investigate the difference between the customer records and asset resource before concluding that a pending transfer explains it.

Reconciliation is a decision process, not a dashboard

Under CASS 17.5.10R, relevant client cryptoasset reconciliations must occur at least each business day. The rules also address discrepancy investigation, shortfalls and records, including discrepancies identified outside scheduled reconciliation.

A practical process should explain:

• Which data is compared.
• The applicable cut-off and treatment of pending transactions.
• Who reviews the result.
• How differences are classified.
• Who investigates and escalates them.
• How remediation is verified.

A green dashboard is only useful if management understands what it checks.

Test whether deposits, withdrawals, network fees and corrections are reflected consistently across the systems supplying the reconciliation.

Investigate discrepancies without rewriting the evidence

Returning to our hypothetical firm, the team discovers that a retry mechanism created a duplicate credit in the customer ledger.

The appropriate response needs an accurate investigation and controlled correction.

A suggested incident record includes:

• When the difference was detected.
• Affected assets and customers.
• The evidence examined.
• The cause or current uncertainty.
• Actions taken.
• Approvals and communications.
• Verification of resolution.
• Preventive changes.

Distinguish an accounting error, timing difference and actual asset shortfall. Each requires an evidenced conclusion.

Avoid altering historical records to make the discrepancy disappear. Preserve the original entry and the correction trail.

Third-party custody needs dependable information

Appointing a specialist custodian can support the operating model, but the applicant must understand its own role and dependencies.

Assess the arrangement against the relevant outsourcing requirements and its continuing responsibilities. The crypto framework includes provisions concerning third-party safeguarding arrangements. 

Suggested preparation questions include:

• What assets does the provider acknowledge holding?
• How are customer and firm holdings identified?
• When are records available?
• How are discrepancies escalated?
• Who authorises transfers?
• What happens during provider failure?
• Can the firm obtain records needed for recovery?

Provider statements should be integrated into the reconciliation process, with clear treatment of unavailable or inconsistent information.

Demonstrate security and recovery controls together

Legal arrangements and reconciliation need reliable technical controls.

A suggested evidence pack should cover:

• Key and access management.
• Transaction approvals.
• Administrative privileges.
• Recovery procedures.
• Staff access removal.
• Monitoring and incident response.
• System changes affecting records.
• Testing results and unresolved issues.

Review how recovery works when an approver is unavailable or an account is compromised.

The FCA’s safeguarding perimeter guidance recognises that control can arise through different technical means. 

Describe the capabilities of the actual system, including powers that are rarely exercised. A marketing description such as “non-custodial technology” should not substitute for that analysis.

Prepare for asset return before a failure occurs

Run a practical exercise asking how customers would recover their assets if the service stopped for virtual assets custoder services.

Suggested questions include:

• Can customer entitlements be extracted accurately?
• Are records accessible if a provider becomes unavailable?
• Who can authorise necessary transfers?
• What legal documents support the process?
• How will disputed balances be handled?
• What resources are available?
• What communications will customers receive?

This is recommended operational preparation, not a guarantee of a particular insolvency outcome.

Safeguarding arrangements should also be described accurately to customers. FCA authorisation should not be presented as eliminating loss or guaranteeing compensation; the relevant redress and compensation position requires separate assessment.

What should the application evidence show?

A suggested safeguarding preparation pack brings the legal and operational arrangements together:

For our hypothetical firm, readiness means correcting the duplicate-credit problem, verifying affected balances and improving the process that allowed it.

The application can then describe an evidenced safeguarding framework rather than relying on the absence of a security incident.

Building your safeguarding framework with CRYPTOVERSE

CRYPTOVERSE is a specialist legal and regulatory firm for UK FCA cryptoasset authorisation support.

CRYPTOVERSE can support custody perimeter assessments, customer and trust documentation, safeguarding governance and application evidence preparation.

Preparing a UK crypto custody service? Contact CRYPTOVERSE to assess how your contracts, asset arrangements and reconciliation controls fit together.

FAQs