Use a computer

For full performance and fluidity, please open Pay Engineers on a desktop or laptop. On mobile, the experience is limited — especially authenticated sections and advanced tools after login.

Payment Infrastructure

SoftPOS / Mobile Acceptance

Tap-to-pay on commercial devices

Presentation

Overview

SoftPOS turns a standard NFC-enabled Android device into a certified card acceptance terminal, removing the need for dedicated point-of-sale hardware for many merchant use cases. Pay Engineers builds SoftPOS solutions end to end, from the on-device acceptance application through to the backend processing and terminal management layer, engineered to meet the scheme security requirements that make this category viable.

SoftPOS is deceptively difficult to get right. The security architecture, particularly around PIN-on-glass entry, must satisfy strict scheme certification requirements, and the acceptance experience needs to work reliably for merchants who are often on the move, in areas of patchy connectivity, with limited technical support available in the moment.

We build with this operational reality in mind from the outset, rather than treating field conditions and connectivity issues as edge cases to handle after launch.

Who This Is For

  • PSPs and acquirers wanting to offer merchants a low-cost alternative to traditional card terminals
  • Field sales, delivery and service businesses that need to accept card payments away from a fixed checkout
  • Micro-merchants and pop-up retailers for whom dedicated hardware is not commercially justifiable
  • Businesses exploring SoftPOS as a way to reduce cost and complexity in their terminal fleet

What You Get

  • A tap-to-pay user experience on commercial Android devices, designed for speed and clarity at the point of sale
  • Terminal fleet operations tooling so you can provision, monitor and deactivate devices across your merchant base
  • Offline resilience allowing transactions to be captured and safely queued when connectivity drops, then processed once restored
  • Receipt and tipping functionality covering digital receipts and configurable tipping prompts where relevant

Technical Approach

The acceptance application is built natively for Android, integrating a certified SoftPOS SDK to handle the cryptographic and PIN-on-glass requirements that scheme certification demands. This part of the stack cannot be improvised: it must be built and tested against the specific certification requirements of the SoftPOS SDK and processor combination you use, and we manage that certification process as a core part of delivery.

The backend, built on Laravel, handles terminal fleet management, transaction processing coordination and reporting, with an HSM or equivalent secure cryptographic service protecting sensitive key material. Offline transaction queuing is implemented with careful attention to duplicate prevention and eventual consistency, so that a connectivity gap never results in a merchant being paid twice or a transaction silently lost.

Delivery Process

  • Discovery of your merchant use cases, target devices and existing processor or acquirer relationship
  • SoftPOS SDK and partner selection, followed by architecture design for the acceptance app and backend
  • Sprint-based build of the acceptance application and fleet management backend in parallel
  • Scheme and SDK certification testing, including PIN-on-glass security requirements and offline scenarios
  • Pilot rollout with a controlled merchant group before wider fleet deployment

Outcomes and Benefits

  • A materially lower-cost acceptance option for merchants compared with dedicated card terminal hardware
  • Reliable acceptance even in the field conditions that traditional terminals struggle with
  • Centralised operational control over a growing terminal fleet without proportional support overhead
  • A certified, scheme-compliant foundation you can extend with new device types or acceptance features over time

Technologies

Android SoftPOS SDK Laravel backend HSM

FAQ

The solution runs on standard commercial Android and, where supported by the certification body, iOS devices, using the phone or tablet's NFC hardware to accept tap-to-pay transactions without a dedicated card terminal. This significantly reduces the hardware cost and logistics burden compared to distributing physical terminals, particularly for micro-merchants, delivery riders or pop-up retail. We scope device compatibility against the certified device list from your chosen SoftPOS certification and processing partner, since not every device model is automatically eligible. The app itself is built to your brand and integrated into your existing merchant or field application if you have one.
SoftPOS solutions operate under specific PCI security standards for software-based PIN entry and contactless acceptance, and we build the application to meet the certification requirements of your chosen SoftPOS platform provider, since the security certification itself is typically performed by a specialised vendor rather than built from scratch. Sensitive card data handling is isolated within a certified secure component of the application, keeping the surrounding merchant app largely out of card data scope. We coordinate directly with your certification partner during development so the integration meets their requirements the first time, avoiding costly re-certification cycles. This division of responsibility is standard practice across the SoftPOS market.
Yes, we typically integrate SoftPOS acceptance as an SDK or module within your existing merchant, point-of-sale or field service application, rather than shipping a separate standalone payment app that merchants would need to switch between. This keeps the payment step within your existing user experience and business workflow, for example combining an order or job completion flow directly with payment collection. We handle the technical integration with your chosen SoftPOS certification provider's SDK and expose a simplified interface to the rest of your application. This integration approach is usually what makes adoption practical for merchants who are already using your app daily.
Contactless transaction limits are set by scheme and regional rules rather than by us, and the application enforces those limits along with any additional risk-based limits you choose to apply on top. We support standard contactless debit and credit cards from major schemes, and where relevant, mobile wallet taps such as Apple Pay or Google Pay presented to the device. PIN entry on the device for higher-value transactions above the contactless limit is supported where your certification partner's platform provides it, extending usability beyond small transactions. We configure limit and card type support to match your target market's scheme rules during implementation.
A first release integrated into an existing merchant app, using an established SoftPOS certification partner's SDK, typically takes 2 to 4 months, with the majority of the timeline driven by the certification partner's own onboarding and testing process rather than our development work. Building a standalone SoftPOS app rather than integrating into an existing one adds some time for the surrounding user experience, but the payment acceptance core remains the same effort. We recommend confirming your certification and processing partner early in the engagement, since their requirements shape several technical decisions. Pilot rollout to a small merchant group before full launch is a common and recommended step we build into the plan.

Similar services