Opens in a new tab

    ASIC CP 392 Explained: Licensing, Custody and Capital Requirements for Digital Asset Platforms

  • At Ante
  • Neque Sodales
  • Excepteur

1. Overview and Status

1.1 The Corporations Amendment (Digital Assets Framework) Act 2026 (DAF Act) passed on 1 April 2026, received Royal Assent on 8 April 2026 and commences on 8 April 2027. It creates two (2) new financial products: digital asset platforms (DAPs) and tokenised custody platforms (TCPs).

1.2 Consultation Paper 392 (CP 392) is ASIC’s implementation package. It is not itself new law. It comprises draft Regulatory Guide 000 (draft RG 000) and three (3) draft legislative instruments covering asset-holding standards, transactional and settlement standards and financial requirements. ASIC states that the drafts are illustrative and may change considerably, and several elements depend on regulations still being settled by Government.

1.3 ASIC’s stated approach is principles-based and technology neutral, applying “same activity, same risk, same regulatory outcome”. The DAP and TCP regime is modelled on the existing investor directed portfolio service (IDPS), registered scheme and managed discretionary account custody frameworks.

2. Key Dates

Date Milestone
15 October 2026 CP 392 released
27 November 2026 Submissions close (fintech@asic.gov.au)
November 2026 to March 2027 ASIC reviews feedback and finalises instruments; further consultation possible
March 2027 Final instruments and guidance published
8 April 2027 DAF Act commences; applications for DAP and TCP authorisations open
7 October 2027 Transition window closes. Existing operators that lodge a new application or variation by this date may continue operating until ASIC decides the application

2.1 ASIC is also considering publishing a list of firms that have lodged an application or variation by 7 October 2027, so that consumers can identify who may continue operating during the transition.

3. The New Products and the Regulatory Perimeter

Definitions

3.1 DAP (s761GC) the operator possesses one or more digital tokens for or on behalf of a client or the client’s nominee, whether as trustee, as bailee or under an obligation to deal with the tokens on the client’s instructions. Merely possessing tokens is not enough; they must be possessed for the client.

3.2 TCP (s761GD) the operator identifies and holds one or more underlying assets (any asset other than money) for another person and creates a single digital token for each underlying asset, possession of which gives a right to redeem the asset or direct its delivery.

3.3 Digital token and possession (s761GB and s86) a digital token is an electronic record that a person can factually control, meaning they can transfer it, exclude others from transferring it and demonstrate both. The test turns on factual capability, not legal rights. A person does not jointly possess a token if they need another person’s express cooperation and that other person can act alone.

Interaction with other regimes

(a) DAP and TCP overlap a facility meeting both definitions is treated as a TCP (s761GC(4)).

(b) Managed investment schemes if a facility also meets the scheme definition, the scheme regime prevails unless the new s9 exclusions in paragraphs (mc) and (md) apply. These require that:

(i) clients have a right to redeem or direct delivery of the underlying assets;

(ii) the operator acts only on client instructions when acquiring, disposing of or using those assets; and

(iii) the operator cannot materially negotiate or determine clients’ rights.

(c) For TCPs, the exclusion also requires the underlying assets to be of the same class and limits divisibility to what can reasonably be delivered. A “native” tokenised unit trust will generally be a managed investment scheme rather than a TCP.

(d) Financial markets and clearing and settlement (CS) facilities where the underlying tokens are financial products and the market or CS facility definition is met, that regime prevails over the DAP regime. The Minister can declare in either direction (s767B, s767C, s768B and s768C).

(e) Custodial staking staking offered by a licensed DAP or TCP operator is not a separate managed investment scheme or financial product (s9F and s765A(1)(pa) to (pb)).

(f) Anti-avoidance the operator is taken to do whatever its agents and sub-agents do (s761GE). A platform with trading functionality cannot avoid being a DAP by outsourcing custody.

(g) Exclusions title-transfer lending or collateral arrangements and pure technology or multi-party computation providers are not DAPs (the latter under the anticipated regulations).

3.4 The platform is a financial product separate from the tokens held through it. Licensing obligations may therefore apply to the platform even where none of the underlying tokens is a financial product, and additional obligations apply where an underlying token is itself a financial product.

4. Licensing and Authorisations

4.1 An existing AFS licence does not automatically cover operating a DAP or TCP. Existing licensees, including those already authorised to deal in digital assets that are financial products following INFO 225, will need a variation to add the relevant issue authorisation.

