Authentication and sessions
User access uses server-managed sessions rather than client-only authentication.
Developers / Security
VirtusCloud applies server-side authorization, user-scoped data access, hosted payment handling, input validation, and controlled credentials across the current application architecture.
Talk to our teamCurrent application controls are active. Formal certifications and enterprise SSO are not claimed as generally available.
What changes for your team
Protect account sessions
Scope data by user and business
Keep card entry hosted
Validate sensitive operations
Capabilities
User access uses server-managed sessions rather than client-only authentication.
Protected operations check the signed-in user and relevant business scope before data access.
Stripe-backed hosted checkout handles sensitive card entry outside the VirtusCloud portal.
Server-side actions validate operational input before database or payment changes.
Service credentials remain in the server environment rather than being embedded in client interfaces.
No blanket certification or enterprise SSO claim is made; current requirements must be reviewed with support.
Planned — contact supportEnd-to-end workflow
Establish a server-managed session before protected application access.
Check the user, role, and business ownership relevant to the requested record.
Reject malformed or disallowed values before they reach the database or payment layer.
Use protected services and hosted payment flows for credentials and card entry.
Where it fits
Keep customer and administrative interfaces behind the correct host and authorization boundary.
Restrict queries and mutations to the signed-in user’s permitted business context.
Avoid collecting raw card details inside the application interface.
Questions
No such certification is claimed on this page. Ask support for the current security and procurement position.
The current online payment flow uses Stripe-hosted checkout for sensitive card entry.
Continue exploring