Choose a payment gateway for your online store
Choosing a payment gateway? Compare payment processing, Australian methods, fees and settlement, then verify the checkout and refund flow for your store.
- Published
- Last updated
A payment gateway securely passes checkout payment information to the services that seek approval for a purchase. Choose a gateway that supports your storefront, required payment methods and Australian business, then compare its full acceptance costs and payout terms.
The checkout’s success screen answers one question: did the payment flow report success? Your order, provider transaction and bank deposit still need to agree.
What a payment gateway does
A payment gateway carries payment information between your checkout and the payment processing service. For an ordinary card order, it sends the payment request onwards and returns the approval or rejection to your store.
Imagine a customer buying a pair of shoes. They enter their card in the provider’s supported payment form. The gateway passes the request into the processing chain, and the card issuer decides whether to authorise it.
The services have different jobs, even when one company supplies several of them.
| Role | Job in an online card purchase | What you need to establish |
|---|---|---|
| Payment gateway | Transmits payment information and the response | Which checkout integration sends the request |
| Payment processor | Handles transaction messages between the payment participants | Who processes the payment and reports its state |
| Acquirer | Provides card acceptance to the merchant and receives funds through the card system | Who owns the acquiring agreement and merchant settlement |
| Merchant account | The card acceptance account or facility used to receive card proceeds | Whether you need a separate facility or the provider supplies acceptance within its service |
A merchant account differs from your everyday business bank account, where payouts ultimately arrive. Stripe describes its service as combining gateway and processing functions. A bundled payment service can therefore save you separate contracts without making those roles interchangeable.
The Reserve Bank of Australia’s explanation of card payment participants and fees identifies the issuer and acquirer on opposite sides of a typical card payment.
From payment method to settlement
A card payment moves from issuer approval to collection and eventually a bank deposit. The gateway’s response is only one part of that sequence.
- The customer chooses a supported payment method. Your checkout passes the order amount and currency to the payment provider.
- The provider’s processing route requests authorisation through the card network. The issuer approves or declines the request. An approval can reserve funds before they’re collected.
- Your store or provider requests capture, automatically or after staff approval under your settings. Capture starts collection against the authorisation.
- The issuer and acquirer settle the card payment through the payment system. Your provider records the proceeds under its settlement rules.
- The provider sends a payout to your nominated bank account. Your bank then credits the deposit.
Suppose a store authorises a hypothetical $120 order while staff confirm stock. The order can exist with an authorised payment before capture. After capture, the store can record it as paid while its provider balance still awaits payout.
Incorrect: treating an order marked Paid as proof that $120 has arrived in the bank. Correct: match the captured transaction to its payout, then match that payout to the bank deposit.
Fees, refunds and adjustments can make a payout differ from gross sales. Stripe’s payout documentation separates funds becoming available from the payout schedule and the bank’s processing time.
Choose a gateway and provider for an Australian store
Choose the payment setup that meets your store’s requirements with a support arrangement your team can manage. Compare the following routes against the same checkout, order mix and refund workflow.
| Route | Practical fit | Responsibility to resolve before choosing |
|---|---|---|
| Integrated platform payments | You want payment and order management in the storefront admin | Confirm business eligibility, supported checkout methods and the platform’s payment support process |
| Bundled payment-service provider | You want one service for gateway and processing functions | Confirm the supported storefront connector, acquiring arrangement and who maintains the integration |
| Separate gateway and merchant facility | You need a gateway connected to a chosen acquiring facility | Confirm both parties approve the connection and identify who investigates each kind of failure |
Shopify Payments is an example of the first route. Its Australian service documentation places payment processing and order management in Shopify admin. Stripe is an example of a bundled gateway and processor. CommBank’s Internet Merchant Account documents a separate facility that connects with approved third-party gateways.
Before requesting quotes, write down your storefront version, checkout extension or connector and every place customers pay. Include mobile checkout and subscription renewals if you use them. A provider’s general support for a platform doesn’t establish support for every connector or checkout surface.
Check Australian business eligibility and the required bank account before comparing rates. Shopify Payments, for example, has business-type restrictions and bank-account requirements for Australian stores. Then confirm settlement currency, initial payout timing, normal payout schedule and any reserve or hold provisions in the offered agreement.
Identify where card details enter the system. A redirect sends the customer to the provider’s payment page. An embedded provider form keeps its payment fields inside your page. Your own form that handles card data creates a different responsibility boundary.
Ask the provider to identify its validated services and your remaining Payment Card Industry Data Security Standard (PCI DSS) duties. The PCI Security Standards Council’s guidance for embedded payment forms explains the relevant script-security confirmation. Using a gateway alone establishes neither your store’s PCI DSS validation nor its privacy compliance. Use the ecommerce PCI compliance guide for the separate assessment task.
Compare payment processing and gateway costs
Compare the total cost of accepting the same orders, including platform charges and services billed outside the gateway quote. A low gateway subscription can sit beside a separate acquiring fee.
Use one quote worksheet with the following inputs and charges.
- Keep order count, average order amount and domestic versus international card mix identical.
- Specify the customer’s payment currency, payout currency and whether currency conversion is needed.
- Record gateway subscriptions, setup fees and connector costs separately from transaction charges.
- Identify processing and acquiring or merchant-service fees. Mark charges included in a bundled rate so you count them once.
- Add applicable platform transaction fees, refund costs, dispute fees and required subscription-billing services.
- Compare every quote on the same goods and services tax (GST) basis, billing period and contract term.
Stripe’s Australian pricing lists domestic card payments at 1.65% plus $0.30 per transaction, including GST, on standard pricing. For a hypothetical 1,000 domestic card orders of $80 each, that is $1,620 in card processing fees. This calculation excludes other paid services, refunds and disputes.
The separate merchant-facility route needs both quotes. CommBank lists account and transaction charges alongside a custom merchant-service fee, so its account fee alone cannot establish the total. Ask the gateway and acquirer to price the same worksheet and identify any overlapping charges.
On Shopify, third-party transaction fees can apply in addition to the external provider’s processing fees. The third-party fee rules also describe exemptions. Apply the rule to the actual payment route and plan instead of adding a blanket platform percentage.
Match payment methods to the buying journey
Choose payment methods by the purchases you serve and the methods your actual integration supports. Availability depends on merchant eligibility, customer location and currency as well as the provider’s capabilities.
| Method | Customer experience | Capability to confirm |
|---|---|---|
| Credit and debit cards | The customer enters card details and completes any required authentication | Accepted card networks, capture settings and refund support |
| Digital wallets | An eligible customer approves payment using a wallet | Supported devices, browsers and checkout integration |
| Buy now pay later | The customer applies for or uses the provider’s instalment arrangement | Eligible products, order values, countries and currencies |
| Bank-based methods | The customer approves a bank payment or supplies an agreed debit authority | Confirmation timing, supported currency and order-release rules |
Shopify Payments in Australia lists Visa, Mastercard, American Express and UnionPay for online cards. It also lists Apple Pay, Google Pay and Shop Pay for accelerated checkout. Its local payment methods depend on the customer’s location. These capabilities don’t mean every method works for subscriptions.
For cross-border purchases, separate the currency shown to the customer from the currency paid to your bank. Include the customer’s market and card origin in your quote. Shopify’s Australian payout rules make multi-currency payout eligibility depend on the store’s plan and account setup.
Follow a recurring payment through renewal
Recurring payments need permission to charge again and support across the payment method, billing service and storefront. A successful one-time card payment alone doesn’t establish that support.
For example, a retailer offering regular consumable deliveries can use Shopify Payments with a compatible subscription app. Shopify’s subscription gateway guidance identifies supported routes and method restrictions. Set up the subscription product and cancellation policy through the app’s documented process.
The customer accepts the amount or its calculation, payment frequency and cancellation terms before the first payment. The provider saves the authorised payment method for that agreed use. Keep the customer’s agreement with the subscription record.
At renewal, the billing service requests another charge against that saved method. Match the renewal payment attempt to the resulting storefront order and release fulfilment only under your confirmed payment rules.
If the renewal fails, inspect its invoice or billing attempt and the provider transaction before taking payment manually. Confirm there is no successful charge or already released shipment. Resolve the failed attempt through the supported recovery flow so an automatic retry and a staff charge don’t collect the same renewal twice.
Keep checkout and support answers consistent
Show payment options and the final payable total before the customer authorises payment. After payment, make the confirmation and order status reflect the recorded result.
Remove card surcharges prohibited by the applicable network rules. The Australian Competition and Consumer Commission’s card guidance covers Visa, Mastercard, American Express and eftpos. The Reserve Bank’s surcharge FAQs explain network rules and possible exemptions. Keep the full requirements in the surcharge ban guide.
Give staff the current accepted-method list, refund policy and meanings of order payment states. A support answer can say a payment is authorised, captured or refunded when the relevant record confirms it. A screenshot of a customer’s pending bank entry is a reason to investigate before retrying.
Shopping assistance can explain payment options and help a customer find their order. Keep card entry in the provider’s supported payment surface and route unresolved payment states to staff with the order and transaction references. Never ask a customer to paste card details into a chat or support message.
Verify the gateway and order flow before launch
Use the chosen provider’s sandbox or documented test mode to verify payments without moving customer funds. Test an isolated store or checkout environment with fulfilment integrations prevented from sending real goods.
For a Stripe-backed integration, use Stripe’s testing instructions and the storefront connector’s documented sandbox settings. The following sequence gives expected records to inspect.
- Enable the provider’s sandbox credentials and confirm the storefront points to that environment. Use only the documented test payment details.
- Place a successful test order. Expect one successful provider payment for the correct amount and currency, linked to one store order. Check the confirmation reaches the designated test inbox.
- Attempt a rejected payment using the documented decline test case. Expect a failed attempt, a useful checkout error and no order released as paid for fulfilment.
- Interrupt a checkout before submission, then separately close the browser after submitting payment. Inspect the provider state before resuming. Reconcile any completed payment with the existing order before another charge.
- Refund part of the successful test payment through the supported storefront action. Expect a provider refund linked to the original payment and the same refunded amount in the order. Check the test customer’s refund notification where configured.
- Repeat the applicable checks for each extra method and for a subscription renewal. Keep the provider transaction references beside the order references.
Stripe recommends reusing the existing PaymentIntent, its payment-attempt record, when an interrupted checkout resumes. Its payment lifecycle guidance explains that relationship. Your connector must preserve the corresponding order link.
If the provider says Paid while the store says Pending, pause release of that order. Check the matching transaction identifier and the provider’s event-delivery log with the integration owner. Repair the missed status update and confirm one order has one intended payment before enabling the route for customers.
Shopify has its own payment test-mode procedure. Subscription tests require a supported route, and simulated transactions don’t prove that a bank payout works. Exit test mode and verify the live account’s configuration before opening checkout.
Handle failed payments, refunds and disputes
Use the provider’s payment record to distinguish a rejected charge from an authorised hold, a refund and a dispute. Each needs a different response.
| Recorded state | What it means | Next action |
|---|---|---|
| Failed authorisation | The attempted payment wasn’t approved | Read the decline result and follow the supported customer recovery flow |
| Authorised but uncaptured | Funds are reserved, but collection hasn’t completed | Capture within the provider’s allowed window if proceeding, or cancel the authorisation |
| Merchant refund | The merchant has requested money back against a successful payment | Check the refund’s own status and reference before promising completion |
| Provider dispute | The customer has questioned a payment through their issuer | Use the dispute workflow and respond with the required evidence before its deadline |
Stripe’s refund and cancellation instructions distinguish cancelling an uncaptured payment from refunding a completed one. A pending or failed refund needs investigation. Starting a refund doesn’t prove the customer has received the money.
A card dispute has its own financial adjustments and response process. Check for an existing dispute before issuing a separate refund, and follow the provider’s instructions to avoid duplicate reimbursement.
Stop retrying when the last attempt’s result is uncertain, a successful payment already exists or the provider requires customer action. Give the responsible payment provider the order reference, transaction identifier, amount and event history. Keep fulfilment on hold until staff can explain the recorded payment state and confirm the intended charge occurs once.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.