New “issue” authorisations (draft RG 000, Table 4)

Business model Description
Custody-only DAP Possesses tokens and records client interests, without execution, matching or settlement. Ancillary staking or lending permitted
DAP as agent Executes client instructions through another DAP, trading venue or liquidity source
DAP as principal Trades with clients as counterparty, including matched principal trading and market making
DAP as trading venue provider Operates the venue on which buyers and sellers interact, without acting as counterparty
TCP Holds an underlying asset and issues a token conferring redemption or delivery rights

4.2 A DAP operating more than one business model may need more than one issue authorisation.

Additional authorisations (draft RG 000, Table 5)

(a) dealing by “using” a DAP or TCP on behalf of another person, a new limb of dealing (s766C(1)(ca));

(b) arranging for another person to deal in a DAP or TCP;

(c) general or personal financial product advice about a DAP or TCP; and

(d) the relevant dealing, market-making or advice authorisations for any underlying asset that is itself a financial product.

4.3 A custodial or depository service authorisation is not required for digital assets that are financial products held through a DAP or TCP (s766E(3)(cb) and (cc)).

Structural limits

(a) No CAR route to issue a person cannot rely on a corporate authorised representative (CAR) appointment to issue a DAP or TCP. The issuer must hold its own appropriately authorised AFS licence unless an exemption applies. Representatives may still provide other services, such as advice or arranging, within their licensee’s authorisations.

(b) No authorised intermediary route the s911A(2)(b) exemption does not apply to the issue of a DAP or TCP, except where the intermediary is a related body corporate.

Licensing exemptions (draft RG 000, Table 3)

(a) low-value DAP (client-value, transaction-value, financial-product and notification conditions);

(b) limited advice and arranging, where these services are not a significant part of the business;

(c) sub-custodian for an appropriately authorised operator;

(d) overseas issuer and client;

(e) overseas related body corporate or joint venture; and

(f) nominee company.

4.4 Each exemption has conditions that require careful assessment. An exemption removes the licensing requirement but does not stop the facility being a DAP or TCP.

Responsible managers

4.5 Responsible managers should have relevant product experience, an understanding of the technology and an understanding of AFS licensee obligations. For Option 5 of RG 105, ASIC may consider relevant experience over the past ten (10) years gained in regulated or unregulated activities, including operating a platform, custody, dealing, market making, operating a market and managing the relevant technology.

5. Operator-Specific Obligations

(a) DAP/TCP Guide a new disclosure document that must be given to retail clients before the platform is issued. It may be combined with the Financial Services Guide. It does not displace a Product Disclosure Statement for underlying financial products. ASIC proposes extending its electronic disclosure relief (Instrument 2025/447) to the Guide.

(b) Target market determination required for the platform where a DAP/TCP Guide is required.

(c) Voting policy required for platforms issued to retail clients (s1020AP to s1020AQ).

(d) Platform rules (s912BC and s912BG) the rules operate as a contract between the operator and each client, and between clients where they can deal with one another. The standards prevail over inconsistent rules, and rights under the rules are not stayed on external administration.

(e) Hawking the s992AB exemption is limited to specified equitable rights or interests arising from holding financial products through the platform. It is not a general exemption for the platform itself.

6. Asset-Holding Standards (Attachment 2)

6.1 The asset-holding standards are made under s912BE and apply to all DAP and TCP operators. Key requirements are summarised below.

Holding arrangements

(a) Underlying assets must be held on trust, under Division 3 of Part 7.8, or under another arrangement that is legally effective and provides “reasonably effective protection” if the operator or a custodian becomes insolvent (for example, bailment).

(b) Other client money must be held under Division 2 of Part 7.8 or, where that Division does not apply, on trust under an arrangement governed by Australian law.

(c) Part 7.8 operates concurrently with the standards. ASIC does not propose broad Part 7.8 relief, but is considering guidance on mixed or unidentified money and on debanking.

(d) Before first holding assets, the operator must publish and give clients disclosure of each holding arrangement, including proprietary versus contractual rights, insolvency consequences and material risks.

(e) Where foreign law governs or materially affects an arrangement, the operator must record a legal assessment of its effect, including on insolvency.

Segregation, pooling and reconciliation

(a) Client assets and money must be segregated from the operator’s and any custodian’s own property.

