How to Accept Online Payments: Sydney Business Guide

Start with the sale you want customers to complete

Picture a specific purchase from your business. Perhaps a customer is paying an agreed project deposit, booking an appointment or buying a product. Write down what you want them to understand before paying, then describe the confirmation you want them to receive. Keep the first version focused on that transaction rather than every possible future sale.

Payment terms set out how and when customers must pay for your goods or services. For your project, agree those terms before discussing screen layouts. Decide whether you want payment before confirming the work, after completing it or at an agreed stage. Have your accountant or legal adviser review the proposed terms where appropriate.

Give repeat payments their own discussion. A direct debit requires your customer to authorise payments from their bank account. If you are considering recurring collection, ask the provider to demonstrate its authorisation process and explain how your team would handle changes or cancellation requests. Keep that decision separate from accepting an individual purchase.

When deciding how to accept online payments, prepare a short description of the sale for prospective providers. Include what the customer buys, when you expect payment and which staff member takes over afterwards. Ask each provider to work through the same example. Judge its proposal against your actual transaction, including the awkward moments, rather than the length of its feature list.

Match the checkout to your website and workflow

With the transaction agreed, consider where the customer should complete it. For an established website, begin by asking your developer to demonstrate a suitable existing integration. For a proposed rebuild, include payment acceptance in the design brief and acceptance testing. Treat a custom checkout as a choice that needs a clear business reason.

Business.gov.au describes ecommerce platforms and plug-ins that integrate with a website and handle ecommerce functions, including payment. Ask shortlisted suppliers to show how their proposed setup would work with your site. Include the customer journey and the staff view in that demonstration, then request a written explanation of anything requiring separate development.

Be specific about the experience you want. For an agreed service deposit, you might ask for a payment request tied to an approved quote. For a product purchase, you might want customers to review their order before paying. Put those requests into the brief and ask providers to confirm which ones their proposed configuration supports.

Ecommerce platforms usually have ongoing subscription costs and may also charge a fee for each transaction. Before commissioning changes, request a complete proposal covering setup and ongoing ownership. If you need help scoping website development, bring the proposed payment journey into that conversation. Keep the initial release centred on the sale you defined, with any additional functions priced separately for later consideration.

Compare the commercial terms using your own sales

The next decision is what you are prepared to pay for the proposed arrangement. Business.gov.au identifies service fees and transaction costs as considerations when choosing payment methods. Ask each provider to price the same sample of your expected sales, using assumptions that you have approved. Keep those assumptions beside the quote so you can revisit them.

For example, prepare a sample month based on your own transaction values and expected activity. Ask providers to identify every applicable charge, state whether tax is included and explain their treatment of refunds. Request written answers about settlement timing and any circumstances in which they could delay access to funds. Treat unanswered questions as matters to resolve before signing.

Discuss administration alongside the quoted fees. Ask your office manager to walk through a payment query and your bookkeeper to review a sample report. Invite both to identify steps they would need to perform manually. Include their feedback when comparing proposals, and ask suppliers to clarify any additional work they expect your business to undertake.

Your decision about how to accept online payments should include an exit discussion. Request the cancellation terms, a description of available records and a proposed handover process if you change suppliers. Keep the provider account under your business's ownership, with authorised staff responsible for it. Agree who may approve commercial changes and who should review the arrangement as your needs develop.

Make the customer journey clear and deliberate

Now return to the customer-facing experience. Business.gov.au recommends encrypting payment information to protect customers. Ask your developer and payment provider to explain how their proposed setup addresses that guidance. Request a clear account of where customers enter their details, which organisation handles them and which responsibilities remain with your business.

Business.gov.au also recommends making online sales terms and conditions clear, accurate and easy for customers to find. Have an appropriate adviser review your wording, then include its placement in the website brief. Review the payment page as a customer: what are you buying, what amount are you approving and how would you contact the business afterwards?

Ask for a demonstration on the devices your customers are likely to use. Include a successful payment and an unsuccessful attempt. Review the wording shown at each stage and decide what you want the customer to do next. Give particular attention to uncertainty: if someone contacts your office asking whether payment went through, how should staff investigate before suggesting another attempt?

Include account access and responsibility for changes in a cyber security review. Ask the reviewer to document recommended controls for your particular arrangement, including who should approve changes to payment destinations.

Follow the payment through to your books

Before approving the build, sit down with the person responsible for your accounts. An invoice tells customers how much they owe, when to pay and how they can pay. Agree which document your customer should receive and ask your accountant to confirm the invoice requirements applicable to your business. Include that decision in the implementation brief.

Business.gov.au recommends accounting software to manage invoices, sales and customer accounts. Ask your bookkeeper to identify the record they want to use when checking a payment. Then have the supplier demonstrate how the proposed checkout supports that process. Request sample records rather than accepting a general statement that the systems work together.

For the walkthrough, follow an individual sale from the customer's confirmation through to the records your bookkeeper would review. Ask how they would match the amount, identify any applicable fee and investigate a difference. Include a refund in the demonstration. Agree what information staff should record and where they should direct questions they cannot resolve.

Keep the first handover understandable to the people doing the work. If your proposed process includes manual checks, document who performs them and when. If you commission integration and automation work, specify the exact handoff you want and the evidence you expect during testing. When planning how to accept online payments, make the bookkeeping walkthrough part of acceptance, with your finance person involved before launch approval.

Launch with a clear owner and a controlled trial

Bring the proposed arrangement together in a controlled trial before opening it broadly to customers. Agree the testing method with your provider, including whether to use its available test facilities or an authorised live transaction. Define what you want to observe and who has authority to approve launch. Record the outcome of each agreed scenario.

• •Walk through a successful purchase and review the customer's confirmation alongside the staff record.
• •Agree how to test an unsuccessful attempt and the instructions your customer should receive.
• •Demonstrate the approved refund process and have your bookkeeper review its records.
• •Have the staff member taking ownership explain how they would investigate a payment query and escalate it.

Give that owner a short operating guide with provider contacts and agreed responsibilities. Include who may approve refunds, who reviews records and who authorises configuration changes. Ask another authorised staff member to practise the process using the guide, then revise anything unclear. Set a review point after launch to discuss questions raised by staff and customers.

For a Sydney business deciding how to accept online payments, our recommendation is to begin with a clearly defined sale and follow it all the way through. Bring your office manager, accountant and developer into the same discussion. Approve the arrangement when you understand the customer experience, the commercial terms and the work your team will own each day.

This article reflects best practices as of the publication date. Technology and security recommendations evolve, so verify current guidance with the original sources or our team before acting.