Security

Designed for customers whose security teams will audit us.

Txnworks processes financial transaction data on behalf of banks, PSPs, and e-commerce risk ops teams. We design controls to the standard those customers' security questionnaires ask for — and we state clearly what we do and do not claim.

Three pillars

Data isolation, encryption, access controls.

Data Isolation

Customer transaction data is stored in logically isolated namespaces. Cross-tenant data access is architecturally prevented — not just access-controlled. Each API key maps to a single tenant namespace.

Encryption In Transit + At Rest

All API traffic requires TLS 1.3 — TLS 1.2 and below are rejected. Data at rest is encrypted using AES-256. Optional field-level encryption for PII fields (name, email, address) available on Scale plans.

Access Controls

API keys are scoped (score-only vs full-access). IP allowlisting supported for all plans. Key rotation via dashboard or API with zero-downtime overlap window. Audit log of all key operations exported on request.

Data handling

What we store, for how long.

The specifics matter to your legal and compliance teams. Here they are without the vague language.

Scoring payloads The full transaction payload (POST /v1/score body) is NOT stored after the score response is returned. Signal vectors are derived and the raw payload is discarded.
Score records transaction_id, score, label, contributing_signals[], and latency_ms are retained for the duration of your plan's score history window (7 days Starter, 30 days Growth, 90 days Scale).
Behavioral signals Aggregated signal state (e.g. velocity counts per device_id) is retained for 90 days to support historical signal computation. Raw event data is not retained beyond signal aggregation.
Feedback labels Outcome labels (POST /v1/feedback) are retained for the life of the contract and used for model retraining. Labels are linked to transaction_id only — not to the original payload.
PII handling Name, email, and address fields submitted in scoring payloads are used for identity consistency signal computation and immediately discarded. We do not build PII profiles. Field-level encryption during transit available on Scale.
Control list

Security controls by the fact.

Transport TLS 1.3 required. All endpoints reject TLS 1.2 and below. HSTS enforced.
Encryption at rest AES-256-GCM for all stored data. Key management via cloud KMS with quarterly key rotation.
API keys Keys scoped to score-only or full-access. Rotation via API or dashboard with 24h overlap window. Compromised key revocation immediate with no downtime.
IP allowlisting Available on all plans. Requests from non-allowlisted IPs return 403 before hitting scoring logic. Supports CIDR ranges.
Audit log All key operations, threshold configuration changes, and feedback submissions are logged with timestamp, actor, and source IP. Available for export on request.
Compliance posture Designed with SOC 2 Type II controls in mind. Formal SOC 2 audit is planned. We do not claim certification we have not yet obtained.
Responsible disclosure

Found a vulnerability? Tell us.

We ask that security researchers give us reasonable time to investigate and fix issues before public disclosure. We will not pursue legal action against researchers acting in good faith.

Contact [email protected] — use subject line "Security Report"
Response time Initial acknowledgement within 2 business days. Status update within 7 days. Fix timeline communicated within 14 days of confirmed severity.
Scope txnworks.com and the Txnworks scoring API. Third-party services integrated with Txnworks are out of scope.
Excluded Social engineering attacks against employees, denial-of-service testing, and automated scanning tools generating excessive traffic are out of scope.