Revenue can look healthy in Stripe or Xero while margin leaks through payment fees, FX, gateway mark-ups and manual reconciliation. The leak rarely arrives as one dramatic bill. It hides in a blended rate, a foreign-issued card, a failed renewal, or a contract nobody has reviewed since launch.

For a New Zealand or Australian SaaS founder, how to reduce transaction costs starts with seeing the whole machine. Payment rails matter, but so do checkout design, pricing, contracts, settlement, fraud controls and the hours your team spends fixing exceptions. The cheapest fee on paper can become expensive if it lowers conversion or creates more support work.

The Moment Transaction Costs Start Biting

The warning usually appears in a quiet finance meeting. Revenue is climbing, headcount is flat, and yet the annualised run-rate feels softer than it should. Then someone asks why cost of revenue keeps rising when the product is mostly software.

A finance lead starts pulling exports. A board member flags the line as a red flag before a raise. Nobody has done anything reckless, but the business has accumulated a payment stack one small decision at a time.

Consider a Wellington SaaS business charging $40,000 in monthly recurring revenue. The leadership team expects payment costs to be a tidy processor line. Instead, the review finds $4,000 of monthly drag spread across gateway charges, interchange, a surcharge revenue share and manual reconciliation hours included in a B2B contract. That scenario is useful because it feels ordinary. The margin problem isn't caused by one bad invoice. It comes from several layers nobody owns.

Practical rule: If you can't explain the cost of a successful payment by customer, channel and rail, you don't yet know your transaction cost.

The Commerce Commission's work puts the scale of the issue in sharper focus. It estimated the annual resource cost of processing card payments in New Zealand at around $950 million, roughly 1.3% of $76 billion in card transactions across the economy (Commerce Commission retail payment systems issues paper). The Commission also reported that interchange made up 60% of merchant service fees in 2024, so payment-method choice can matter far more than trimming a small software subscription.

Four buckets belong on the founder's desk

Separate the leak into four buckets:

  • Payment rails: EFTPOS, domestic debit, domestic credit, international cards, direct debit, bank transfer and alternatives.
  • Operational processing: Failed payments, refunds, chargebacks, reconciliation, support tickets and collection time.
  • Pricing design: Surcharges, minimums, annual commitments, usage bundles and payment timing.
  • Platform surface area: Gateways, acquirers, fraud tools, tax systems, middleware and contract terms.

This is the playbook many founders need at month six, not year three. The problem is structural, not a sign that the team lacks discipline. Once the buckets are visible, the decisions get less emotional and much more practical.

Mapping and Measuring Your Real Transaction Costs

Start with a ledger, not a negotiation. A processor can offer a sharp headline rate while another system collects gateway, FX, fraud and reconciliation costs around it.

Map the full stack

Pull the last useful period of payment data and list every charge tied to collection:

  1. Gateway and acquirer: Include Stripe, Windcave, EziDebit, Adyen or any other provider, plus merchant service fees and settlement charges.
  2. Network costs: Separate scheme fees, interchange and any platform margin.
  3. Customer-facing charges: Record surcharge revenue and any share retained by a provider.
  4. Currency and risk: Isolate FX margin on USD cards, Stripe Radar or Adyen risk charges, refunds and chargebacks.
  5. People time: Estimate the work involved in chasing failed renewals, correcting account details and matching payments in Xero.

That last item gets missed because it doesn't look like a payment fee. It still reduces contribution margin. A useful primer on categorising understanding bank fee expenses can help tidy the accounting side before you start comparing providers.

A six-step infographic guide for mapping, measuring, and reducing operational transaction costs in business processes.

Baseline the unit economics

Use three views rather than one blended percentage:

  • Cost per successful transaction: Useful for low-value subscriptions and frequent orders.
  • Cost per $1,000 processed: Better for comparing customer segments with different ticket sizes.
  • Recovery rate: Track how many declines or 3DS-friction events become successful collections.

