We build the application, backend, provider integration, and operational tooling behind SoftPOS and tap-to-phone products, and support the certification work they require. Supported devices, countries, processors, and payment methods depend on the implementation you choose.
SoftPOS is software that lets a supported commercial device accept contactless payments using its built-in NFC, without a separate card reader. Whether a given device, operating system, country, processor, or payment method is supported depends on the SoftPOS implementation selected. Not every Android device can accept contactless payments, and an approval for one implementation does not transfer to every device, region, or deployment.
A customer taps a card or wallet on the supported device. The implementation reads and protects the data, and the transaction is routed through the provider and processor.
Support is defined by the implementation: device models, operating system versions, and regions. We confirm compatibility before scoping.
PCI's Mobile Payments on COTS (MPoC) framework is the security specification SoftPOS solutions are commonly assessed against.
Integrating an approved provider's SDK is different from certifying a new solution. We scope the two separately.
The right path depends on your devices, regions, timeline, and how much of the solution you need to own.
Build your application and backend around an existing provider's SoftPOS SDK. The provider holds the underlying solution; we engineer everything around it.
Configure and brand a proven white-label SoftPOS solution, with the customization scope agreed up front. Customizations can change approval scope.
Design a new SoftPOS solution for requirements that existing options do not meet. This is a larger engagement and includes the security and certification work a new solution requires.
Already have an application and need help with EMV Level 3 certification? See EMV Level 3 certification services or managed certification.
Included work depends on what is contracted.
Payment screens, sale and refund flows, and the business logic around them.
Merchant onboarding and boarding integrations with the provider or processor, where included.
Receipts, transaction reporting, and reconciliation support.
Backend services and APIs that connect the application to your systems and the provider.
Provisioning, configuration, monitoring, and support tooling, separating what we build from what a provider supplies.
Applications for commercial Android devices with their own supported SoftPOS implementation. See the section below.
Integration is not the same as certification of a new solution. Solution providers, qualified labs, processors, and other approval parties each have a role, and Paying.co does not grant approvals.
| Area | Paying.co | Solution provider | Client, labs, and processors |
|---|---|---|---|
| Approach and architecture | Recommends an approach and designs the application and backend | Provides SDK, documentation, and platform capabilities | Confirms requirements, provider relationship, and decisions |
| Application and backend | Builds and tests as contracted | Operates its own services where applicable | Owns the application per the agreement; supplies content and access |
| Security and certification | Engineers to the requirements and coordinates certification work as contracted | Holds and maintains its own solution approvals | Holds processor and acquiring agreements |
| Evaluation and approval | Prepares and coordinates; does not grant approval | Provides applicable listings and letters | Labs, processors, and other parties conduct evaluations and grant approvals |
Learn what MPoC certification is. For a new solution that needs MPoC certification, see the MPoC Certification Program, which sets out its own prerequisites, scope, and terms.
SoftPOS has a phone side and a backend side. Provisioning, monitoring, updates, support, and security services are scoped by what we build and what a provider supplies.
Feasibility, then provider and architecture selection, integration or development, testing and applicable approvals, pilot, and rollout.
SDK integration and a new solution build are very different in scope. Provider fees, external dependencies, assumptions, and ongoing obligations are listed in the scope.
Engineering QA, provider validation, and processor requirements are separate workstreams.
Learn what drives the cost of a custom payment app. Review payment application testing beyond approved and declined transactions. See why provider SDK restrictions can decide between native Android and cross-platform frameworks.
Paying.co develops and integrates payment applications for commercial Android devices using supported device-specific SoftPOS implementations. We connect payment acceptance with business workflows, supported peripherals, and backend systems.
SoftPOS can fit when the merchant is mobile or when a separate terminal is impractical, subject to the implementation's device and region support.
Drivers accepting payment at the door on a supported device.
Temporary retail and on-site service teams.
Servers using one device for ordering and payment.
Drivers and conductors accepting payment on the device they already use for dispatch.
Mobile clinics, in-home care, and traveling specialists.
Merchant onboarding that can start as an app download where the provider and boarding process allow.
Tell us what you're building and how ready you are. Include target countries, acquiring or provider relationships, intended devices, required payment flows, existing application status, and whether you want SDK integration or a new solution.
Tell us about your project — we route you to the right specialist.
Share your devices, countries, provider relationships, and whether you need SDK integration or a new solution. We will come back with a scoped plan.