Compliance
Compliance & risk approach
Veritron is built as a platform foundation for regulated partnerships: verification, risk monitoring, customer lifecycle states and audit trails are part of the architecture rather than added later. This page describes how those controls work today.
Identity verification (KYC)
Customers submit an identity document and a selfie. Documents are stored in a private bucket that only the customer and reviewers can read through short-lived signed links. Verification moves through submitted, under review, approved, rejected or expired — customers can never set their own verification state.
Company onboarding (KYB)
Business workspaces capture legal entity details, directors and beneficial owners before business accounts can be used. Each submission carries a verification level and a screening state, so an external verification provider can be connected without changing the onboarding flow.
Transaction risk monitoring
Every money movement passes through a rule engine on the server. Rules cover large single amounts and velocity — too many payments, or too much value, in a short window. Matches raise a risk flag for review instead of silently passing.
Customer states
Accounts and customers have explicit lifecycle states: pending, active, restricted, suspended and closed. Restricted or suspended customers are blocked from moving money by the engine itself, not just by hidden buttons in the interface.
Audit trail
Verification decisions, customer state changes, card and account changes and every transaction are written to an append-only audit log with a timestamp and the acting user. Audit entries cannot be edited or deleted from the application.
Security model
All data access is enforced at the database level per user. Money movement happens only inside server-side routines with balance checks, idempotency keys to prevent duplicate execution, rate limits, and step-up verification for high-value transfers.
Scope and current status
Veritron is a demonstration product. It is not a licensed financial institution, it does not custody real customer funds, and balances, cards and payments in the app are simulated. Identity and company verification decisions are made manually by an internal reviewer; no third-party verification, sanctions-screening or payment provider is connected yet. Nothing on this page should be read as a certification, audit outcome or regulatory approval.
Questions about this approach can go to our contact page.