Build your payment experience around the commercial Android device you choose. Paying.co develops business applications and integrates supported device-specific SoftPOS implementations, peripherals, and backend systems into a complete operational workflow.
COTS means commercial off-the-shelf. The term does not by itself establish payment approval status, and not every commercial Android device includes a SoftPOS implementation.
We work with commercial Android devices that ship with, or are supported by, their own SoftPOS implementation. Support is confirmed per combination of device, firmware, SDK, provider, and region. A successful deployment on one model or version does not establish support for every device in a family, so we publish no universal device list.
| Device and model | Android and firmware | SoftPOS implementation or SDK | Provider, processor, region | Peripherals | Status and limitations |
|---|---|---|---|---|---|
| Confirmed per engagement | Confirmed per engagement | Confirmed per engagement | Confirmed per engagement | Confirmed per engagement | Delivered, supported, or requires assessment |
This is what we confirm for every engagement before committing to scope.
Included work depends on what is contracted. These are the areas we typically cover.
Native Android applications built for the device, its screen, and its operating environment.
Sale, refund, void, tips, receipts, and the business rules around them, within provider capabilities.
Printers, scanners, cameras, and other components, where the device and its SDKs support them.
Connections to your existing backend, POS, or ERP, and to payment provider services.
Transaction reporting, reconciliation support, and administrative tools where contracted.
Provisioning, configuration, and update approaches for fleets, using confirmed tools.
For broader application engineering see Mobile App Development and Custom Development.
Your application calls the supported SoftPOS SDK or service. The provider's implementation handles card acceptance. Paying.co does not supply the underlying SoftPOS implementation in every engagement.
Card reading, cryptography, attestation, and the interfaces and result codes the SDK exposes are supplied and operated by the SoftPOS provider or device manufacturer. Their documentation defines what is possible.
We integrate those interfaces into your application, design the workflow around them, handle results and interruptions, connect the backend, and test the combined system.
Printers, scanners, cameras, and other built-in components, used only where the specific device and its SDKs support them.
External printers, scanners, or other accessories, where compatible with the device and its payment implementation. We confirm each during scoping.
Learn how SDK restrictions can decide between native Android and cross-platform frameworks.
An illustrative view. The exact data flow, and where sensitive payment data travels, depend on the provider's implementation and are confirmed in technical review for each project.
Understand payment gateway integration scope, timelines, and dependencies.
Provisioning, app distribution, updates, configuration, and monitoring. We name specific tools only when they are confirmed for your project, and define support boundaries in writing.
Application QA, device and provider validation, and processor requirements are separate workstreams with separate owners.
Any certification or evaluation depends on the device, the provider, the processor, and what you customize. A customization can change the approval scope.
Using a commercial device, an existing SDK, or an existing implementation does not automatically satisfy all requirements for a new deployment. Not every COTS integration needs a new MPoC solution certification project. Learn what MPoC certification is. Where a new solution certification does apply, see the MPoC Certification Program.
Review payment application testing beyond approved and declined transactions. Engineering QA does not replace provider or processor test requirements.
The typical division of work. Final responsibilities are set in the agreement for each engagement.
| Area | Device manufacturer | SoftPOS provider | Paying.co | Client |
|---|---|---|---|---|
| Device and platform | Supplies the device, operating system, firmware, and built-in components | Documents supported devices and versions | Confirms fit for the workflow during scoping | Selects and procures devices |
| SoftPOS implementation | Provides components the implementation relies on | Supplies and operates the SoftPOS SDK or service and its documentation | Integrates the supported implementation into the application | Holds the provider relationship and access |
| Application and workflows | Not applicable | Not applicable | Designs, builds, integrates, tests, and maintains as contracted | Defines workflows; supplies decisions and content |
| Backend and peripherals | Supplies built-in peripherals and drivers | Not applicable | Builds backend connectivity and supported peripheral integration as contracted | Supplies existing systems, interfaces, and external peripherals |
| Agreements and approvals | Not applicable | Sets provider requirements | Supports readiness; coordinates as contracted | Holds processor, acquiring, and provider agreements; processors and acquirers grant approvals |
Maintenance and support options are agreed with the engagement. Learn what drives the cost of a custom payment app.
Where the device manufacturer or a provider offers a supported SoftPOS SDK or service and you have access to it, we can integrate it into your application. We confirm the device, firmware, SDK version, provider, and region during scoping. We do not assume every commercial Android device includes SoftPOS.
Support is confirmed per combination. A successful deployment on one model or version does not establish support for every device in a family. We confirm the device model, Android and firmware version, SDK version, provider or processor, and geography before committing to scope.
Where the device and its SDKs expose those components, yes. We confirm which built-in and external peripherals are supported on your specific device during scoping.
Yes, where your systems expose the interfaces needed. We build the backend connectivity, reporting, and administration that the engagement includes. Scope, dependencies, and hidden integration work are covered in our payment gateway integration article.
It depends on the device, the SoftPOS provider, the processor, and what you customize. Application testing, device and provider validation, processor requirements, and any applicable certification or evaluation are separate workstreams. Using a commercial device or an existing SDK does not automatically satisfy every requirement for a new deployment, and a customization can change the approval scope.
We design provisioning, distribution, update, configuration, and monitoring around the tools you use or the tools we agree on for the engagement, and we define support boundaries in writing. We name specific tools only when they are confirmed for your project.
Ownership, documentation, and maintenance terms are set in the agreement for each engagement. We confirm them before work begins.
Include what you have. Gaps are fine; we will help identify them.
Tell us about your project — we route you to the right specialist.