Separated store workspaces
Operational requests are scoped to the signed-in business and active store workspace so one tenant cannot use ordinary application access to reach another tenant's records.
Security at V-POS
Practical safeguards for store operations and business data.
Security is part of how V-POS handles identities, permissions, store boundaries, register activity and subscription billing.
Controlled staff access
Employee roles, permissions, PIN sessions and protected owner functions limit who can view or perform sensitive store actions.
Protected register activity
Open register shifts are tied to registered stations and terminal identities. Checkout requests are validated on the server before a sale is recorded.
Portable business records
Owners can export eligible store data. V-POS also preserves operational records needed for sales history, receipts and register reporting.
Payments and card information
V-POS subscription checkout and payment-method management are handled through Stripe-hosted billing pages. V-POS does not store the full payment-card number used to pay a V-POS subscription.
For in-store card sales, merchants use their configured external payment terminal or supported integration. Merchants remain responsible for configuring and operating their payment hardware and providers correctly.
Responsible claims
This page describes controls available in V-POS. It does not claim SOC 2, PCI DSS or another third-party certification. Questions or suspected security issues can be sent to support@vyominc.com.
See how V-POS fits your store.
Explore the working demo or start a 30-day trial without a credit card.