Support & Resources

Frequently Asked
Questions

Everything you need to know about deploying Uvik UPoS Transit SoftPOS across your mobility ecosystem.

Product & Platform

Uvik UPoS is India's first and premier SoftPOS solution globally certified specifically for transit fare collection. It transforms standard NFC-enabled Android smartphones into contactless payment terminals, enabling NCMC (National Common Mobility Card) acceptance for metro, bus, cab, and mobility platforms — eliminating the need for dedicated hardware terminals.

What sets Uvik apart: Uvik is the only company globally holding RuPay Terminal Specification V2.0 certification covering Transit Modes 91 through 94. No other SoftPOS vendor — in India or internationally — holds this transit certification at the time of writing.

The platform operates on a white-label SaaS model, allowing transit authorities, banks, fintechs, and aggregators to deploy the solution under their own brand with complete control over the fare collection workflow.

The platform supports the complete RuPay NCMC transaction stack across both retail and transit contexts:

Online SaleReal-time authorisation via acquiring network
Offline SaleStore-and-forward for poor/no connectivity
Balance EnquiryCheck NCMC card balance on-device
Balance UpdateSync updated wallet onto NCMC card
Service CreationTransit service provisioning on card
Money Add (Cash)Top-up NCMC card balance via cash
Money Add (Account)Top-up via linked bank account
Retail Sale / VoidStandard EMV contactless payments

Yes. Uvik UPoS is built on an offline-first architecture featuring store-and-forward capability — a requirement for in-vehicle and rural deployments where network coverage is unreliable.

Conductors can process NCMC card payments in underground tunnels, on remote rural bus routes, or during network outages. Transactions are queued securely on-device and automatically reconciled with Uvik Cloud once connectivity is restored. No transaction data is lost.

This is directly addressed by RuPay Transit Modes 93 and 94 (offline single-tap) and 92 (offline entry-exit), all of which Uvik UPoS is certified for.

Tap-to-Onboard (TTOD) is a digital merchant activation model that eliminates physical logistics for terminal deployment. The process works as follows:

  1. The aggregator or transit operator onboards the merchant/operator entity onto their system.
  2. The aggregator registers the merchant on the acquiring switch to retrieve a unique MID/TID (Merchant/Terminal ID).
  3. Unity's onboarding APIs register the merchant and terminal against that MID/TID.
  4. Individual conductors or agents are onboarded via API onto the Uvik system, using the same MID/TID to complete their transactions — no physical key injection or hardware setup required.

This enables a conductor's smartphone to become a live NCMC-accepting terminal in minutes, with no hardware to ship or configure.

Certifications & Compliance

Uvik holds a comprehensive enterprise certification stack covering both network/scheme certifications and PCI security standards:

PCI MPoC PCI DSS v3.2.1 PCI PIN PCI SSF-S3 PCI SSF-SSLC RuPay Terminal Spec V2.0 NCMC L2 Visa Ready SoftPOS Mastercard TTP EMVCo Contactless Google Play Integrity
All certifications are fully in-house — Uvik designed, developed, and certified its own L2 kernels for Visa, Mastercard, and RuPay. This is not a licensed or OEM kernel — it gives Uvik complete control over kernel updates, certification renewals, and transit-specific customisations.

RuPay Terminal Specification V2.0 defines specific terminal profiles for transit acceptance. Uvik is the only SoftPOS vendor certified for all transit modes:

ModeDescriptionUse CaseStatus
Retail 21Attended Online OnlyStandard retail POS
Retail 22Attended Offline with Online capabilityRetail with offline fallback
Retail 23Attended Offline OnlyPure offline retail
Transit 91Attended Online OnlyMetro gates, online fare
Transit 92Attended Offline with Online capabilityBus — mixed connectivity routes
Transit 93Attended Offline with Online (Single-Tap)Conductor single-tap, hybrid
Transit 94Attended Offline OnlyRural bus, tunnels, no connectivity

Source: NPCI RuPay Kernel Product List V2.0. No other SoftPOS solution currently holds Transit 91–94 certification.

PCI MPoC (Mobile Payments on COTS) is the PCI Security Standards Council framework that governs the security of contactless card acceptance on commercial off-the-shelf Android devices — i.e., standard smartphones used as payment terminals.

Without PCI MPoC certification, a SoftPOS product cannot be legally deployed for live card acceptance on Android devices. It is the foundational certification for the entire Tap-on-Phone category. Uvik's MPoC certification applies to Android COTS devices; iOS and Windows are outside the MPoC scope.

MPoC covers the security of the entire solution stack: the mobile application, SDK, backend server (covered by PCI DSS), PIN entry (covered by PCI PIN), and monitoring mechanisms (covered by PCI SSF-S3 and SSLC). Uvik holds all five of these interdependent certifications in-house.

Note: The Card Reader Extension uses 3DES DUKPT encryption and is separately certified under PCI PTS SCRP 5.x for hardware PIN security.

Technical & Integration

The Uvik UPoS SDK uses an intent-based integration model — a low-code approach where the partner's Android application triggers payment transactions by launching the UPoS SDK via Android Intent calls, without needing to manage complex payment flows directly.