(b) Omnibus wallets and pooled accounts are permitted if supported by a written policy (reviewed at least every thirteen (13) months), client-level records and reconciliation each business day, or less frequently where that is ordinary commercial practice for the asset.

(c) Any shortfall must be corrected by the end of the second business day after it arises.

Instructions, withdrawals and use of assets

(a) Instructions must be verified as properly authorised before being acted on, and records kept.

(b) Terms that restrict withdrawal rights are permitted only where necessary for legal compliance, or reasonably necessary to manage fraud, operational error, cyber, sanctions, AML/CTF or other financial crime risk. Withdrawal fees are limited to cost recovery, and any delay, suspension or refusal must be reasoned, recorded and notified.

(c) Using client assets (for example, staking or lending) requires written disclosure and express client authorisation. Participation cannot be a condition of holding an account, clients must have an opt-out mechanism that does not require a withdrawal, and the operator must indemnify clients for losses caused by negligence or unauthorised use.

Wallets and token identifiers

(a) Operators must keep records of wallet structures and addresses and report them to ASIC quarterly, within ten (10) business days of quarter-end, as well as notifying material changes. Private keys and seed phrases are expressly excluded.

(b) Each class of token must have a unique digital token identifier (ISO 24165 where practicable), and the list of supported classes must be published.

Third-party custodians

(a) The operator remains responsible for compliance by its custodians and sub-custodians.

(b) It must carry out due diligence before appointment, monitor ongoing, and review its arrangements at least every thirteen (13) months. ASIC may direct an independent report.

(c) The custody agreement must contain extensive prescribed terms, including instructions, reconciliation, audit and ASIC access, incident notification, business continuity, suspension and termination rights, orderly transfer-out, no encumbrances securing the custodian’s own fees, and an annual compliance statement.

Other

(a) Domestic custody is not required. ASIC seeks views on emergency fallback arrangements, such as local key access.

(b) Material changes to platform rules require twenty-eight (28) days’ notice.

(c) Records must be kept for seven (7) years and remain accessible on insolvency.

7. Transactional and Settlement Standards (Attachment 3)

7.1 The transactional and settlement standards are made under s912BF and apply to DAP operators where clients can buy or sell through the platform. They do not apply to custody-only DAPs or to most TCP activity, and transactions in tokenised tangible property and s761D(3)(a) physically settled derivatives are carved out. Compliance is a core obligation for breach reporting purposes.

Governance and conduct

(a) Records must be kept for seven (7) years, timestamped at each stage of processing.

(b) Each order must identify its execution method.

(c) A trade confirmation is required for each executed order, naming any liquidity support provider counterparty.

(d) Operators need an asset admission and monitoring framework. Delisting decisions must be published and notified, with trading continued for seven (7) days where reasonably practicable.

(e) Operators need conflicts arrangements for tokens created by, or held by, the operator or a related body corporate.

(f) No shelf-space fees operators may not accept benefits for preferencing a token, except payments covering reasonable costs.

Principal trading

7.2 The operator and its related bodies corporate must not trade as principal on the operator’s own or group DAPs. This is not a blanket prohibition on principal business models. The exceptions cover:

(a) orders executed as agent for the client;

(b) orders the client has instructed be executed with the operator as principal counterparty (the OTC model); and

(c) matched principal trades where neither side is the operator or a related body corporate.

7.3 Tied broker and tied dealer models, which route to a named related facility, are expressly accommodated.

Misconduct, intervention and liquidity providers

(a) Platform rules must prohibit conduct that interferes with platform integrity. The operator must hold intervention rights (restrict, suspend, cancel, reverse) and publish how they are used.

(b) The operator must notify ASIC whenever it suspends or terminates a client for misconduct.

(c) Every liquidity or market-making provider needs an enforceable written agreement. The operator must monitor the provider’s performance and retain assistance and intervention rights, and the provider’s identity must be publicly disclosed.

Order matching and settlement

(a) Order-matching DAPs must operate in a fair, orderly and transparent manner, with non-discretionary, time-priority matching and sufficient resources.

(b) Settlement arrangements must be fair and effective and published, covering settlement failure, finality and timing.

(c) Pre-trade transparency (for order books), post-trade transparency and trading information must be made available free of charge and, for pre-trade and post-trade data, in real time.

Best execution