Then attribute the result. Domestic EFTPOS, Visa Debit, Mastercard Debit, domestic credit and foreign-issued cards shouldn't sit in one bucket. The Commerce Commission's 2024 consultation material warns that interchange and scheme fees vary by card type, processing environment and network, so a blended rate can hide expensive segments (Commerce Commission card-payment costs consultation).

Monitor the leaks weekly

Build a dashboard with cost per transaction, decline rate, settlement time, FX drag and net collected amount. Add customer, country, channel and rail as dimensions.

The export most founders never build is a per-customer, per-rail fee breakdown. Create it from Stripe or your gateway export, join it to Xero or your billing system, and inspect customers whose payment behaviour changes the margin. A high-volume customer paying by an expensive rail can matter more than dozens of smaller accounts.

The Payment-Rail Economics Most Founders Miss

A payment fee has three main layers. Interchange generally flows through the card network to the issuing bank. Scheme fees support the network. Acquirer or processor margin covers the company handling acceptance, settlement and related services.

The merchant sees one charge, but the operator should ask for the pieces. A lower interchange rate doesn't guarantee a lower effective rate if the provider adds gateway fees, scheme pass-through, fraud charges or a wider margin.

New Zealand's historical data makes the rail difference clear. Retail NZ reported that domestic EFTPOS debit acceptance was free for most merchants, while weighted-average merchant service fees were about 1.6% for credit cards and 1.2% for contactless debit cards in its 2018 survey (Retail NZ payments survey). The same survey said NZ merchants paid about twice as much as Australian merchants and between three and six times more than UK merchants for comparable card transactions.

More recent Commerce Commission material shows a wide spread, with figures around 0.70% for contactless debit, 1.09% to 1.19% for other New Zealand debit and credit transactions, and 2.39% to 2.49% for international cards (Retail NZ payments survey source and Commerce Commission material). Those figures aren't a promise of your final rate. They show why rail-level reporting matters.

A practical rail comparison

Rail Interchange and fees Effective cost on $50 Conversion impact
Domestic EFTPOS or debit Usually the lowest-cost path, depending on channel and provider Varies by contract and terminal Can work well in person, but isn't always preferred for remote or recurring billing
Domestic credit Higher cost than low-cost debit rails Varies by card type and pricing Often familiar and convenient
International credit Higher network and acceptance cost, with FX exposure Varies by issuer, currency and contract Useful for tourists and overseas customers, but can carry more friction
BNPL or alternative rails Variable and often less transparent across all charges Must be modelled from settlement to support May support conversion, but acceptance cost can be harder to see

A $10 subscription paid on a corporate card in Sydney isn't economically the same as a $10 subscription paid through domestic EFTPOS in Auckland. That sounds obvious, yet many billing systems still report one average rate.

Cross-border transfers create a similar blind spot. Review the practical discussion of hidden fees on international transfers when modelling overseas settlement, currency conversion and intermediary charges. For open banking and account-to-account options, learn how open banking works in New Zealand before assuming a bank-transfer flow will be simple.

Know your rail mix before you negotiate. Otherwise, you're bargaining over an average that may protect the provider more than it protects you.

Checkout, Invoicing, and Routing That Cut Fees

The cheapest legitimate rail should be easy to use, not forced on customers through a clumsy detour. A NZ SaaS charging $49 a month might offer direct debit or account-to-account payment for annual contracts, card payment for monthly billing, and bank transfer for larger invoices. The right mix depends on customer preference, collection speed and support load.

Match the method to the transaction

Rail or method Best use case Cost profile Founder checks
EFTPOS Face-to-face NZ payments Often low cost Confirm terminal, settlement and contactless pricing
Domestic debit Local online or recurring payments Usually lower than credit, but varies by channel Check authorisation, token support and failure recovery
Credit card Monthly subscriptions and convenience-led checkout Higher than low-cost debit rails Measure conversion against net margin
Bank transfer Larger B2B invoices and committed contracts Can avoid card acceptance costs Check matching, payment references and collection delay
Direct debit Recurring plans and annual agreements Depends on provider and mandate handling Test failed debit recovery and cancellation controls
Foreign-issued card Tourists and overseas customers Higher acceptance and FX exposure Track country, currency, settlement and customer value

