Security
Security approach.
Design intentions for the platform, with a clear status table of certifications and launch readiness.
Status table
Certification and launch status.
| Item | Status |
|---|---|
| Architecture principles | In development |
| Live payment environment | Not launched |
| PCI certification | Not claimed |
| Independent security audit | Not claimed |
Security model
Snapix is designed as the experience and orchestration layer. Regulated payment activity is planned to run through established infrastructure with server-confirmed transaction state.
Payment data boundaries
Snapix does not intend to store raw card numbers, CVVs or PINs. Where partners support tokenization, Snapix intends to rely on those capabilities rather than handling raw payment credentials.
Forms & data
This website uses two separate form systems. The five general forms (Contact, Support, Customer Early Access, Merchant Interest and Partner Inquiry) are submitted through Web3Forms for processing and delivery — they do not share the Snapix application backend. Career Applications use the private Snapix / PocketBase application backend with Cloudflare Turnstile anti-bot verification. The two systems do not share the same backend or bot-protection system.
Authentication
Customer and merchant account access is planned around secure authentication. Live product auth is not offered on this marketing site.
Merchant permissions
Owner and cashier roles with least-privilege permissions and staff activity records are part of the planned merchant model.
API security & webhooks
Provider callbacks and APIs are planned to be validated through controlled server-side paths — not trusted solely from a device.
Logging & incident handling
Operational monitoring and logging are planned to support reliability and incident response. Formal public incident SLAs are not published pre-launch.
Data minimization
Website forms collect only what is needed for the workflow (interest, partnership, careers, support). Career resumes are stored privately in the Snapix application backend.
Infrastructure responsibilities
Authorization, settlement, KYB/KYC and chargeback infrastructure sit with payment partners under the planned split. See How it works.
Report a security concern about this website or planned product design to support — do not include live secrets in email.
support@snapixmoney.com