Choosing AML Tooling for a FinTech or Crypto Business: Criteria and Questions
A product that moves money quickly has different needs from a branch-based firm. This guide sets out the trade-offs and the questions worth putting to any vendor before you integrate.
Event-driven or batch: a trade-off, not a contest
Event-driven checks
Fits when: A customer action, such as a sign-up, a payment instruction or a wallet withdrawal, triggers a check before the flow continues.
What you gain: Risky activity can be held or declined while the customer is still in the journey.
What it costs you: Your product now depends on the vendor being reachable at the moment of the action, so you must decide what happens when it is not.
Batch checks
Fits when: A scheduled job re-screens a customer base or reviews a day of activity after the fact.
What you gain: Simpler to run, easier to retry, and easier to schedule around your own systems.
What it costs you: Something problematic may already have completed by the time the batch notices it.
The architecture side of this choice, including retries and the evidence each pattern leaves, is covered in real-time versus batch AML screening.
Four areas to press a vendor on
Speed, expressed as questions
- How long does a check take in the slowest ordinary case, and will the vendor commit to that in writing?
- What does your user see while a check runs, and what is the fallback if it is slow?
- Does the vendor publish a status history that you can read before you sign?
False positives and tuning effort
- Who adjusts matching and rule thresholds, you or the vendor, and how long does a change take to reach production?
- Can you replay old cases against a proposed change before it goes live?
- How are analyst decisions fed back so repeat noise falls over time?
Audit trail and explainability
- For each alert or block, can you see which data and which rule produced it, in words a reviewer can read?
- Is every analyst action stamped with who, when and why, and can it be exported?
- Can a supervisor reconstruct a decision long after the vendor changed its models?
Webhooks and API reliability
- Are webhooks signed, retried and idempotent, and how do you find events that were never delivered?
- What happens to in-flight checks during the vendor's maintenance or an outage?
- Is there a sandbox that behaves like production, and are API changes announced with notice?
Crypto and digital-asset analytics
Businesses that hold or move virtual assets usually add a category of tooling that reads public ledgers and rates the wallets and counterparties involved. Examples, in alphabetical order, are Chainalysis and Elliptic. They are named as examples only: not an endorsement, not tested by us.
- Which chains and tokens are covered, and how quickly is a newly popular one added?
- How is a risk rating explained, and can a reviewer see the path that led to it?
- Can alerts flow into the same case process your fiat-side tools use?
Product and company names belong to their owners and are used only to identify them.
Where FRAMEWORQ fits
Once the tools are chosen, someone must show that they are run properly: who owns each control, when it was last reviewed and where the evidence sits. That is the governance layer, and it is the only job FRAMEWORQ does here. It does not screen, monitor or trace. See the AML software landscape for how the categories fit together and the AML audit readiness guide for how evidence is organised, or use the vendor evaluation checklist when you are ready to compare quotes.
Frequently Asked Questions
Should a FinTech use real-time or batch AML checks?
Do crypto businesses need different tooling?
Does FRAMEWORQ replace any of these tools?
Is this page a recommendation of vendors?
Find the gaps. Close them. Prove it.
Stay audit-ready with FRAMEWORQ, our compliance readiness platform. Free 3-month trial, and a pilot if you want one.