Bank EFTPOS terminals (Linkly)
One connection that drives the integrated EFTPOS terminals of the major Australian and New Zealand banks.
Most Australian shops already have an EFTPOS terminal from their bank and key the amount into it by hand. An integrated terminal does away with that: the till sends the amount to the PIN pad, the customer taps, and the sale closes itself. Wrong-amount keying, unmatched tenders and the nightly hunt for a five-dollar difference all go away.
Banks do not each expose their own till interface. Nearly all of them route integrated payments through Linkly — the payments middleware formerly known as PC-EFTPOS. Connect Linkly once and the same connection drives a NAB terminal, a CommBank terminal, an ANZ terminal or a Westpac one. You do not change anything here when you change banks; you pair the new PIN pad and carry on.
Which banks this covers
These are the acquirers Linkly lists as bank partners. If yours is on it, your terminal can be driven from the counter — you do not need to change banks, change merchant agreements or move your settlement anywhere.
| Country | Banks and acquirers |
|---|---|
| 🇦🇺 Australia | NAB · Commonwealth Bank · ANZ (ANZ Worldline) · Westpac · St.George · Bank of Melbourne · BankSA · Zeller · Live Payments · Fiserv · Nuvei · Wpay · Suncorp Bank (see the note below — Suncorp is closing its merchant facilities) |
| 🇳🇿 New Zealand | Terminals supplied through Skyzer and Verifone NZ |
The four largest have a page of their own, because what you order and who you ring differs at each: NAB, CommBank, ANZ and Westpac (which covers St.George, Bank of Melbourne and BankSA too). New Zealand has its own page. Everything after this point is the same whichever bank you are with.
Bank terminals are an AU/NZ arrangement. If you trade in the UK, Ireland, Singapore, Canada or the United States, take cards in person with Square Terminal or Stripe instead.
How the cloud pairing works
There is no software to install. This is Linkly's cloud product, so nothing runs on the computer at the counter — not a driver, not a background service, not a client application. Three parties talk to each other:
- Your PIN pad holds a permanent connection out to Linkly's cloud over the shop's internet.
- Linkly's cloud sits in the middle and routes messages between the PIN pad and whoever is authorised to drive it.
- Our servers send the sale to Linkly and are told the outcome when the customer has finished.
Pairing is what introduces the two ends to each other. It happens once per PIN pad and produces a key that does not expire, stored encrypted against your company. There is nothing to renew and no daily login for your staff. Two things do end a pairing, and both are deliberate: changing the password on your Linkly Cloud account, and pairing that same PIN pad to a different point-of-sale system. If a terminal stops responding out of nowhere, ask whether either of those has happened.
Because the PIN pad reaches Linkly over the internet rather than over a cable to the till, the two devices do not have to be on the same network — and a tablet or a phone can drive a terminal sitting on the other side of the shop. What the terminal does need is a working connection of its own: Wi-Fi, ethernet or its SIM.
What you need before you start
| What | Where it comes from |
|---|---|
| An integrated EFTPOS terminal | Your bank. Ask for it as integrated up front — at several banks the standalone and the integrated terminal are different products. |
| A Linkly Cloud account (a username and password) | Your bank, as part of setting the terminal up for integration. |
| The pair code | The PIN pad itself, when you put it into pairing mode. It is shown on the terminal's screen. |
| A payment method pointed at the terminal | You, in POS → Settings → Payments. |
Nothing else is needed from us. You do not need an account with Linkly directly, you do not pay Linkly, and there is no separate merchant agreement to sign — your merchant relationship stays with your bank, and so does your settlement.
Step 1 — Order an integrated terminal
Ring your bank's merchant team and say you are moving to an integrated EFTPOS terminal and that your point-of-sale software connects through Linkly (some staff still know it as PC-EFTPOS). Those two words matter. At some banks the standalone and the integrated terminal are different products entirely; at others it is the same hardware carrying a different software load. Either way it is settled when the order is written, so be explicit on the first call rather than discovering it when the box arrives.
The bank pages linked above say exactly what to ask each bank for.
Step 2 — Ask the bank for a Linkly Cloud account
Integration is not automatic once the terminal turns up. Ask the same merchant team for a Linkly Cloud production account for your merchant number. They will send you a username and password. That pair is what proves to Linkly that the terminal is yours.
Keep those credentials to hand for the pairing step, and treat them like any other banking credential — they are yours, not ours. We use the password once, at the moment you pair, and never store it.
Step 3 — Put the PIN pad into pairing mode
Do this standing at the terminal, with the suite open on the counter screen next to you — the code the terminal shows does not last long. Exactly which buttons you press depends on the make of PIN pad, so follow your bank's own instructions. On every model the result is the same: the screen shows a short pair code and waits.
If your terminal asks for a pairing host rather than showing a code straight away, it has not been loaded with the integration settings. That is a job for the bank's helpdesk, not something to guess at — ring them and ask them to configure the terminal for Linkly Cloud pairing.
Step 4 — Pair it in the suite
- Go to Settings → Integrations → Bank EFTPOS via Linkly. The Integrations tab is visible to owners and admins only.
- Press Add a terminal. Give it a name your team will recognise at the counter ("Front counter", "Workshop"), choose the store it belongs to, and pick your bank from the list.
- Enter the username and password your bank gave you, and the pair code currently on the PIN pad's screen.
- Press Pair. The terminal confirms on its own screen and the row flips to paired.
That is the last time you will type those credentials. The pairing sticks: the terminal can be switched off, moved or rebooted and it comes back paired.
Step 5 — Point a payment method at the terminal
The till decides where to send a payment from the payment method's gateway, so a paired terminal does nothing until a method is bound to it:
- Go to POS → Settings → Payments.
- Add a method, or edit the "Card" or "EFTPOS" method you already use, and set its gateway to the bank terminal.
The name on the button is yours to choose — it is the gateway setting, not the name, that wakes the terminal. Skip this step and the integration will sit there connected while every sale still goes through by hand.
Taking a payment
At the counter it is one extra tap and nothing to remember. The cashier rings the sale up as usual, picks the bank-terminal payment method and confirms their staff PIN. The terminal wakes with the amount already on it, and the customer taps, inserts or swipes. The till follows along — waiting for the customer, then the outcome — and posts the sale as soon as the bank approves it.
The card is taken before the sale is recorded, so a decline or a customer pressing cancel on the PIN pad never leaves a phantom sale behind: the till simply returns to the payment screen so you can try another card or another tender. Surcharges, split payments and every other tender behave exactly as they do today — see Taking payment and Split payments.
Refunds
An EFTPOS refund goes back through the terminal, and it is tied to the original purchase. Run the refund in the POS the normal way and choose to refund to the original payment; the amount is sent to the PIN pad along with the reference the bank gave when the sale was approved, and the terminal takes it from there.
This is where a bank terminal differs from Stripe and Square. Those refunds are sent back to the card with nobody present; a bank EFTPOS refund is a transaction on the PIN pad, so the customer has to be at the counter with the card they paid on. Refunds are also whole-sale only — to take back part of a sale, use an exchange instead. See Refunds and returns.
If the refund fails at the terminal, the POS refund still stands and you are told plainly, so the money side can be sorted out separately rather than leaving the sale in an unknown state.
End of day
Settlement stays with your bank. The terminal settles on your bank's schedule and the money lands in your account exactly as it does now — nothing about that changes, and no money passes through us.
What changes is that the card figure at close should now match without arithmetic. Because every approved transaction is posted by the till rather than typed in, your card total for the shift is the sum of what the terminal actually approved. Close the register as usual (see Registers and shifts) and check it against the terminal's own settlement report; a difference now means a transaction to look at, not a keying error to hunt for. The tender breakdown in Standard reports gives you the same figure over a period.
When something goes wrong
| What you see | What it means | What to do |
|---|---|---|
| Pairing is refused and the terminal has gone back to its idle screen | The pair code lapsed. Codes are short-lived by design. | Put the PIN pad back into pairing mode for a fresh code and pair again. There is no way to extend one. |
| Pairing is refused with a credentials error | The username or password is wrong, or it is a test account rather than a production one. | Re-type both — they are case-sensitive and a trailing space pasted in from an email is the usual culprit. If they still fail, ring your bank and confirm the account is a Linkly Cloud production account for your merchant number. |
| The terminal shows as offline, or a sale never reaches it | The PIN pad has lost its connection to Linkly. | Check the terminal's own network indicator first, then the shop's internet. A terminal that has dropped off looks identical to a POS problem but is not one. |
| The customer has tapped and been approved, but the till is still waiting | The result has not come back yet — usually a momentary network blip. | Do not take the payment again. The sale is safe: we ask Linkly for the outcome of that exact transaction and post it when it arrives. Give it a moment before doing anything else. |
| The till says the transaction could not be confirmed | We could not establish the outcome within a reasonable window. | Check the PIN pad's screen or its receipt to see whether the customer was charged, then either let the sale complete or take payment another way. Never assume a decline from silence. |
| Everything is paired but no terminal wakes at the counter | No payment method is pointed at the terminal. | Set the method's gateway in POS → Settings → Payments. This is the single most common miss. |
The other acquirers
Everything above applies unchanged to the acquirers that do not have a page of their own. What differs is only who you ring and what the terminal is called.
St.George, Bank of Melbourne and BankSA
All three are Westpac group brands selling the same hardware under their own colours, and the Linkly-integrated terminal at each is EFTPOS Connect. Their helpdesk numbers and the ordering wording are on the Westpac page.
Zeller
Zeller is an Australian payments provider rather than a bank, and its own terminals are listed by Linkly for both cloud and on-premises integration. Ask Zeller support to enable Linkly integration on your account and to issue Linkly Cloud credentials; everything from pairing onwards is identical to a bank terminal.
Live Payments
Live Payments is a Linkly partner in its own right. Their own marketing does not use the word Linkly, so ask for Linkly Cloud integration explicitly when you order or when you ring support, rather than assuming an integrated terminal is a Linkly-integrated one.
Fiserv
Fiserv publishes its Linkly certification plainly — their Australian terminal page says the terminals are certified with Linkly, "formerly PC EFTPOS", as they put it. Ask for a terminal configured for Linkly Cloud, and for a production cloud account to go with it.
Nuvei (formerly Till Payments)
Till Payments no longer exists as a brand — the business is now part of Nuvei, and Linkly lists the terminals under that name. If your paperwork still says Till, you are a Nuvei merchant: ring the number on your statement and ask for Linkly Cloud credentials for your terminal.
Wpay
Wpay appears on Linkly's partner list and works the same way. Ask your account manager for a Linkly Cloud production account and a terminal configured for cloud pairing.
Suncorp Bank has told its merchants that from 11 December 2026 it will no longer be able to offer merchant facilities at all, following changes to its third-party provider arrangements. That is not about integration — it is the whole merchant facility. If you are on Suncorp, arrange a facility with another provider rather than putting effort into pairing a terminal that is due to be collected. Every other bank on this page is a straightforward move, and none of them affects anything in the suite beyond re-pairing the new PIN pad.
Replacing or moving a terminal
A terminal that is being swapped out is revoked from its row in Settings → Integrations, and the replacement is paired with its own code — nothing else changes and the sales history is untouched. Moving a terminal to another shop means revoking it and pairing it again against that store, so payments are attributed to the right place.