For a startup in the Great Southern, comparing fintech fees begins with understanding the service being purchased. A low percentage or free app can describe only one part of the arrangement, while setup, connected services and internal administration remain elsewhere.
This beginner guide builds a practical comparison before commitment. It explains the questions behind a cost picture without recommending a financial product or assuming that a startup’s expected activity will become actual sales.
Begin with the task, rather than the fintech label
Identify what the service is meant to help the startup do. Taking a payment, reviewing a statement and preparing information for an adviser are different tasks, even when a supplier presents them together.
Describe the people, channels and actual locations within the proposed scope. A Great Southern business may work in more than one setting; the conditions at one desk do not establish those at every workplace.
Keep the starting requirement bounded. A feature can be appealing without being necessary for the first task the business is ready to examine.
Learn the difference between a rate and a total cost
A percentage needs context: which transactions it applies to, what its calculation includes and what sits outside it. A headline figure should not be copied into a budget without those definitions.
For example, CommBank’s merchant service fee metric excludes non-transaction charges such as terminal rental and chargeback fees. That published metric is not a complete individual startup quote.
Use the example to ask better questions, rather than assuming its figures or exclusions describe every provider. Relevant actual charges need confirmation for the particular offer.
Separate setup, continuing and conditional charges
Ask what is required to begin, what continues during ordinary use and which stated conditions can create another charge. Keep optional additions distinct from components necessary for the intended task.
Write down the source and date of an actual offer. An advertisement, preliminary estimate and confirmed proposal are different kinds of evidence; uncertainty should remain visible when an item has not been priced.
Include connected arrangements that the proposed workflow depends on. A free interface can still require another paid service, while an included feature may need staff preparation to become useful.
Compare a consistent activity example
Use the same explicitly estimated activity assumptions for each relevant offer. Identify what would change if the expected mix, channel or volume were different, rather than presenting a forecast as a measured result.
Do not use another business’s experience as proof of your startup’s costs. The Great Southern location gives context, but it does not establish transaction volume, customer preference or the same commercial conditions.
When an assumption matters materially, turn it into a question for the provider or an appropriately qualified adviser before relying on the total.
- The task and service boundary.
- The charging basis and exclusions.
- The setup and continuing amounts.
- The estimated activity assumptions.
- The staff work and commitment conditions.
Understand merchant expense separately from customer pricing
A provider’s charge to the startup does not by itself authorise passing the amount to customers. Merchant costs and customer pricing rules need separate consideration.
The ACCC’s current price-display guidance states that card surcharges for Visa, Mastercard, American Express and eftpos credit, debit and prepaid payments are prohibited from 1 October 2026. Keep that rule distinct from the existence of merchant service expenses.
Do not rely on an older cost-of-acceptance explanation or assume relabelling a card surcharge changes its nature. Obtain appropriate current guidance for the actual proposed pricing arrangement.
Allow for the work retained by the startup
Someone still needs to prepare information, understand reports, check unfamiliar entries, obtain help and maintain access. Include learning, receiving checks and cover for the responsible person.
These contributions can change the practical value of two apparently similar offers. Time moved between tasks is not automatically money saved, and a projected benefit remains an estimate until supported by suitable evidence.
For early discussion, use invented examples rather than real customer or account information. Establish supported non-live conditions before any software practice could initiate payments or alter operational records.
For a simple discussion example, distinguish an ordinary low-activity period from a later period with a different mix of work. Keep both explicitly hypothetical and apply the same stated assumptions to each offer. The exercise can expose a question about charging conditions without claiming that either pattern predicts the startup’s future trading.
Read the commitment behind the comparison
Retain actual billing dates, minimum commitments, renewal conditions and relevant transition questions. A monthly equivalent can help comparison while still concealing a different payment schedule if the underlying dates are omitted.
Finish with a record of the task, actual offer, assumptions and next authorised enquiry. A beginner’s fee comparison becomes useful when the Great Southern startup can explain what it would pay for, what it would still do and what remains uncertain before buying.