DeFi protocol frontend in New Zealand
Operates a web frontend or aggregator that interacts with permissionless smart contracts on behalf of users. May or may not screen users / restrict regions.
DeFi frontend is conditionally permitted in New Zealand with a local entity, subject to AML obligations and medium licensing burden.
Verdict Details
- Permitted
- conditional
- Local entity required
- Yes
- Licensing burden
- Medium
- Last updated
- 2026-07-13
AML Obligations
- Register as a reporting entity with the Department of Internal Affairs (DIA) under the AML/CFT Act 2009 if the frontend conducts any regulated activity (exchanging, transferring, custody, or financial services related to virtual assets).
- Conduct a comprehensive risk assessment and establish an AML/CFT Programme covering identity verification (CDD/ECDD), ongoing monitoring, sanctions screening, and suspicious activity reporting.
- Verify customer identity: obtain full name, date of birth, address (or for entities: name, legal form, proof of existence). Specific rules for non-face-to-face onboarding under the Identity Verification Code of Practice.
- Beneficial ownership identification for legal entity customers (25%+ ownership/control threshold).
- Enhanced CDD for PEPs, high-risk jurisdictions, complex/unusually large transactions, and complex ownership structures.
- Screen customers and transactions against relevant sanctions lists (e.g., UN Security Council lists).
- Report suspicious transactions or activities to the New Zealand Police Financial Intelligence Unit (FIU) — no tipping off.
- If the frontend offers derivatives (futures, options) or manages client funds in a structured investment product, FSP registration and potentially an FMA Market Services Licence or Financial Advice Provider (FAP) Licence would also be required.
Key Restrictions
- Fee-taking (e.g., swap fees, routing fees) from users is likely to trigger categorization as a 'reporting entity' under the AML/CFT Act (exchanging virtual assets or facilitating such exchanges), requiring DIA registration.
- If the frontend merely provides a non-custodial interface to permissionless protocols and does not take fees, custody user assets, or facilitate the exchange itself, the regulatory classification is ambiguous — DIA or FMA may still assert jurisdiction.
- Any offering of derivatives (futures, options) based on virtual assets would trigger FMA licensing (Market Services Licence or Financial Advice Provider licence).
- No specific minimum capital requirements under AML/CFT Act for DIA-registered reporting entities alone, but FMA-licensed activities carry capital/solvency requirements.
Key Risks
- ["Regulatory ambiguity: DIA and FMA have not published definitive guidance on whether a non-custodial DeFi frontend that merely aggregates/renders protocol data constitutes a 'reporting entity' — enforcement risk exists if regulators take a broad interpretation.", "Enforcement precedent: Dasset (NZD $2.3 million penalty) and Coinstash show aggressive enforcement of AML/CFT obligations against crypto operators in NZ, including for compliance programme failures.", "Individual liability risk: The FMA's action against James Malcolm Allan (individual ban + penalty) shows personal enforcement against unregistered crypto-related activities.", "If the frontend uses a geofence to block NZ users, it may avoid NZ regulatory exposure entirely — but any NZ-resident user access without KYC creates material enforcement risk.", "Liquidation risk: Dasset went into liquidation after its penalty, highlighting the existential threat of compliance failures for smaller operators."]
Evidence
This verdict synthesizes the following facts. Each fact links to its primary source(s).
AML/CFT Registration (DIA): Most crypto businesses, including exchanges, custody providers, and payment processors dealing with VAs, are categorised as "reporting entities" under the AML/CFT Act. This requires them to register with the DIA as a reporting entity and comply with comprehensive AML/CFT obligations. This is not a "license" in the traditional sense of permitting operation, but a mandatory registration for AML/CFT compliance.
Primary Requirement: AML/CFT Reporting Entity Registration (DIA)
Businesses that exchange virtual assets for fiat currency, other virtual assets, or facilitate such exchanges are deemed "reporting entities" under the AML/CFT Act. This includes operating a trading platform.
Businesses that offer safekeeping services for virtual assets on behalf of customers (i.e., holding private keys or managing custodial wallets) are considered "reporting entities" under the AML/CFT Act.
Businesses that transmit money or value using virtual assets, or facilitate payments in VAs, are typically classified as "money or value transfer services" under the AML/CFT Act and must register with the DIA.
Potential Secondary Requirement: FSP Registration/Licensing (FMA)
If the exchange offers derivatives (e.g., futures, options on VAs), manages client funds in a structured investment product, or provides regulated financial advice, then FSP registration and potentially an FMA license (e.g., a Market Services Licence or a Financial Advice Provider (FAP) Licence) would be required.
If the custody service is part of a broader investment scheme (e.g., a managed investment scheme where the provider also makes investment decisions or offers investment products), then FMA licensing would be necessary. Merely providing technical custody without any active management or investment component is less likely to trigger FMA licensing, but full AML/CFT compliance remains critical.
There are no specific minimum capital requirements under the AML/CFT Act for VASPs solely registered as reporting entities.
However, if an FMA license is triggered (e.g., Financial Advice Provider, Market Services Licence), then specific capital and solvency requirements will apply, often based on the nature and scale of the financial services provided. For example, FAPs must demonstrate adequate financial resources.
Anti-Money Laundering and Countering Financing of Terrorism Act 2009: https://www.legislation.govt.nz/act/public/2009/0035/latest/DLM2140700.html
Identity Verification Code of Practice 2013 (or current version): Issued by the supervisors, this code provides practical guidance on how to meet customer identity verification requirements.
Exchange virtual assets for fiat currency (and vice versa).
Exchange one form of virtual asset for another.
Conduct a comprehensive risk assessment: This identifies and assesses the money laundering and terrorism financing risks specific to their business, customers, products, services, delivery channels, and jurisdictions they operate in. Risks associated with the inherent characteristics of virtual assets (e.g., pseudo-anonymity, speed of transfer, global reach) must be specifically addressed.
Establish and maintain an AML/CFT Programme: This is a documented programme that outlines the policies, procedures, and controls the VASP has in place to mitigate the risks identified in their risk assessment. It must include measures to:
Identity Verification: Obtaining and verifying the customer's full name, date of birth, and address using reliable and independent sources (e.g., passport, driver's license, national ID, proof of address utility bills). For legal entities, verifying the entity's name, legal form, proof of existence, registered address, and articles of association.
Face-to-Face vs. Non-Face-to-Face: Specific requirements apply to non-face-to-face onboarding to mitigate higher risks. Technologies like video conferencing or biometric verification can be used if they meet the standards set out in the Identity Verification Code of Practice.
Enhanced CDD (ECDD): Required for higher-risk situations, such as:
Beneficial Ownership: Identifying and verifying the identity of the natural person(s) who ultimately own or control a customer (typically those with more than 25% ownership or control for legal entities).
Ongoing Monitoring: Regularly reviewing transactions and customer information to ensure it is consistent with the VASP's knowledge of the customer, their business, and risk profile. This is crucial for VASPs given the dynamic nature of virtual assets.
Sanctions Screening: Screening customers and transactions against relevant sanctions lists (e.g., UN Security Council sanctions lists).
Obligation to Report: VASPs must report any transaction or activity they suspect is related to money laundering, terrorism financing, or other criminal activity to the New Zealand Police Financial Intelligence Unit (FIU).
No Tipping Off: Reporting entities are prohibited from disclosing to the customer or any third party that a report has been made or that an investigation is underway.
Violation Type: Significant breaches of the Anti-Money Laundering and Countering Financing of Terrorism Act 2009 (AML/CFT Act), including failures in customer due diligence, risk assessments, suspicious transaction reporting, and compliance programme. Penalty Amount: NZD $2.3 million. Outcome: Coinstash admitted to the breaches and agreed to pay the penalty. The DIA noted this was the largest financial penalty issued under the AML/CFT Act for a single infringement notice.
Entity Targeted: Dasset Limited (now in liquidation). Violation Type: Significant breaches of the Anti-Money Laundering and Countering Financing of Terrorism Act 2009 (AML/CFT Act), including failures in customer due diligence, risk assessments, record-keeping, and the overall compliance programme. Penalty Amount: NZD $1 million. Outcome: Dasset admitted to the breaches and agreed to pay the penalty. The company subsequently went into liquidation in October 2023, though the DIA noted the penalty was not the direct cause.
Entity Targeted: James Malcolm Allan (individual). Violation Type: Operating an unregistered financial service provider, making misleading representations about financial products (including crypto-assets), and breaches of the Fair Trading Act 1986 and the Financial Service Providers (Registration and Dispute Resolution) Act 2008. Allan had been promoting investments via social media, purporting to offer high returns from trading shares and crypto-assets. Penalty Amount: Permanent ban from providing financial services and from acting as a director or manager of any financial service provider. A pecuniary penalty of NZD $50,000 was also ordered. Outcome: The FMA successfully obtained orders from the High Court against Allan, resulting in the ban and penalty. This was a significant action against an individual promoting crypto-related investments without proper registration or disclosure.
Verdict Attribution
- Source:
- AI-Generated · Unreviewed
- AI synthesized:
- 2026-07-13 (deepseek-chat)
- Last updated:
- 2026-07-13
- Confidence:
- medium
This verdict was produced by an AI model from the underlying facts. Confirm with counsel before relying on it for material decisions.
Conditional — a DeFi protocol frontend operating in/for NZ residents likely triggers AML/CFT reporting-entity registration with the DIA if it takes fees or facilitates exchanges (even non-custodially), with full CDD/KYC, sanctions screening, and suspicious reporting obligations; the FMA may also assert jurisdiction if derivatives or investment services are offered, but purely informational non-fee-taking frontends face regulatory ambiguity.
Questions this verdict aims to answer
- Is operating the frontend a regulated activity even if the protocol is decentralized?
- What geofencing or KYC obligations apply?
- Does fee-taking change classification?