Route Australian customers through Australian acquiring where the volume justifies local settlement. Keep account details consistent, though. A routing change that creates failed payments or reconciliation gaps isn't a saving. It's a new bill wearing a different hat.

For recurring revenue, use network tokenisation, account updater services, smart retries and clear dunning messages. These tools protect collection without asking every customer to re-enter details. The success metric is not the processor fee alone. Track authorisation rate, settlement time, failure rate and net collected amount.

Design the invoice around the buyer

B2B customers need purchase-order fields, approval controls and automated reminders. Payment links and card-on-file flows suit deposits and renewals, while bank transfer often makes more sense for larger invoices.

At the checkout, put a direct-debit call-to-action beside card payment with plain information about timing, cancellation and account requirements. New Zealand consumer guidance says a surcharge must not exceed the actual cost of accepting that payment type, must be clearly disclosed and should sit alongside at least one surcharge-free option (Consumer Protection guidance on card payment surcharges).

Good payment design removes cost without making customers feel tricked. Review local ecommerce website design decisions through that lens, particularly where checkout friction can erase a fee saving.

Pricing, Bundling, and Automation That Change the Math

Payment cost isn't only a finance problem. It belongs in the price architecture.

A NZ platform charging a fixed amount per order might test a platform fee above a minimum spend. An Australian B2B SaaS may get better economics by bundling implementation, support and usage into clear tiers instead of applying a card payment to every low-value event. The point isn't to add random charges. It's to stop tiny transactions from carrying a disproportionate collection cost.

An infographic showing how pricing, bundling, and automation strategies improve unit economics and business profitability.

Rebuild the unit of value

Annual prepayment can reduce collection frequency, but only use a discount when the cash-flow model supports it. Separate committed spend from metered usage so customers understand what they're buying and the business can forecast the expensive parts.

A marketplace can charge one consolidated vendor fee, then settle payouts by bank transfer. That may reduce repeated card events, but the contract must explain refunds, reserves, payout timing and liability. A neat checkout can still produce a messy back office.

Build price floors from contribution margin, not processor quotes. Include:

  • Refunds and failed payments: Money returned or never collected still consumes work.
  • FX and tax handling: Overseas customers can create currency and compliance costs.
  • Fraud and support: Risk tools and human review belong in the model.
  • Recovery work: A successful retry may require automated messaging and finance follow-up.

Automate the boring, expensive edges

Rules-based invoicing, usage validation, reconciliation and exception queues reduce labour and revenue leakage. Automation won't fix a poor rail choice, but it stops the team from paying twice, first through the provider and then through manual work.

Review packaging against customer behaviour each quarter. If high-volume customers remain on entry plans, test minimums, overages, annual commitments and bundled transaction allowances. The best price is not always the lowest price. It's the structure that keeps the payment event, support burden and customer value in the same economic frame.

For teams connecting billing, CRM and collection workflows, CRM and automation development in New Zealand is a useful place to assess the systems work behind those rules.

Contracts, Integrations, and Platform Choices

Switching to a cheaper rail is not automatically smart. A provider may waive terminal fees while charging higher interchange, minimum monthly amounts or restrictive routing fees. Commercial cards and cross-border B2B payments deserve particular scrutiny because the headline consumer rate may not describe your costly transactions.

A July 2026 submission to the Commerce Commission said B2B merchants can face baseline merchant service fees of 3.01% to 5.00% (Revolut submission on commercial credit-card interchange regulation). Treat that as a warning to segment commercial cards, online transactions and foreign-issued cards before signing a volume deal.

Ask for the real contract

Decision area Questions to ask What to measure
Pricing Are interchange, scheme, gateway and margin shown separately? Effective cost by rail and channel
Settlement Where are funds held and in which currency? Settlement time, FX drag and cash availability
Risk Who pays for fraud, disputes and chargebacks? Losses, review work and recovery outcomes
Routing Can the business choose local acquiring or payment paths? Approval rate and cross-border cost
Integration Is the API, hosted page or middleware doing duplicate work? Engineering hours, reliability and reconciliation quality
Exit Can tokens, records and payment history move to another provider? Migration effort and operational downtime

A direct API may reduce gateway cost while increasing engineering, security and compliance work. A hosted payment page can launch faster, but it may give you less control over routing and customer data. Avoid duplicate tokenisation, unnecessary middleware and payment links sent through separate systems that fracture reconciliation.

For tax-sensitive billing, a clear approach to understanding sales tax APIs can help you judge whether tax automation reduces labour or merely adds another subscription. Choose providers based on total cost, reliability, local settlement, webhook quality and exportability, not a demo-rate comparison.

New Zealand's Retail Payment System Act 2022 gives the Commerce Commission powers to regulate retail payment networks, set pricing standards, regulate merchant surcharges and investigate compliance (Retail Payment System Act 2022). Check NZ and Australian obligations before changing surcharge logic or payment routing.

Your 90-Day Plan to Reduce Transaction Costs

A good cost programme needs a calendar. Otherwise, the spreadsheet gets admired, the contract stays untouched and the same fee leak returns next quarter.

Weeks 1 to 2

Run the map, baseline, attribute and monitor process. Export a one-page dashboard showing cost per successful transaction, rail mix, decline rate, FX drag, refunds, chargebacks and net collected amount. Give finance and product one shared view.

Weeks 3 to 6

Ship the checkout and routing changes with the clearest payback. Make EFTPOS or domestic debit easy where it suits the customer, apply surcharge rules correctly, tighten FX handling and test local acquiring for Australian volume. Renegotiate on per-rail volume, not a blended rate.

New Zealand's regulated interchange structure gives operators useful reference points. Commerce Commission material indicates a capped weighted-average credit-card interchange rate of 0.50% for Mastercard and Visa, Visa Debit at no more than 12 cents per transaction, and EFTPOS at 4 to 5 cents for non-cash-out transactions (MBIE submission on retail payment systems). The same source gives an RBNZ-published direct-connection reference of NZ$78,000 excluding GST, so check integration economics before building a bespoke connection.

Weeks 7 to 10

Re-price or bundle low-value events. Automate dunning, retries, reconciliation and failed-payment recovery. Consolidate software contracts where annual commitments make sense, but don't trade away exportability or a migration path for a small discount.

Weeks 11 to 12

Set guardrails for commercial-card and cross-border B2B exposure. Review settlement, FX, surcharge and refund rules. The Commerce Commission says revised interchange limits took effect on 1 December 2025 for domestically issued cards and take effect on 1 May 2026 for foreign-issued cards (Commerce Commission interchange-fee regulation). Monitor the impact instead of assuming every saving reaches your margin.

Keep the checklist short: measure, route, renegotiate, re-price, automate, repeat quarterly. Transaction costs are a moving operating system, not a one-off procurement task.

A 90-day plan infographic illustrating steps to reduce transaction costs, including assessment, optimization, and scaling phases.


NZ Apps helps NZ and Australian founders assess the software, ecommerce and automation choices that sit behind payment costs, from checkout builds to connected operational systems. Visit NZ Apps to review relevant local providers and plan a payment stack that protects margin without making customers fight the checkout.

Is Your Company Listed?

Add your NZ or Australian app or tech company to the NZ Apps directory and get discovered by founders and operators across the region.

Get Listed

Advertise With NZ Apps

Reach tech decision-makers across New Zealand and Australia. Sponsored and dofollow editorial links, permanent featured listings, and sponsored articles on a DA30+ .co.nz domain.

See Options