Soft POS

Traditional card acceptance often uses a dedicated terminal, whereas soft POS uses a general-purpose mobile device and its built-in capabilities for a contactless interaction. The merchant installs or uses a provider's approved application connected to an acquiring or payment service that can process and settle the transaction, and the customer taps an eligible card or wallet near a device with suitable near-field communication capability and an approved software configuration.

It should not be confused with a payment link, which asks the customer to pay on their own device, while soft POS accepts an in-person contactless tap on the merchant device. Not every phone works, because operating-system version, hardware, security settings and provider support matter, so check the exact supported device list.

Not every card works either: a tap-to-phone solution may accept contactless cards and wallets but not inserted chip or magnetic stripe payments without extra hardware. PIN handling varies, with some solutions supporting on-device entry under relevant security standards and others using different verification methods, so do not promise that every transaction can be accepted.

Security is central, and payment data should be handled by an approved solution, not a merchant's improvised app or manual card-number note. The PCI Security Standards Council describes standards for mobile payments on commercial off-the-shelf devices, and its MPoC programme addresses contactless data and PIN acceptance in approved solutions.

The US Payments Forum distinguishes tap-to-mobile, which can use built-in NFC, from a broader mobile POS setup that may require an added card reader, so check provider and acquirer approval, since a phone's ability to read NFC tags is not proof it may safely accept card payments as a merchant. Read the fees carefully, because processing charges, subscription prices, settlement fees and chargeback costs can vary, and no separate terminal does not mean no cost.

A simple calculation for a $200 payment with a 2.5% processing fee gives $195 before any other fees or taxes, which is an example and not a standard provider rate. Check settlement timing too, since a successful tap does not always put money immediately in the bank and provider terms govern payout.

Plan for connectivity, because a weak signal can interrupt authorisation or sync, so ask whether offline transactions are supported and what risk they carry. Issue receipts through an accepted method that supports returns or disputes, and train staff to show the amount before tapping, verify success and avoid repeated charges when a screen is slow.

Check payment limits as well, since scheme, issuer and local rules may require verification or another method for some amounts, and a backup acceptance route can help. Manage devices with lock screens, access controls, app updates and lost-phone procedures, and set a clear company policy for personal-device use.

Define the refund workflow with permission controls and a way to find the original transaction before reversing it, and reconcile transactions, fees, refunds and payouts with invoices and cash records, because a low-cost setup still needs normal controls. For an owner, soft POS changes the hardware used at the point of interaction, and delivery staff, pop-up shops and tradespeople may benefit from collecting payment where they meet customers, but its fit depends on security, supported payment methods, reliability and full processing cost.