Legal Checklist Before Providing a Financial Service in New Zealand

Offering a financial service in New Zealand can look straightforward at first, especially if you already have a product, platform or customer base ready to go. The trouble is that founders often move too fast on the legal side. Common mistakes include assuming a business model is not a regulated financial service when it actually is, relying on a provider's standard terms without a proper contract review for risk allocation, and collecting sensitive customer information without the right privacy processes in place.

If you are working out what to do before providing a financial service, the key issue is not just whether you can operate, but how you should structure the service, documents and compliance from day one. The right legal checklist helps you spot whether registration or licensing rules apply, what your customer contracts need to say, and where misleading marketing or poor disclosure can create problems later. Here’s what to sort out before you sign, before you onboard clients, and before you rely on verbal assurances from providers or partners.

Overview

New Zealand financial services are regulated based on what you actually do, not just what you call the business. A founder who handles client money, gives financial advice, arranges payment products, or operates an investment-related platform may trigger specific registration, disclosure and conduct obligations.

• Confirm whether your activity is a regulated financial service in New Zealand.
• Check whether you need to be registered on the Financial Service Providers Register or hold a licence.
• Review your customer terms, disclosures, privacy processes and complaint handling framework.
• Make sure your advertising and sales language complies with fair trading rules.
• Check your agreements with technology providers, referral partners, introducers and outsourced service providers.
• Assess how client funds, client data and operational risk will be handled in practice.

What Before Providing a Financial Service Means For New Zealand Businesses

Before providing a financial service means checking the legal character of your business model before you commit to documents, marketing or customer promises. The label you use is far less important than the substance of the service.

For some businesses, the position is obvious. If you are offering financial advice, facilitating investments, issuing payment facilities, managing money for clients, or providing certain credit-related services, you may be in regulated territory. For others, the answer is less clear. A software platform, marketplace, subscription product or consulting service can drift into financial services regulation depending on how it operates and what customers are told.

Why the definition matters

The main risk is treating a regulated activity like an ordinary service business. That can lead to the wrong contracts, the wrong onboarding process, missing disclosures, or failure to register or obtain a licence where required.

New Zealand businesses often assume that if they outsource part of the service to a bank, payment provider or licensed operator, they do not need to check the rules themselves. That is not always right. Your own role, representations and control over the customer relationship still matter.

Examples of founder moments where this comes up

The issue usually appears in practical situations, such as when a founder is about to sign with a payment partner, white label another provider's financial product, or onboard the first business customers to a platform that handles money-related functions.

• A fintech wants to offer stored-value or wallet features to users.
• A business plans to introduce customers to lenders and gets paid per successful referral.
• A platform wants to pool, hold or transfer funds between users.
• An advisory business starts giving recommendations that may amount to regulated financial advice.
• A software provider adds account aggregation, payments or investment functionality to its product.

Registration and licence-style questions

Some financial service providers in New Zealand must be registered on the Financial Service Providers Register. Depending on the service, licensing requirements may also apply. Whether registration alone is enough, or whether a separate licence or authorisation is needed, depends on the nature of the activity and who the customers are.

This is where founders often get caught. They assume registration is a general business formality, when in reality it can be part of a wider compliance framework. Registration also does not remove the need for proper contracts, fair dealing, internal processes and accurate disclosures.

Business structure and operating model still matter

The way you structure the business can affect risk, contracting and compliance. If a company in your group contracts with customers, another entity provides technology, and a third entity receives referral fees, that split needs to be deliberate and documented.

Before you spend money on setup or sign commercial terms, think about:

• which entity is actually providing the financial service;
• which entity owns the customer relationship and brand;
• who handles client money or payment flows;
• who is responsible for compliance, complaints and record keeping;
• whether external providers are regulated and what they take responsibility for.

These points affect your contracts and your exposure if something goes wrong.

Legal Issues To Check Before You Sign

The best time to fix legal gaps is before you sign a contract, before you accept the provider's standard terms, and before you onboard your first customers. Once the service is live, changing disclosures, customer terms or provider arrangements is harder and more expensive.

1. Are you actually providing a financial service?

Start with the substance of your offer. What are you promising customers, what actions are you taking for them, and where does money, advice or investment activity sit in the process?

If your service touches regulated activities, get clear on what legal category applies. A business that simply provides back-end software may sit outside the main regulated role. A business that markets, controls, recommends, arranges or handles the service directly may not.

Before you rely on a verbal promise from a provider that “their licence covers everything”, test that carefully against the actual operating model and contract wording.

2. Do you need registration, licensing or formal compliance systems?

Many founders focus on the headline question of whether they need to register. The more useful question is broader: what formal obligations attach to this service, and who is accountable for them?

Depending on the service, key compliance items may include:

• registration as a financial service provider;
• holding or operating under a relevant licence;
• meeting conduct, disclosure or client care obligations;
• having a dispute resolution process where required;
• keeping records that support customer communications and decisions.

If your business model is changing quickly, revisit this analysis before each expansion. Adding a new feature can change the regulatory position.

3. Customer contracts and disclosures

Your customer terms need to match the actual service. Generic terms copied from a SaaS template or consultant agreement are usually not enough for a financial service.

At a minimum, your customer documents should deal clearly with:

• what the service includes and what it does not include;
• fees, charges, payment timing and refund position;
• your role, and any third-party provider's role;
• how instructions are given and when transactions are treated as authorised;
• risk warnings and any limits on reliance;
• complaints handling and support process;
• liability clauses, indemnities and suspension or termination rights.

The drafting needs to reflect real customer behaviour. If users will act through an app, delegate access internally, or rely on notifications and dashboards, the terms should address that directly.

4. Fair trading and marketing claims

Marketing for financial services needs special care because customers often make decisions quickly based on claims about ease, returns, speed, cost or safety. If the wording overreaches, the business can face problems even before a customer contract is signed.

Check your website, pitch deck, onboarding screens, sales scripts and social media for claims such as:

• “guaranteed” outcomes or savings;
• suggestions that your product is government approved when it is not;
• statements that imply no risk, no fees or instant access in all cases;
• unclear comparisons with banks, advisers or other providers;
• promises about suitability for all users or businesses.

Under fair trading rules, the overall impression matters, not just the fine print. Disclaimers do not always fix a misleading headline claim.

5. Privacy and data handling

Financial services commonly involve sensitive personal and business information. If you are collecting identity documents, bank account details, transaction history, financial profiles or customer verification materials, your privacy notice and internal processes need close attention.

Before you launch online or onboard customers, check:

• what personal information you collect and why;
• how you notify people about collection and use;
• where data is stored, including any overseas hosting or support providers;
• who can access customer information inside your business;
• how long records are retained and how they are securely deleted.

A privacy policy alone is not enough if your day-to-day practices do not match it.

6. Outsourcing and third-party provider contracts

Most new financial services rely on external providers for payments, identity checks, cloud hosting, fraud tools, banking rails, white label products or customer support. The legal risk often sits in the provider contract.

Before you accept the provider's standard terms, review issues such as:

• service levels and outage responsibility;
• rights to suspend or terminate on short notice;
• liability caps that leave your business exposed to customer claims;
• ownership and use of customer data;
• audit, reporting and compliance cooperation;
• who deals with regulatory requests or complaints;
• whether you can migrate customer data and transition away from the provider.

This matters even more where the provider is customer-facing or where your service depends entirely on their licensed infrastructure.

7. Complaints, records and internal governance

A financial service should not rely on ad hoc inbox management and informal Slack decisions. If customers dispute a transaction, challenge advice, or complain about an outage, you need records and a defined process.

Put basic governance in place before you sign major customer deals. That usually includes decision-making authority, approval steps for marketing and disclosure changes, complaint escalation, incident handling and document retention.

Common Mistakes With Before Providing a Financial Service

The most common mistakes happen when businesses treat financial services like ordinary digital products or general consulting arrangements. That approach usually misses regulation, disclosure and risk allocation.

Assuming a technology layer is not a financial service

Founders often say, “We are just the platform.” Sometimes that is correct, but sometimes the platform controls key parts of the user experience, presents recommendations, handles money flows, or holds itself out as the provider. Those details can change the legal analysis.

If your brand is front and centre and customers rely on your promises, your legal position may be more involved than a pure software vendor.

Using generic contracts

Another common error is using standard website terms, a generic services agreement or a short proposal letter for a regulated or high-risk financial offering. That leaves gaps around authority, instructions, risk warnings, provider responsibility, customer suitability and complaints.

It also makes disputes harder to manage because the documents do not match what was actually sold.

Relying on a partner's licence or assurances without checking the detail

White labelling and embedded finance arrangements can look simple in a sales call. The legal detail is rarely simple. A regulated partner may cover some parts of the service, but not your marketing, onboarding or customer communications.

Before you sign, pin down exactly:

• who is the provider of record;
• whose terms govern the customer relationship;
• whose disclosures are shown to customers;
• who handles complaints and remediation;
• who takes responsibility if the service is interrupted or misdescribed.

Overpromising in marketing or sales conversations

Financial services are particularly sensitive to sales language. A founder may casually describe a feature as “safe”, “guaranteed”, “fully compliant” or “approved”, without meaning to overstate anything. Those words can still create legal risk.

Train anyone who speaks to customers to stay within approved wording. A strong contract helps, but it will not always undo a misleading sales representation.

Ignoring privacy and security until after onboarding begins

Many businesses only think about privacy once customers start asking hard questions about data location, access and security. At that point, the product and workflows may already be built in a way that is hard to change.

Sort this out before you collect sensitive information. It is much easier to design proper data handling early than to retrofit it later.

Missing the practical side of compliance

Some founders get legal advice on the headline structure but do not implement day-to-day processes. The service then operates in a way that drifts away from the documented position.

Common operational gaps include:

• customer support teams using unapproved language;
• outdated disclosure documents staying live online;
• no clear process for transaction disputes or complaints;
• sales staff promising functionality that the provider contract does not support;
• poor records of customer consent or instructions.

The legal framework only works if the business follows it in practice.

FAQs

Do all financial service businesses in New Zealand need a licence?

No. Some businesses may need registration, some may need a licence, and some may need both depending on the activity. The answer turns on what service is being provided and how the business interacts with customers.

Can I rely on a white label provider's documents?

Not automatically. You still need to check whether the provider's terms, disclosures and compliance settings actually fit your business model, branding and customer journey.

What should I review before I sign with a payments or fintech provider?

Look closely at liability, service levels, suspension rights, data use, complaints handling, compliance cooperation and who is responsible to the customer if something goes wrong.

Do privacy rules matter if I only serve business customers?

Yes. If you collect personal information about directors, sole traders, staff, authorised users or end customers, privacy obligations can still apply. Business-to-business does not remove privacy risk.

Is a disclaimer enough to protect me from misleading statements?

No. If the overall impression of your advertising or sales message is misleading, a disclaimer may not solve the problem. The main claim itself needs to be accurate and balanced.

Key Takeaways

• Before providing a financial service in New Zealand, first confirm whether your actual activities fall within a regulated financial services category.
• Check whether registration, licensing, disclosure, dispute resolution or other formal compliance obligations apply to your model.
• Make sure your customer contracts match the real service, especially around fees, authority, risk, complaints and third-party provider roles.
• Review marketing carefully so you do not overstate outcomes, approvals, safety or suitability.
• Put privacy, data handling, records and internal complaint processes in place before onboarding customers.
• Do not accept a provider's standard terms or verbal assurances without testing who carries responsibility when things go wrong.

If you want help with customer contracts, provider agreements, privacy compliance, and regulatory position checks, you can reach us on 0800 002 184 or team@sprintlaw.co.nz for a free, no-obligations chat.