BSA / AML · Early access
Prove your BSA/AML program to your bank partner — without exposing customer records.
Your bank partner is accountable for your compliance program, so it asks for evidence constantly. ZTZK gives it proof on every transaction — checkable by the bank, with customer data kept where it is.
The basics
BSA / AML, explained.
For fintechs — and the bank partners behind them.
The Bank Secrecy Act and anti-money-laundering rules require financial institutions to detect and report financial crime: screening against OFAC sanctions lists, verifying customers (KYC), and filing currency transaction and suspicious activity reports. Reg E adds consumer protections for electronic transfers.
When a fintech offers accounts or payments through a bank partner (often called a sponsor bank), the bank stays responsible for the program. It oversees the fintech’s controls — and examiners oversee the bank.
ZTZK runs OFAC, BSA, KYC and Reg E checks on every transaction inside the fintech’s environment and gives the bank partner a signed proof of each result — not the customer data behind it.
Outcomes
What ZTZK proves for BSA / AML.
Every transaction, not a sample
Screening and reporting rules run on each transaction and each result is signed — so the program is proven continuously, not reviewed monthly.
Customer data stays with the fintech
Your bank partner receives proofs, not records. It confirms OFAC, KYC and BSA checks passed without learning who the customer is.
Rules compliance can read
Each rule is a short, readable contract — what’s forbidden, what’s guaranteed — that compliance officers can review. Not a black box.
Scope
What’s covered
The core of a fintech compliance program, expressed as rules that run on every transaction.
- OFAC
- Sanctions screening for senders and recipients against current lists.
- BSA
- Currency transaction reporting thresholds and structuring patterns.
- KYC
- Verification level matched to transaction size, with refresh requirements.
- Reg E
- Disclosure before authorization, error resolution and unauthorized transfers.
- Fraud
- Fraud checks, with the approved model version verified on each decision.
How it runs
BSA / AML, step by step.
- Step 01
Write the rules
Your compliance team and ZTZK express your program as readable contracts — sanctions, thresholds, KYC levels.
- Step 02
Prove each transaction
Checks run where the transactions are, inside the fintech’s environment.
- Step 03
The bank verifies
Your bank partner verifies the proofs on its side — no data exchange, no monthly spreadsheet.
What a rule looks like
Readable by compliance. Provable by math.
Each rule is compiled, hash-pinned and signed. Change the rule and the hash changes — so an examiner can see exactly which version was in force for any transaction.
FORBID recipient IN sanctions_list
GUARANTEE kyc_level >= required_level
THRESHOLD amount >= ctr_threshold
→ TRIGGER ctr_reportFAQ
BSA / AML questions, answered
Can our bank partner verify our controls without seeing customer data?
Yes — that is the point. Zero-knowledge proofs confirm a check ran and passed without revealing the customer records behind it.
Can examiners see which version of a rule was applied?
Yes. Every rule is hash-pinned, and each proof references the exact rule version in force when the transaction ran.
Does ZTZK replace our BSA officer or independent testing?
No. Your BSA officer still owns the program, and independent testing is still required. ZTZK gives them — and your bank partner — evidence they can verify rather than take on faith.
We use a model to score fraud. Can ZTZK cover that?
In early access. ZTZK can verify that the approved model version made each decision, supporting model risk management under SR 26-2 / OCC 2026-13. See AI governance.
Request access
Prove your BSA / AML controls.
We're onboarding a small number of early teams. Tell us about your BSA / AML program and we'll show you evidence that stands up on its own.
We use your email only to reply to your request. Privacy policy
✓ Request received. We'll be in touch.