7.4 For execution other than by order matching, operators must take reasonable steps to obtain the best outcome, execute comparable orders sequentially and maintain access to at least two (2) liquidity sources. Exemptions, each with prescribed disclosure, apply for:

(a) specific client instructions, valid for up to twelve (12) months and not to be induced;

(b) tied brokers and tied dealers; and

(c) orders the client instructs be executed with the operator as principal counterparty.

8. Financial Requirements (Attachment 4)

All licensees providing DAP or TCP services

(a) solvency and positive net assets;

(b) $50,000 in surplus liquid funds (SLF) where the licensee holds more than $100,000 in client money; and

(c) adjusted SLF where the licensee transacts with clients as principal: $50,000, plus 5% of adjusted liabilities between $1 million and $100 million, plus 0.5% of adjusted liabilities above $100 million.

Additional requirements for operators

(a) cash flow projections covering at least twelve (12) months, approved by the directors at least quarterly, with documented assumptions;

(b) cash or cash equivalents of at least the greater of $200,000 and 50% of required net tangible assets (NTA);

(c) liquid assets of at least 100% of required NTA, excluding money held under s981B;

(d) an audit opinion covering the cash flow and NTA requirements;

(e) CPI indexation of thresholds from 1 July 2027; and

(f) all guarantees included in full in adjusted liabilities.

NTA: three alternative models under consultation

Model Third-party custody concession Self-custody
Model 1
(IDPS mirror)
Greatest of $200,000, 0.5% of average underlying asset value (capped at $7 million) and 10% of average revenue Greater of $14 million and 10% of average revenue
Model 2 As for Model 1 Greater of $7 million and 10% of average revenue if no underlying asset is a financial product; otherwise as for Model 1
Model 3
(scalable)
As for Model 1 Greatest of $2 million, 0.5% of average underlying asset value (capped at $14 million) and 10% of average revenue, plus activity add-ons: agent $500,000, neutral trading venue $750,000 (Attachment 4 states $500,000), principal $1 million

8.1 The models are alternatives, not cumulative. The third-party custody concession requires every underlying asset of every platform to be held by third-party custodians or sub-custodians, written assurances from each custodian within the preceding thirteen (13) months that it meets the equivalent NTA, and supporting audit reports. Engaging a custodian is not enough on its own.

9. Wider Proposals

(a) Restricted stablecoins for all AFS licensees, not only digital asset firms, stablecoins issued by, or possessed by or for, the licensee or its associated or controlled entities cannot count towards NTA. Independently issued stablecoins held by a third-party custodian are not restricted, but must still meet the cash equivalent or liquid asset definitions; eligibility is not automatic.

(b) INFO 225 this information sheet will remain the primary guidance on when digital assets are financial products. It will be updated for public digital token infrastructure and its exemption, wrapped tokens (where the redemption right is disregarded under s765E) and custodial staking arrangements.

10. Practical Implications

(a) Map actual flows labels such as “execution-only”, “brokerage” or “no ongoing custody” do not determine the outcome. The analysis should identify who controls the tokens, on whose behalf, whether the operator acts as agent or principal, and whether any exemption applies. That analysis drives the licence variation, CAR, responsible manager, custody and capital planning.

(b) CAR and intermediary structures these are the most significant structural change. Any business relying on a CAR appointment or another licensee to issue a custodial platform should be re-tested, as it is likely to need its own issue authorisation by 7 October 2027.

(c) Capital under Models 1 and 2, self-custody NTA of $7 million to $14 million effectively pushes smaller operators to qualifying third-party custody. Model 3 is the only model workable for start-ups that self-custody.

(d) Principal and hybrid models the OTC and matched principal models remain available through the client-instructed principal counterparty and matched principal exceptions. However, operators trading for their own account on their own order book, and those relying on informal market-making arrangements, will need restructuring and documented, publicly disclosed liquidity support agreements.

(e) Custody documentation existing custody agreements will need to be re-papered against the prescribed contract terms, and pooled wallet policies and daily reconciliation processes will need to be formalised.

“Digital asset law reform implementation: proposed standards and guidance for digital asset platforms and tokenised custody platforms.”

Disclaimer

This summary is based on the CP 392 consultation package released on 15 October 2026. The standards and guidance are draft proposals and may change following consultation. It is a general summary only and does not constitute legal advice in relation to any particular arrangement.

Sources: