Non-Cash Payment Facilities: Legal Requirements in Australia

If you run a small business or startup in Australia, there’s a good chance you accept payments that never involve physical cash at all. Cards, direct debits, in-app payments, QR code payments, and online checkouts are now standard.

From a legal perspective, these tools aren’t just “how you get paid” - depending on how they’re set up, they can fall into a regulated category known as a non-cash payment facility. If your business is setting up new payment methods, building a platform, launching a marketplace, or even just trying to tighten up risk and compliance, it’s worth understanding what this term means and why it matters.

This guide explains what a non-cash payment facility is in plain English, when it can become a legal issue for your business, and what practical steps you can take to reduce risk as you grow. This article is general information only and isn’t legal advice.

What Is A Non Cash Payment Facility?

A non-cash payment facility is a facility that lets a person make payments (or arrange payments) without using physical cash.

In everyday business terms, it usually covers things like:

• paying by debit or credit card (in-store or online)
• direct debit arrangements
• digital wallets and tokenised payments
• stored value, credits, vouchers and “wallet balances” inside an account
• platform-based payments where you collect money and pass it on to someone else

Where businesses often get caught out is assuming that “using a payment provider” means you’re automatically outside the rules. Sometimes you are. But sometimes the way you structure your checkout, wallet, credits, or settlement process can mean you’re operating (or helping operate) a non-cash payment facility.

That matters because, in Australia, some non-cash payment facility arrangements are regulated under the Corporations Act 2001 (Cth) as a financial product, and dealing in, issuing, or providing advice about that product can amount to providing a financial service. This can trigger obligations such as holding (or operating under) an Australian Financial Services Licence (AFSL), as well as disclosure and conduct requirements. The boundaries can be technical, so getting tailored advice early is important if payments are core to your model.

Why Small Businesses Should Care About Non-Cash Payment Facility Rules

For many businesses, accepting card payments through a standard payment terminal or checkout is straightforward. You’re using a third-party provider, and you’re not creating your own payment system.

But startups and scaling businesses often go a step further. For example, you might:

• build an app that allows users to store funds or credits
• operate a marketplace that collects customer money and pays sellers later
• run a subscription service with recurring billing and plan changes
• offer gift cards, prepaid packages, or customer “top ups”
• introduce in-platform refunds to a wallet rather than back to a card

These commercial decisions can create legal complexity quickly, especially around:

• regulatory risk (could your payment arrangement be a regulated financial product or financial service?)
• contract risk (who is responsible when payments fail or are disputed?)
• cashflow and insolvency risk (who owns funds while you’re holding them, and how are they protected?)
• consumer law risk (how refunds, credits and expiry are handled)
• privacy risk (what data you collect and how you store it)

Even if you’re not a “fintech”, if your product includes payments, you’ll often need to treat payment design as a legal issue - not just a technical one.

Common Business Models That Can Trigger Non-Cash Payment Facility Issues

You don’t need to be a bank to end up with non-cash payment facility considerations. Below are some common scenarios where small businesses and startups should slow down and check the legal position.

1. Marketplaces And Platforms That “Hold” Customer Money

If your platform collects money from a customer and then pays out to a supplier/seller later (for example, weekly or after the job is completed), you may be dealing with customer funds in a way that raises financial services, custody and trust/accountability issues.

Key questions include:

• Are you acting as an agent for the seller, or collecting in your own name?
• When does the seller become entitled to the funds?
• What happens if there’s a chargeback, refund, or dispute?
• Are you allowed to set off fees against the balance?

This is one of the biggest “grey areas” we see for startups, because the payment flow is central to the product - and fixing it later can be expensive.

2. Stored Value, Wallets, Credits And Prepaid Balances

If customers can deposit money into an account, or buy credits that can be redeemed later, that can look and behave like a facility that enables non-cash payments.

Even if you call it “credits”, you’ll want to think carefully about:

• whether credits are refundable (and when)
• whether credits expire
• how credits are valued (e.g. $1 = 1 credit)
• what happens if your business closes

These aren’t just user experience choices - they’re legal risk points. Depending on the structure, stored-value models can also raise financial product and AFSL questions, so it’s worth checking the regulatory position before launch.

3. Direct Debit And Recurring Payments

Subscriptions are great for predictable revenue, but recurring billing is also a common source of customer complaints, chargebacks and disputes.

If you run subscriptions, you’ll want contracts that clearly cover:

• billing cycles and renewal terms
• price changes (and how customers are notified)
• cancellations, cooling-off and refunds
• failed payments and suspension of access

This is also where your website terms and consumer law obligations need to be aligned, especially if you’re selling to consumers.

4. Gift Cards, Vouchers And “Top Up” Packages

Gift cards and prepaid vouchers can feel simple, but they often create tricky issues about:

• expiry dates
• partial redemptions
• refunds for unused balances
• what happens if the underlying product is no longer available

If you’re also advertising discounts or promotions, you’ll want to ensure your marketing and terms don’t create misleading expectations.

Key Legal Areas To Get Right When You Offer Non-Cash Payments

Once payments are part of your product or platform, there are a few legal “pillars” you should aim to cover early. The goal is not to over-lawyer your business - it’s to reduce disputes and avoid building a model that becomes hard to scale or hard to fund.

Australian Consumer Law (ACL): Refunds, Chargebacks And Customer Promises

If you sell goods or services to consumers in Australia, you need to comply with the Australian Consumer Law (ACL). This affects how you describe your product, what you promise in advertising, and how you handle refunds when something goes wrong.

Payments are often where ACL problems show up first, because customers will ask:

• Can I get a refund, and how will it be processed?
• Why did you refund me in “store credit”?
• Why is there a cancellation fee?

Your terms should reflect what you actually do in practice, and your customer support process should follow the terms (and the ACL). The ACL generally focuses on whether a consumer is entitled to a remedy (like a refund, replacement, repair or compensation) rather than prescribing a single mandatory “original payment method” rule in every case, so it’s important your policy and practice are both accurate and fair.

If you’re using deposits, credits, or cancellation fees, it’s worth checking the structure of your cancellation fees approach so it’s commercially workable and legally defensible.

Contract Law: Who Is Responsible For Payment Problems?

When payments fail, customers don’t usually blame a third-party processor - they blame you. That’s why your contracts and terms need to clearly allocate responsibility for:

• failed transactions and double charges
• payment disputes and chargebacks
• refund timing (especially where third parties are involved)
• fraud and unauthorised use
• platform fees and deductions

For online businesses, this usually sits inside your website or platform terms. If you’re running a more complex platform or app, you may need tailored platform terms and a tighter payment clause structure.

Privacy And Data: Payment Data Is Sensitive (Even If You Don’t Store Card Numbers)

Even if you never store card details (because a third-party provider does), you will still likely collect personal information connected to payments - such as names, emails, billing addresses, transaction histories, and sometimes identity verification details.

If you collect personal information, you’ll usually need a Privacy Policy that explains what you collect, why you collect it, and who you share it with (including payment providers).

If your model involves collecting and storing customer details for recurring payments, it’s also worth thinking about your security practices and vendor contracts, because a data breach can become both a legal and reputational problem very quickly.

Direct Debit And Payment Setups: Make Sure Your Process Matches Your Paperwork

Many disputes come down to a mismatch between:

• what your website says
• what your checkout screens say
• what your terms say
• what your team actually does

A practical way to reduce risk is to map the payment journey end-to-end (sign-up, payment authorisation, renewal, failed payment, cancellation, refunds), and then make sure your legal documents and internal processes match the reality.

If You’re Holding Someone Else’s Money, You Need Extra Care

If you operate a platform that holds funds before paying them out (even temporarily), you should treat this as a high-risk area and get legal advice early.

From a commercial perspective, you’ll want clarity on issues like:

• whether funds are held “on trust” or as part of your business funds
• how and when you can deduct fees
• what happens if you have a cashflow issue
• what happens if a supplier doesn’t deliver and the customer wants a refund

This also links to how you document relationships across your platform - for example, whether you need supplier agreements, contractor terms, or other commercial arrangements.

What Legal Documents Should You Have In Place?

There’s no single “perfect set” of legal documents for every business, but if your business touches payments (especially non-cash payments), the documents below are commonly relevant.

• Website Terms & Conditions: sets the rules for using your website or platform, including payment terms, refunds, chargebacks and limitations of liability.
• Customer Contract / Service Agreement: especially important if you provide services, higher-value products, or B2B arrangements where payment timing and milestones matter.
• Privacy Policy: explains your handling of personal information (including transaction-related data) and is often expected by payment providers and customers.
• Supplier / Contractor Agreement: if you rely on third parties to deliver what customers pay for, your upstream contract should align with your downstream promises.
• Platform / Marketplace Terms: if you connect buyers and sellers, these terms should clearly address payment flows, payout timing, disputes, and fees.
• Shareholders Agreement: if you have co-founders or investors, it helps manage decision-making and funding issues (especially when payment risk impacts cashflow). A Shareholders Agreement can be particularly useful if your business is scaling quickly and taking on capital.

If you’re running a company, it’s also worth checking that your internal governance documents fit your growth plans. A solid Company Constitution can be helpful where you’re issuing shares, bringing in investors, or formalising decision-making as you scale.

And if your model involves recurring billing or “set and forget” payments, strong terms can help reduce disputes around late payment fees, suspension, and cancellation. Getting your invoice approach right also matters - including your payment timing and expectations in your invoice payment terms helps customers understand what happens if payments aren’t made on time.

Practical Compliance Tips Before You Launch (Or Before You Scale)

Most payment-related legal problems aren’t caused by bad intentions - they’re caused by moving fast and not documenting the payment model clearly. Here are practical steps you can take now.

Map Your Payment Flow Like A Lawyer (Not Just Like A Developer)

Write down, step-by-step:

• who pays who
• where the funds sit at each stage
• when you deduct fees
• how refunds and disputes work
• what happens if a service isn’t delivered

This makes it much easier to identify whether you’re moving into non-cash payment facility territory, and it makes your terms far easier to draft accurately.

Keep Your Marketing, Checkout And Terms Consistent

If your checkout says “cancel anytime” but your terms impose a cancellation fee, you can end up with complaints and potential ACL issues.

A good habit is to review key checkout screens and key marketing claims alongside your legal terms, especially when you change your product offering.

Be Careful With “Store Credit Only” Refunds

Refunding to store credit can be commercially attractive, but it can also create consumer law risk if you do it in situations where a consumer is entitled to a refund or other remedy under the ACL, or where the consumer hasn’t agreed to credit.

If you want to offer store credit, you should structure it carefully and make sure it’s communicated clearly upfront.

Use The Right Documents When You’re Taking Payments Online

If you sell online, terms matter because customers often never speak to you before they pay. Your website terms essentially become your “contract” with the customer at the point of sale.

If you’re operating a more complex online business model (subscriptions, memberships, SaaS, marketplaces), it’s worth reviewing whether you need more than a generic set of terms, especially around payment mechanics and liabilities.

Don’t Ignore Security And Fraud Risk

Even when you outsource payment processing, your business can still be affected by fraud, account takeovers, or chargeback fraud. Clear contract clauses and internal processes (including record keeping and verification steps) help you respond quickly when disputes arise.

If you’re collecting identification information, storing customer information, or using third-party tools, privacy compliance and data security should be treated as part of your payment compliance program - not an afterthought.

Key Takeaways

• A non-cash payment facility broadly covers arrangements that allow payments without physical cash, and it can become legally significant depending on how your product or platform handles payments.
• Standard card payment acceptance is usually straightforward, but marketplaces, stored value wallets, credits, gift cards, and payout models can create higher regulatory and contractual risk.
• Some non-cash payment facility models may be regulated as financial products and can trigger financial services obligations under the Corporations Act 2001 (Cth) (including potential AFSL and disclosure requirements), so it’s worth getting advice before you launch or scale.
• Australian Consumer Law (ACL) affects how you handle refunds, cancellations, store credit and payment disputes, so your payment practices need to match what you promise customers.
• Strong contracts and platform terms help allocate responsibility for failed payments, chargebacks, fees, refund timing and third-party delivery risk.
• If you collect personal information connected to payments, you’ll likely need a clear Privacy Policy and a practical data-handling approach that matches what you say you do.
• Mapping your end-to-end payment flow early is one of the simplest ways to reduce risk and avoid building a payment model you’ll have to redesign later.

If you’d like a consultation on setting up or reviewing your non-cash payment facility model, platform terms, or payment-related legal documents, you can reach us at 1800 730 617 or team@sprintlaw.com.au for a free, no-obligations chat.