Boring where it counts. That’s the point.
Payments reward paranoia. Triceratops is engineered like money software should be: minimal surface area, maximum audit trail, and safeguards enforced in code — not in a handbook.
// architecture facts — the way the system is built, not aspirations
How it’s built
The safeguards, plainly stated.
Tokenized at the edge
Payment details entered on our pay pages go directly to our certified payment partners and come back as tokens. Triceratops stores tokens and truncated identifiers — never full card numbers. That keeps the sensitive surface area near zero, by design.
Recorded, honored, auditable
Merchants warrant consent to contact their customers, and the platform keeps the receipts: what was agreed, when, and how. Every message identifies its sender. Every channel supports instant opt-out with confirmation.
Hold less, protect more
Encryption in transit, access controls, and a simple retention principle: keep what the service and the law require, then delete or de-identify. We don’t sell personal information — full detail in our Privacy Policy.
Guardrails in code
Tone controls approved by the merchant, reply-aware pausing, quiet hours enforced in the scheduler, and human review available on every message. First-party only: the agent speaks in the merchant’s name, about the merchant’s own current receivables.
Known and disclosed
A short, current list — payment infrastructure, cloud hosting, AI provider, email/SMS carriers — each bound by contract to use data only in service to Triceratops. Available on request at [email protected].
Found something? Tell us.
Responsible disclosure is welcome and appreciated: [email protected] with subject "Security disclosure." A human reads it the same business day. Formal certifications (SOC 2) are on our roadmap as we scale.
Questions an underwriter would ask? Ask them.
Partners, processors, and security-minded merchants: we’ll walk you through the architecture directly.
Talk to us