Alcinéo transit SoftPOS
A SoftPOS stack for gates and on-vehicle terminals. It supports the transit kernels needed for open-loop fare collection, such as Visa VCTKS, and runs transit payment on standard Android devices.
What is supplied
A SoftPOS stack for gates and transit operators. Supplied for embedding in terminals and SoftPOS, as an implementation that has passed certification.
Specifications and certifications
What transit use requires
| Aspect | Detail |
|---|---|
| Kernel | Support for transit programmes such as Visa VCTKS |
| Response time | The tap processing time a gate crossing requires |
| Offline | Risk handling when connectivity is lost, and settlement afterwards |
| RF characteristics | Stability outdoors, with metal enclosures and under continuous tapping |
For transit operators, measuring the RF characteristics and the response time matters. ProxiLAB Quest for waveform analysis and characterisation alongside it.
Choosing the right Alcinéo stack
Alcinéo does not make test equipment. It supplies software that is embedded in the device under test. The scope of certification differs by product, so the schemes covered and the extent of any valid approval are confirmed individually. Completeness increases along the path from component kernel, to SDK, to operations, to an industry-specific stack.
| Product | If you are considering |
|---|---|
| Level 2 contactless kernel | You want to embed an EMV kernel in your own terminal or SoftPOS, as a component |
| MPoC Software SDK | You want to implement software-based payment aligned with PCI MPoC |
| SoftPOS SDK | You want to turn a standard smartphone into a contactless payment terminal |
| A&M Backend Services | You want attestation and monitoring for SoftPOS operation, run from a backend |
| ★ SoftPOS for transit (this page) | You want a complete stack for gates and transit operators |
To verify this device under test
A terminal with this runtime embedded — the device under test — is tested at Level 1, Level 2 and Level 3 with the testers below. What is verified is not the runtime on its own but the device under test with the runtime embedded.