Enabling crypto-adjacent operations for a client is not a single decision. It is a set of decisions that should be made before the first payment moves, and revisited afterwards. A checklist helps because the risks are cumulative: each item left unexamined weakens the record behind every later operation.

Before the first operation

  • Confirm the licence status of every provider that will execute a digital-asset leg; a supervised party is a pre-condition, not an upgrade.
  • Identify the principal who legally stands behind the operations.
  • Register any agents, and confirm their identities are revocable and never anonymous.
  • Set policy — limits, approved counterparties and approval thresholds — below the model, where an agent cannot argue with it.
  • Confirm the data that must accompany each operation, including information-transfer requirements, and how it will travel.
  • Run sanctions screening and confirm what reliance, if any, applies to another institution's due diligence.
  • Establish the ledger record: double entry, attributed to principal, agent and policy version.
  • Agree who has access to KYC documents on request, and under what conditions.

Ongoing controls

Onboarding is not the finish line. Reliance agreements typically provide for selective audit, limits, suspension and exclusion. Monitoring should look for client-profile mismatches and network anomalies, and over-limit operations should become a human approval request rather than a rejection. Because reliance does not transfer legal responsibility, and cross-border reliance is not permitted everywhere, local-law limits need checking jurisdiction by jurisdiction.

A note on records

The strength of an onboarding file shows up later, during an audit or a query. A ledger that ties every operation to principal, agent and policy version, with signed and verifiable documents and per-unit reporting, turns a difficult question into a short answer.

In short

  • Confirm licence status before a leg can run.
  • Identify the principal; register revocable agents.
  • Set limits, counterparties and thresholds below the model.
  • Confirm information-transfer data and reliance terms.
  • Keep the record complete from the first operation.

This is general information, not legal, tax or financial advice. For the institutional route, see /institutions/