Taxi EFTPOS Guides
Tap to Pay on a phone and a dedicated taxi EFTPOS terminal can both make electronic payment convenient. The better fit depends on the whole job: accepted payment methods, receipts, driver access, reporting, connectivity and the rules that apply to your taxi operation.
In this guide
- What does Tap to Pay on a phone mean?
- What does a dedicated terminal offer?
- Compare the complete payment process
- Think through battery, connectivity and device availability
- Put receipts into the demonstration
- Shared vehicles need a clear ownership model
- Compare pricing and suitability separately
- Questions about phone and terminal payments
- Choose the workflow you can operate confidently
Start by separating two phrases that sound similar. A passenger tapping a card or phone on a terminal is contactless payment. A driver accepting that payment directly on a compatible smartphone is a phone-based payment service, often called Tap to Pay or SoftPOS. Those are different setups, even when the passenger makes the same tapping motion.
What does Tap to Pay on a phone mean?
A phone-based payment service uses a supported device and payment application to accept compatible contactless payments. It does not mean that every phone can take a fare simply by switching on NFC.
For example, Apple’s Australian Tap to Pay page describes accepting contactless cards and compatible digital wallets through a supporting payment app. Device, software, payment-provider and regional requirements apply. Check the current requirements for the particular service you are considering.
Android services also need to be assessed against their own provider’s supported-device list and operating conditions. Avoid treating “works on a phone” as a complete specification for taxi use.
What does a dedicated terminal offer?
A dedicated terminal separates payment acceptance from the driver’s general phone. Depending on its configuration, it may provide a purpose-built keypad, card insertion, a printer or a fitted vehicle arrangement. Those capabilities vary, so the device supplied in the quote must match the demonstration.
TaxiPay Australia’s terminal information describes a wireless EFTPOS service for taxi drivers. This guide compares payment approaches generally; phone-based acceptance should not be assumed to be part of a TaxiPay package without direct confirmation.
Compare the complete payment process
| Question | Phone-based acceptance | Dedicated terminal |
|---|---|---|
| Which hardware is required? | A provider-supported smartphone | The supplied terminal and any required accessories |
| How does the passenger pay? | Supported contactless method through the app | Supported methods on that particular terminal |
| How is a receipt supplied? | Check digital delivery and any printing arrangement | Check the printer or digital-receipt options |
| What happens if the device fails? | Check access from another approved device | Check replacement or approved backup arrangements |
| How do drivers share access? | Check user accounts and device-management rules | Check driver identification and handover procedure |
| How are payments reconciled? | Check reports and settlement records | Check reports and settlement records |
Neither column establishes an automatic winner. A single owner-driver may value fewer devices, while a fleet may value keeping payments separate from personal phones. The best answer comes from testing the actual workflow and terms.
Think through battery, connectivity and device availability
A phone can already be serving as a navigation tool, booking device and communication channel. Adding payments may be convenient, but it also makes the phone’s availability more important. Ask what happens during an incoming call, a flat battery, an app update or a lost device.
A terminal needs its own charging and connectivity arrangements too. Separate hardware does not make those questions disappear. Check what the provider supports, where the equipment will sit and how the driver identifies a successfully completed payment.
Do not assume either method accepts payments offline. If a provider offers an offline feature, obtain its exact conditions, limits and risk allocation. A failed or pending authorisation should be handled using the provider’s approved process.
Put receipts into the demonstration
Ask the provider to demonstrate a normal fare and then supply the passenger’s receipt. Consider someone who does not want to share an email address or cannot receive a digital message at that moment. Check what alternative is available and what your service is required to provide.
Next, try to retrieve the transaction later. Can the driver or operator find it using the date, amount and reference? Does the receipt identify enough information to help resolve a query? Our taxi receipt guide explains why the receipt process matters after the passenger leaves.
Shared vehicles need a clear ownership model
Where two drivers share a taxi, identify who owns the device, who holds the payment account and whose transactions appear in each report. Those can be three different things.
Avoid a setup that relies on drivers sharing personal credentials or guessing which payments belong to a shift. Ask whether separate accounts or identifiers are supported, who can approve a refund and how access is removed when someone stops driving the vehicle.
The same principle applies to terminals. A fitted device is not evidence that the system allocates revenue to individual drivers. For larger operations, test the reports described in the fleet reporting guide.
Compare pricing and suitability separately
A phone-based service may avoid a dedicated reader, but that does not prove it has a lower overall cost. Include the payment-service charges, phone requirements, data, accessories and any business-management costs relevant to your setup.
Likewise, a terminal’s supply terms should be compared with its transaction and service terms. Use the taxi EFTPOS fees guide to compare equivalent activity. Check applicable taxi charging requirements rather than assuming a retail pricing model transfers unchanged into passenger transport.
Questions about phone and terminal payments
Is Apple Pay the same as Tap to Pay on iPhone?
No. Apple Pay is a payment method a passenger may use. Tap to Pay on iPhone is a way for a merchant to accept supported contactless payments on a compatible iPhone through a participating app.
Does contactless payment mean a terminal is unnecessary?
No. Contactless payment can be accepted on a dedicated terminal as well as through a supported phone-based service. Decide which equipment and account arrangement fits your operation.
Can a phone replace every function of a taxi payment terminal?
Do not assume so. Check receipts, payment types, reporting, driver allocation, specialised transport arrangements and local requirements for the exact proposed setup.
Choose the workflow you can operate confidently
Ask for a demonstration of payment, receipt, refund, reporting and device failure before making a decision. The most useful technology is the one that supports your work consistently and gives you a clear process when the normal routine is interrupted.
Speak with TaxiPay Australia about its available taxi payment equipment and services, or start with the Australian taxi EFTPOS buying guide.