Start with scope
Plan the scope of your evaluation.
Tell us which product topics you want to evaluate, who would use them, and what coverage matters to your team. These details provide a basis for a pricing conversation; they do not establish a package or entitlement.
Product scope
Which FinTrace capabilities align with your immediate needs: monitoring, investigation, intelligence, API access, or combined workflows.
To confirmUser population
How many analysts, investigators, compliance officers, or system integrations will require access.
To confirmCoverage requirements
Which blockchains, asset types, and geographic jurisdictions are relevant to your operations.
To confirmVolume parameters
Expected transaction monitoring volume, investigation case load, or API call frequency.
To confirmIntegration context
Existing compliance infrastructure and data residency requirements relevant to your environment.
To confirmDeployment requirements
Cloud, on-premises, or hybrid deployment, matched to your security and operational needs.
To confirm- Business requirement
- Platform scope
- Coverage
- Integration
- Commercial discussion
This information enables a scoped commercial discussion aligned to actual operational requirements.
Illustrative scope builder
Sketch your requirements.
Use this builder to organize your thinking before a conversation with our team. Nothing you select here is submitted, saved, or shared, and it does not generate a quotation.
- Product topics
- To confirm
- Primary workflow
- To confirm
- Users
- To confirm
- Networks and assets
- To confirm
- Coverage
- To confirm
- Estimated volume
- To confirm
- Integration method
- To confirm
- Deployment
- To confirm
- Support
- To confirm
- Timeline
- To confirm
Illustrative requirements summary — not a quotation or commercial offer.
Product configuration
Explore the product topics.
Select the topics closest to your use case to keep them in mind for your conversation with our team.
- 01
Wallet Screening
Real-time wallet risk scores with entity context and address clustering.
Typical question: “Which risk factors matter most for your onboarding decisions?”
Explore - 02
Transaction Monitoring
Continuous monitoring against configurable thresholds, with alerts routed to reviewers.
Typical question: “What thresholds and alert routing does your team need?”
Explore - 03
Blockchain Investigations
Trace funds across chains, bridges, and DEXs with exportable evidence.
Typical question: “Which chains and bridge activity do you need to trace?”
Explore - 04
Entity Intelligence
Sourced entity attribution with a confidence indicator.
Typical question: “What confidence level does your review process require?”
Explore - 05
Sanctions Screening
Direct and indirect exposure to sanctions and watchlist sources.
Typical question: “Which watchlist sources are relevant to your jurisdiction?”
Explore - 06
Case Management
Assign, document, and hand over reviews with a full activity history.
Typical question: “How should reviews be assigned and handed over in your team?”
Explore - 07
Risk & Compliance API
Risk signals in your own systems over REST and streaming endpoints.
Typical question: “Which systems need risk signals integrated directly?”
Explore - 08
Reports & Audit Trails
Exportable reports pairing findings with tamper-evident history.
Typical question: “What audit and export format does your review process need?”
Explore
Commercial terms
Commercial information to confirm.
Specific commercial terms are confirmed only through executed agreements. No pricing, packaging, or entitlement is established by preliminary discussions, product documentation, or marketing materials. All commercial terms are subject to internal approval processes and legal review.
Illustrative review workspace, sample rows
Preparation
What to bring to a pricing conversation.
Describe your intended use, team size, required coverage, and any integration questions. No public price or free trial has been confirmed.
Illustrative preparation tracker for your own reference — nothing here is sent to FinTrace automatically.
Use-case definition
What decisions will FinTrace inform? Transaction approval, investigation, regulatory reporting, or risk assessment.
The intended decision shapes which capabilities and evidence matter most.
e.g. Transaction approvalTeam structure
Number of users, role types, and required permission levels.
User count and roles affect access structure and review workflow.
e.g. 12 analysts, 2 adminsCurrent state
Existing tools, gaps, and why FinTrace is being evaluated.
Understanding the current setup clarifies what needs to change.
e.g. Manual spreadsheet tracingCoverage needs
Priority blockchains, asset classes, and entity types.
Coverage scope is one of the main drivers of a commercial discussion.
e.g. Bitcoin, Ethereum, stablecoinsVolume estimates
Monthly transaction volume, case volume, or API throughput requirements.
Volume parameters inform which usage structure is discussed.
e.g. ~500 cases per monthTechnical requirements
Integration points, data residency needs, and deployment constraints.
Technical constraints affect deployment and integration options.
e.g. On-premises requiredProcurement process
Decision timeline, stakeholder approvals required, and budget parameters.
Procurement steps affect how quickly terms can be finalized.
e.g. Legal review, then financeSecurity review
Information security questionnaire requirements or vendor assessment processes.
Security review timelines often run in parallel with commercial discussion.
e.g. Vendor security questionnaireDeployment context
Technical details that can influence a commercial discussion, all subject to confirmation for your environment.
- CloudManaged and scalable
- On-premisesInside your perimeter
- Air-gappedIsolated environments
- Data residencyRegion-specific hosting
- Security reviewVendor assessment support
- Access modelRole-based permissions
Integration context
Ways the platform can connect to your systems, discussed as part of scoping.
- Web applicationBrowser-based access
- REST APIDirect system integration
- Streaming endpointContinuous data feeds
- Existing case systemsCase management interoperability
- AuthenticationEnterprise identity support
- Expected throughputSized to your volume
Inclusions
What may be included.
Product and feature names referenced on the FinTrace website describe capabilities that may be available through commercial engagement. These descriptions do not constitute an offer or confirmation of bundled packaging.
Specific inclusions, exclusions, and optional add-ons are defined only in executed agreements.
| Requirement | Requested scope | Confirmation status | Contract reference |
|---|---|---|---|
| Product modules or feature sets | To confirm | Subject to review | — |
| Blockchain and asset coverage | To confirm | Subject to review | — |
| API access and rate limits | To confirm | Subject to review | — |
| Support tiers | To confirm | Subject to review | — |
| Response commitments | To confirm | Subject to review | — |
| Training and onboarding | To confirm | Subject to review | — |
| Export and reporting | To confirm | Subject to review | — |
| Custom deployment | To confirm | Subject to review | — |
| Integration services | To confirm | Subject to review | — |
To initiate a pricing and scope conversation, contact sales@fintraceintelligence.com with the information outlined above. A FinTrace representative will respond to schedule a discovery call.
Process
How a commercial discussion unfolds.
- 01
Describe the use case
What decisions the platform needs to inform, in your own words.
- 02
Identify products and coverage
Which product topics and coverage areas are relevant.
- 03
Review users, volume, and integrations
Who needs access, at what volume, and how systems connect.
- 04
Confirm security and deployment requirements
Deployment model, data residency, and security review needs.
- 05
Align procurement and legal review
Internal approvals and timelines on both sides.
- 06
Receive applicable commercial terms
Terms specific to the confirmed scope are shared.
- 07
Finalize an executed agreement
Commercial terms take effect once the agreement is signed.
Evaluation access
Evaluation access is reviewed individually.
- Individual review. Requests for platform evaluation are reviewed on a case-by-case basis.
- Confirmation required. Access and scope are confirmed before an evaluation begins.
- Separate terms. Evaluation access, where granted, is governed by separate evaluation agreements.
- No general trial. No general free trial or self-service evaluation is confirmed.
Illustrative request outline, not a submission form
Frequently asked
Pricing: questions and answers.
Is public pricing available?
No. Pricing depends on deployment scope and volume, so it is not published on this website. Request a demo and the team will walk through options for your requirements.
Is there a free trial?
No general free trial or self-service evaluation is confirmed. Evaluation requests are reviewed individually, and any access granted is governed by a separate evaluation agreement.
What information is needed for pricing?
Your intended use, team size, required coverage, expected volume, and any integration or deployment requirements. This scopes the conversation to your actual needs.
Can several products be evaluated together?
Product topics can be discussed in combination. Which combinations are relevant, and how they are scoped commercially, is confirmed during the conversation.
Does coverage affect commercial scope?
Coverage requirements, such as relevant blockchains, asset types, and jurisdictions, are part of the information used to scope a commercial discussion.
Are API and platform access priced separately?
How API access and platform access relate commercially is confirmed as part of scoping your requirements; it is not stated generally on this website.
Which deployment options can be discussed?
Cloud, on-premises, and air-gapped deployment can all be discussed. Availability for your environment is confirmed during the conversation.
When are commercial terms considered confirmed?
Only once reflected in an executed agreement. Website content and preliminary discussions do not establish binding commercial terms.