How Fintra checks each action, maps it to your frameworks and keeps the evidence
Every consequential action passes through the same six stages.
A person’s action or an AI agent’s, each stage gives the same answer for the same inputs, and each leaves evidence behind.
The relationship map
The action is checked against who and what it touches.
- Each event is checked against a map of people, accounts, systems and AI agents before anything decides.
- Fixed detection rules and a risk score produce a plain statement of what happened, the same every time.
- Dangerous combinations show up as one chain (a stale login, a new vendor, an unregistered agent) that no single alert would show.
- For each action Fintra works out what it would reach if it were wrong.
The map is seeded today with data from early customers. It decides, records and can stop an action; it never acts on its own.
Frameworks and controls
One control, mapped to many frameworks.
- The control library covers 84 frameworks and 111 controls: SOC 2, ISO 27001, HIPAA, GDPR, SOX, PCI DSS, NIST AI RMF and more.
- Each control maps to every framework it satisfies, so one piece of evidence answers many obligations at once.
- Each checked action is tied to the specific controls it touches.
- Your standing is kept current all year, not measured once a year.
The sealed record
Each checked action is written to a record that cannot be changed.
- As soon as an action is checked, it is added to an append-only record, mapped to its controls.
- Each entry carries a seal of the one before it, so recomputing the record shows any edit or deletion.
- Evidence fills in the controls it maps to, so preparing for an audit is a search instead of a quarter of screenshots.
- People and AI agents are recorded the same way.
The verdict
A verdict and a trust score on every action.
- Trust combines identity, compliance and financial signals into one verdict it can explain: allow, ask for more proof, hold or block.
- Every action gets a trust score with its factors shown. The same inputs always give the same number.
- Policies tie the verdict to a named owner and a stated reason.
Stopping an action outright happens only where an AI agent calls a tool, and it is opt-in. Everywhere else, consequential actions stay drafts until a person confirms them.
The decision list
Decisions ranked by what matters now.
- Pending decisions across finance, identity, compliance and AI are ranked by risk, urgency and reach.
- Each one comes with a recommended verdict an approver can act on.
- The approver acts once, and the outcome goes straight into the record.
The reach of an action
See what an action reaches before you approve it.
- The same map shows which people, accounts, agents and data an action reaches.
- It answers what breaks if this is wrong before anyone signs off.
- Dangerous chains are marked on the map, not buried in a log.
One control
ExampleTwo-step sign-in enforced
counts toward
- SOC 2
- ISO 27001
- HIPAA
- GDPR
- SOX 404
- PCI DSS
- NIST AI RMF
The record
Intact| Entry | Seal of the one before |
|---|---|
| Bank change proposed | 0000 0000 |
| Trust score 42 | a71c 9f2a |
| Verdict: hold | b03e 9f2b |
| HR approval, sealed | c9d4 9f2c |
What it reaches
ExampleWhat is real, said plainly
- Trust gives a verdict and seals evidence on every action. Stopping an action outright happens only where an AI agent calls a tool, and it is opt-in. Everywhere else, consequential actions are drafts until a person confirms them.
- The relationship map is seeded today with data from early customers; the example shown here reflects that, not a live customer.
- Scoring gives the same answer for the same inputs, and every score shows its factors.
- We align to recognised frameworks and share evidence on request. We never publish audit dates, certificate numbers or customer logos that do not exist.
One action, end to end: a bank change the day before payroll.
An employee changes their payroll bank account. Here is what Trust does with it.
An employee changes their payroll bank account.
- Fintra runs the books, payroll and payments, so Trust sees the change the moment it happens.
- It is checked against the map before anything decides.
The trust score drops.
- Account trust dropped
- Identity confidence is low
- A new bank account, and payroll runs tomorrow
- Every factor in the score is shown
The payment is held for HR approval.
- Trust can stop it where an agent calls a tool, or hold it as a draft for a named approver.
- A person approves before money moves; the change waits either way.
Handled, with the evidence kept.
- Evidence mapped to the controls it satisfies, SOC 2 and more
- An append-only, sealed entry that can be recomputed
What is AI governance for finance?
AI governance for finance is deciding, as it happens, whether an action taken by a person or an AI agent should be allowed against financial systems, and then proving that decision afterwards. In Fintra, Trust does this in one pass: it checks every action against a map of people, accounts, systems and agents and works out what the action reaches; maps it to the specific controls in 84 frameworks; gives it a trust score and a verdict (allow, ask for more proof, hold or block); ranks the decision for a person; and seals the whole thing into an append-only record. Consequential actions are drafts until a person confirms them: an AI agent can propose, but a named person approves before anything irreversible posts.
Security, compliance and privacy, topic by topic
Platform security
The controls that protect your books at every layer.
- Security at FintraHow Fintra secures SMB financial data: layered defenses, tenant isolation, hardened cloud infrastructure, employee controls, and incident response.
- Encryption & Key ManagementFintra encryption in depth: TLS 1.2+ in transit, AES-256 at rest, managed key rotation, secrets handling, and hash-chained integrity for audit records.
- Access Control & IdentityHow Fintra controls access: role-based access control, least-privilege defaults, SSO and MFA, session security, and managed non-human identities for AI.
- Audit Logging & EvidenceFintra audit logging: append-only, hash-chained event trails covering every human and AI action, with retention, export, and evidence-grade integrity.
Compliance and privacy
Frameworks we align to and the rights you keep over your data.
- Compliance & CertificationsFintra’s compliance posture: alignment to SOC 2 Trust Services Criteria, ISO 27001 practices, and GDPR: continuously monitored and evidenced by Fintra Trust.
- Privacy & Data ProtectionFintra’s privacy practices: data minimization, defined retention windows, DPA availability, subprocessor transparency, and customer rights over data.
- Data Residency & StorageWhere Fintra stores and processes data: US-hosted Postgres on Supabase, encrypted backups, cross-border transfer safeguards, and regional roadmap.
- Integration SecurityHow Fintra secures integrations: OAuth with scoped consent, least-privilege API tokens, webhook signing, vetted partners, and MCP tool-call firewalling.
AI trust
How AI is governed, approved, and held accountable in Fintra.
- AI Governance & Runtime ControlHow Fintra governs AI at runtime: AgentFence approval gates, an MCP and tool-call firewall, hash-chained trust ledger, and shadow-AI discovery for SMBs.
- AI Model GovernanceHow Fintra governs AI models: vetted providers, no training on customer data, prompt and response logging controls, model versioning, and evaluations.
- Responsible AIFintra’s responsible AI commitments: human-in-the-loop approval for consequential actions, explainable outputs, usage metering, and honest limitations.
Operations and disclosure
Uptime commitments and how to reach the people who can act.
- Availability & StatusFintra availability commitments: a 99.9% uptime target, published maintenance windows, incident communication via status page and email, and DR objectives.
- Contact Our Security TeamHow to reach the Fintra security team: security@fintrahub.com for vulnerability reports, privacy requests, and due diligence, with clear response SLAs.
- Vulnerability Disclosure PolicyFintra’s coordinated vulnerability disclosure policy: scope, safe harbor for good-faith research, how to report, and public acknowledgment for researchers.
Questions about Trust
What is AI governance for finance?
AI governance for finance is deciding, as it happens, whether an action taken by a person or an AI agent should be allowed against financial systems, and then proving that decision afterwards. In Fintra, Trust does this in one pass: it checks every action against a map of people, accounts, systems and agents and works out what the action reaches; maps it to the specific controls in 84 frameworks; gives it a trust score and a verdict (allow, ask for more proof, hold or block); ranks the decision for a person; and seals the whole thing into an append-only record. Consequential actions are drafts until a person confirms them: an AI agent can propose, but a named person approves before anything irreversible posts.
Should this AI agent be allowed to act?
That is the question Trust answers on every consequential action. Reading a report is not the same as posting a journal entry or moving money. Trust looks at the action in context (the map, any dangerous combinations, what the action reaches) and, where an agent calls a tool, checks the call against an allowlist and argument rules and sends financially material actions to a person for approval. Low-risk reads go through so agents stay useful; irreversible or money-moving actions wait for a named person, and both the proposal and the approval are recorded.
What is the trust score?
The trust score is a number Trust works out for every consequential action from weighted signals: identity confidence, account and vendor trust, compliance standing and Fintra’s financial context. The same inputs always produce the same score, and every score comes with its factors, so a reviewer sees why an action was trusted or held. A second score rolls the per-action scores up for the whole organisation.
How does the sealed record work?
Every checked action (the request, the tool call, the verdict and the approval) is written to an append-only record in which each entry carries a cryptographic seal of the entry before it. Changing or deleting any entry breaks the chain, and the record can be recomputed at any time to prove it is intact. Each entry is also mapped to the controls it satisfies across frameworks, so daily work becomes audit evidence instead of being reconstructed later.
What does the relationship map do?
Before anything decides, Trust checks each event against a map of people, accounts, systems and AI agents, runs fixed detection rules, and works out a risk score and what the action reaches. It finds dangerous chains of conditions that each look harmless alone, which single-signal tools miss. Today the map is seeded with data from early customers; it decides, records and can stop an action, but it never acts on its own.
How is this different from a SIEM or a compliance dashboard?
A SIEM or a dashboard tells you that something happened. Trust decides whether it should happen, before it does, scores it, holds or stops it, and proves it. Because it sees actions through Fintra, which runs the money, it grounds identity, fraud and compliance signals in real financial events (pending approvals, payment and payroll changes, new vendors and bank changes) that a standalone monitoring tool never sees. Every item in its list ends in a decision.
One finance briefing a week
Security and compliance updates included. Unsubscribe from any issue.
Running a security review?
We keep a standing evidence package ready for due diligence: questionnaire answers, the DPA, the subprocessor list and SOC 2 alignment documents.