A customer has chosen a meal, a haircut or a repaired pair of shoes. The work is done, but the sale pauses at a familiar question: can I pay by card? For a small business, the answer depends on more than willingness. Someone must arrange a payment service, carry the necessary equipment, keep it connected and understand what happens after the customer leaves. Smartphone card acceptance changes one part of that arrangement by allowing a compatible merchant phone to act as the contactless acceptance device.
In South Africa, Nedbank’s Tap on Phone functionality provides a concrete example. Its merchant guidance describes accepting contactless cards through the PocketPOS application on supported NFC-enabled Android phones. The merchant still needs the appropriate service and a compatible handset; owning a smartphone alone does not establish a card acceptance business account.[1] The interesting development is therefore both technical and practical: a device already used for bookings and customer communication can also become a checkout point.
What the phone is actually doing
Near-field communication, usually shortened to NFC, lets compatible devices communicate over a very short distance. In this setting, the merchant enters the purchase amount in the acceptance application, and the customer presents a contactless payment card or supported payment device. The application then participates in the payment provider’s transaction process. The phone is an interface to that service, rather than a private container into which money is physically transferred.
This distinction helps explain why a successful tap and the merchant’s eventual bank balance are different things to monitor. The checkout needs a clear transaction result, while the business also needs settlement records, fee information and a way to investigate exceptions. The technology reduces the equipment involved at the counter, but it does not remove the accounting behind the counter.
There is also an important difference between paying with a phone and accepting payment on one. A customer using a mobile wallet is the payer. A trader running a merchant acceptance application is receiving a card transaction. The two experiences may look similar across a market stall, but their registration, security controls and commercial agreements serve different roles.
A South African example with practical limits
Nedbank’s published merchant FAQ identifies compatible Android hardware and NFC as requirements and warns that some devices may remain incompatible despite meeting an operating-system requirement. It also describes PIN entry within its certified acceptance application when verification is required.[1] These are product-specific details, not rules that can safely be applied to every payment application advertised online.
For a trader considering the service, the sensible first step is to check the exact phone model against the provider’s current requirements. A handset purchased several years ago may still handle messaging perfectly while failing an acceptance application’s security or hardware checks. A phone advertised as having NFC may also need further provider approval. Compatibility should be confirmed before buying equipment or promising customers a new payment option.
Historical business stories provide useful context without proving universal results. Nedbank has described CoffeeToCar’s use of its service for mobile coffee sales.[2] That example illustrates why carrying less checkout equipment can suit a moving trader. It does not establish that every café, salon or informal retailer will achieve the same commercial outcome.
The checkout becomes part of the working day
Consider a hypothetical mobile hairdresser who travels between appointments. The same phone receives booking messages, displays directions and records card payments. Carrying one device could simplify the visit, but the arrangement also concentrates several tasks in one place. A flat battery could interrupt both the journey to the client and the final payment. A practical setup therefore includes charging, connectivity and a fallback process agreed before an appointment starts.
At a busy food stall, the difficulty may instead be staff coordination. If the owner’s phone is the only acceptance point, every sale could require the owner to stop cooking. A technology that removes a separate terminal can still create a queue when too many duties depend on the same person. The appropriate arrangement follows the business’s workflow, not simply the smallest number of devices.
A useful trial asks staff to perform normal tasks in normal conditions. Can they see the amount outdoors? Can they find the NFC contact area quickly? Can they distinguish a completed payment from one still processing? These ordinary observations reveal more than a successful demonstration in a quiet office.
Lower equipment needs do not mean zero costs
The commercial question is the total cost of accepting payments. Nedbank’s FAQ explains that usual merchant charges and data costs still apply even where the feature itself adds no separate feature cost.[1] Providers can have different pricing structures, settlement arrangements and contractual terms. Any comparison should use the current written offer for that merchant rather than a remembered promotional headline.
For illustration only, imagine a business evaluating a quoted percentage charge on a basket of R100. A hypothetical 2% charge would be R2 before any additional charges or tax treatment specified in the agreement. That arithmetic is not a quotation from any provider. Its purpose is to show why a small percentage must be considered alongside gross margin, average purchase value and the number of transactions.
The phone also has a cost even when it is already owned. Business use can require more charging, a reliable protective case, mobile data and eventual replacement. None of this makes smartphone acceptance unattractive by definition. It means that the owner should compare complete operating arrangements, including the time spent reconciling sales and resolving payment problems.
Settlement matters as much as acceptance
A trader can have a successful trading day and still struggle to pay a supplier if money becomes available later than expected. Before adoption, the owner should ask when completed transactions are normally settled, which days count, what happens around public holidays, and whether optional faster settlement has an additional cost. The answers belong in the provider’s current agreement and support material.
Daily records should distinguish sales, refunds, charges and deposits into the bank account. Adding up the day’s customer purchases and expecting an identical bank deposit can cause unnecessary confusion when fees or timing differences are involved. A simple reconciliation follows each stage: what was sold, which payments were completed, what adjustments occurred and which settlement covered those transactions.
For a small business, clarity can be more useful than elaborate software. A consistent sales reference, a saved provider report and a short daily review may provide a workable starting point. As volumes increase, the business can assess integrations with its bookkeeping process. The objective is to understand the money without repeatedly reconstructing events from messages and memory.
Receipts and refunds shape customer trust
The customer needs to know the amount charged and how to raise a concern afterwards. Before opening for trade, a merchant should understand which receipt options the provider supports and what information appears on them. A recognizable business name matters because an unfamiliar description on a bank statement can lead to avoidable questions. The name shown at checkout should make sense alongside the name used in advertising and bookings.
Refunds deserve their own rehearsal. Staff should know who is authorized to process them, how to locate the original payment and how the provider describes the refund’s progress. A refund request should not become an improvised transfer to banking details supplied in a rushed message. Following the provider’s documented process preserves a clearer record for both parties.
If a customer reports that an attempted payment appears twice, the merchant should check the transaction history before trying another charge or promising an immediate reversal. A pending entry and a completed transaction may require different handling. The provider’s support team can interpret the actual record; guesses made under pressure can compound the disagreement.
Security includes people and routines
A professional checkout should show the customer the correct amount and use the provider’s genuine application. Staff should obtain the app through the provider’s verified instructions and keep the device supported and updated. Sensitive customer information should not be copied into a notebook or photographed as a substitute for the payment service’s normal process.
Bank security guidance also matters around the business’s wider digital activity. Standard Bank’s phishing guidance warns that misleading communications can seek confidential information and recommends verifying suspicious requests through a trusted, independently obtained channel.[3] For a merchant, that principle applies to messages claiming that an acceptance account must urgently be repaired, reactivated or verified through an unfamiliar link.
An owner should also plan for a lost phone. The plan needs a way to contact the provider, protect access and continue communicating with customers. Where several employees take payments, access should follow the provider’s supported staff controls. Sharing a personal phone password widely can make it difficult to identify who performed a transaction or changed an important setting.
Connectivity should be tested where trade happens
A payment method that works at home may behave differently inside a shopping center, at a roadside stall or in a crowded event venue. Merchants should check the provider’s connectivity requirements and test in their actual trading location. They should never assume that a weak connection has left a transaction unpaid, or that a screen frozen during processing means it succeeded.
A useful fallback is a clearly understood alternative payment method, supported by an orderly record of what happened. The appropriate choice varies by business. The key is that staff should not invent a new process in front of a growing queue. Repeatedly asking a customer to tap without checking transaction status can create uncertainty for everyone involved.
Connectivity planning also concerns the rest of the phone. Incoming calls, notifications and an almost empty data balance can distract the operator. A short preparation routine before trading can cover battery level, application access and network availability. This is ordinary operational housekeeping, but it often determines whether the new payment experience feels dependable.
Accessibility is part of a good payment experience
Small screens and unfamiliar interactions can make checkout uncomfortable for some customers. A merchant should communicate the amount clearly, explain where to tap and allow time for the result. If the application requests a customer action, staff should follow the provider’s instructions while preserving the customer’s privacy. No one should need to announce a secret credential to a queue.
Language is equally practical. A trader serving customers in different South African languages can prepare a short explanation in the languages commonly used at the business. Even where the application itself has limited language options, the human explanation can reduce confusion. Staff should avoid treating a customer’s hesitation as proof that the person cannot use technology.
The business should also recognize customers who prefer another payment method. Smartphone acceptance adds an option; it does not automatically describe everyone’s needs. Keeping the payment conversation respectful can matter as much as transaction speed, especially in a small enterprise whose customers return because they know and trust the people serving them.
Measuring whether the change helps
A useful evaluation compares a few business measures before and after adoption. These might include completed sales, abandoned purchases attributed to payment limitations, average checkout time, settlement queries and staff time spent reconciling transactions. The measurement should cover comparable trading days where possible. A holiday market and a quiet weekday do not provide a clean comparison merely because they used different payment equipment.
Customer comments can explain the numbers. If people say that card acceptance made a purchase possible, record that observation without turning it into a guaranteed revenue forecast. If queues remain long, investigate whether preparation, packaging or payment is actually the bottleneck. Buying a different payment service cannot resolve a delay caused mainly by another part of the business.
The owner should also review failure cases. A method that completes most transactions but creates lengthy disputes on the remaining few may require better training or support. The aim is a reliable whole service: clear checkout, accurate records, predictable settlement and a manageable response when something goes wrong.
Choosing a service without chasing a headline
Before committing, a merchant can prepare a one-page comparison of the options under consideration. Record supported devices, all quoted charges, settlement timing, receipt options, refund procedures, staff access and support availability. Ask the provider to clarify ambiguous terms in writing. A cheaper headline rate may be less useful if an essential workflow is missing or if replacing the phone changes the overall cost substantially.
This comparison should also include the business’s existing arrangement. An owner who already has a dependable card terminal may find smartphone acceptance useful for deliveries or overflow rather than as a complete replacement. Another trader may prefer it as the main method. The right decision follows actual needs and a tested setup, rather than an assumption that newer equipment must always be better.
South Africa’s move towards more flexible acceptance tools is significant because checkout can travel with the person doing the work. The lasting value comes when the rest of the business travels with it: clear prices, respectful service, secure access and records that reconcile. A successful tap is the beginning of a completed business transaction, and the systems around it determine whether that convenience lasts.
Sources
[2] Nedbank. Tap on phone payments and the CoffeeToCar business example. Checked 23 September 2026.
[3] Standard Bank. Business Online phishing guidance. Checked 23 September 2026.