The integration sequence is:

  1. Partner app makes an Intent-based transaction call to the UPoS SDK.
  2. Partner app simultaneously calls the Merchant Host to generate an Intent Hash (security token).
  3. The Intent Hash is passed to the UPoS SDK to authenticate the request.
  4. SDK completes the payment and returns the result to the partner app.
The SDK is distributed via Private Maven repository and embedded into the partner's existing Android application. Play Integrity / App Signing must be configured on the Play Store for security attestation. The entire backend (IA-Unity) is hosted on GCP under PCI DSS scope.

User authentication on the SDK supports MPIN-only, OTP-only, or Biometric + Device Authentication modes, configurable by the deploying partner.

Uvik UPoS (native SoftPOS) requires:

Android 9+ for Transit/NCMC deployments
Android 10+ for standard retail SoftPOS (CCAvenue TapPay)
NFC Chip required for contactless card tap
Active SIM required for network-dependent modes
Google Play Services required for Play Integrity attestation

iOS and Windows are not supported — PCI MPoC certification applies exclusively to Android COTS devices.

For fleets using non-NFC Android devices (Android 7.0+), the Uvik Card Reader Extension — a Bluetooth/USB-C peripheral — enables EMV chip-and-PIN and contactless acceptance via the same UPoS SDK. The Card Reader uses 3DES DUKPT encryption and is PCI PTS SCRP 5.x certified.

Settlement and reconciliation flows through the IA-Unity backend via SFTP:

  1. Payment Gateway / Acquiring Switch sends settlement files to IA-Unity via SFTP.
  2. IA-Unity parses and reconciles transaction data against its records.
  3. Reconciled settlement files are pushed to the Aggregator / Transit Operator via SFTP.
  4. T+1 settlement is credited to the merchant/operator account.

The UPort dashboard provides shift-wise reconciliation, conductor-level accountability, route-wise analytics, and full audit trails. Real-time transaction monitoring is available via the Monitoring module within IA-Unity.

IA-Unity is the GCP-hosted (PCI DSS) application server that forms the core backend of the Uvik platform. It provides:

AttestationDevice & app integrity verification
MonitoringReal-time transaction surveillance
Crypto Key MgmtECC 256, RSA 2048/3072 key lifecycle
Remote Key InjectionSecure key provisioning (non-transit)
Merchant OnboardingAPI + bulk + TTOD flows
Switch IntegrationAPI-based & ISO 8583 H2H
ReconciliationSFTP settlement file parsing
DashboardAnalytics, reporting, audit trails

Acquiring switch integration supports both REST API-based and ISO 8583 Host-to-Host (H2H) integration patterns. The architecture is switch-agnostic — Uvik can connect to your existing acquiring infrastructure. Partner HSM integration is also supported for partners with on-premise HSM requirements.

Deployment & Operations

A standard deployment — from initial requirements through sandbox integration to a fully tested production fleet rollout — typically spans 6–8 weeks:

WeekPhaseActivities
WK 1–2Requirements & SetupSDK access, sandbox environment, requirements analysis
WK 3–4Integration & CustomisationSDK integration, white-label branding, backend API setup
WK 5–6Testing & CertificationUAT, network certification, security testing, Play Store submission
WK 7+Production LaunchGo-live, fleet rollout, conductor training

Actual timelines subject to partner readiness, lab availability, and network certification schedules. Transit deployments requiring new acquiring switch integrations may have additional lead time.

No. Uvik UPoS completely eliminates the need for legacy POS hardware. Conductors use their existing NFC-enabled Android smartphones (Android 9+) as the payment terminal. Digital activation via TTOD means there are no devices to ship, configure, or physically inject with security keys.

Hardware cost eliminated per terminal: ₹10,000 – ₹40,000 procurement + ₹2,000–₹5,000 installation + ₹3,000–₹8,000 annual maintenance. Over a 3-year fleet lifecycle, this translates to ₹25,000–₹60,000 per terminal saved — purely on hardware TCO.

For fleets where conductors use non-NFC devices, the Uvik Card Reader Extension provides a compact Bluetooth peripheral option at a fraction of a full hardware POS cost.

Commercial & Partnerships

Uvik UPoS is available to enterprise and institutional partners — not directly to individual merchants or conductors. The platform serves:

Banks & AcquirersOffer transit SoftPOS acquiring to transport clients under your brand
State Transport Corps (STUs)Deploy NCMC acceptance across your bus fleet with conductor apps
Metro & Rail OperatorsExtend NCMC to service counters, top-up kiosks, mobile ticketing
Fintechs & AggregatorsWhite-label the full platform to serve your government/mobility clients
Mobility AggregatorsIntegrate NCMC across cab, auto, bike-sharing, and parking services
ISVs & OEMsEmbed transit payments into your fleet management or ticketing software

All commercial enquiries, pricing discussions, and partnership negotiations are handled directly by Rahul Hirve, Founder & CEO at rahul@uvik.in / +91 88845 55449.

Didn't find your answer?

Schedule a technical deep-dive with our team — we'll walk through your deployment scenario in detail.