Blockchain Forensics and Data
Multi-provider blockchain data, AML risk scoring, sanctions screening, price feeds, and on-chain transaction inspection — powered by leading specialist providers, surfaced through a single Studio API so your compliance and operations teams can query everything from one place.
Who this is for
| Persona | Typical inbound |
|---|---|
| Compliance or forensics team | ”What blockchain forensics providers do you integrate? Can we query AML risk and sanctions data through your platform?” |
| AML and sanctions screening operations | ”Do you screen wallet addresses against sanctions lists at the address level, not just the entity level?” |
| Cross-chain operations team | ”We need transaction data across multiple chains plus a price feed in one API surface.” |
| Internal compliance reviewer | ”Where does the forensic data behind our KYC reviews come from?” |
Not a fit if you require direct contractual access to the underlying providers (the contracts are KryptoGO’s; you query through us), need a forensics provider we do not currently integrate (we can scope adding one — not self-serve today), or need to bring your own provider account and have us proxy to it (we operate the provider relationships ourselves).
What you can ship today
A consolidated blockchain-data and forensics surface, available to your operations and compliance teams via the Studio API and inside the Studio console:
| Capability | What it covers |
|---|---|
| AML risk scoring on every transaction | On-chain wallet-address risk scoring inline with payment acceptance and treasury operations. Configurable per-organisation policy. |
| Address-level sanctions and PEP screening | Wallet-address screening against major sanctions lists. Complements the entity-level screening surfaced in KYB and KYC Workflow. |
| Multi-chain blockchain data | Address, transaction, block, and mempool data across major chains, including the UTXO chains (Bitcoin and others) that the rest of our wallet stack does not natively expose. |
| Tron account inspection | Account balances and on-chain reads for Tron-based assets, including the Tron USDT flows used in our payments and payouts surfaces. |
| Price feeds | Aggregated spot prices across major tokens and trading pairs, suitable for fiat-denominated quotes, statement generation, and merchant reporting. |
How it works
1. Your application or your compliance reviewer issues a query
against the Studio forensics API — for an AML risk score on a
counterparty address, for sanctions and PEP screening on an
address, for transaction history on a chain, or for a price.
2. The platform identifies the appropriate provider for the query
shape and routes the request to that provider behind the scenes.
Multiple specialist providers sit behind the same surface so
your team integrates once, not five times.
3. The provider's response is normalised against the documented
response shape and returned to your application.
4. For payment acceptance and treasury flows, the address-level AML
scoring runs inline at policy-evaluation time — no separate call
from your code is required.
5. For ad-hoc compliance investigations, your reviewer queries the
surface directly through the Studio console or the API.Custody model
Forensics and data queries are read-only. They do not move assets and have no direct custody implication. They operate alongside any of the four custody models — see Custody Options — and the same address-level AML scoring runs against incoming payments regardless of which custody surface receives them.
Compliance posture
Address-level AML risk scoring, sanctions and PEP screening, and inline policy evaluation run inside the regulated platform with the same posture as the rest: Taiwan VASP, ISO 27001, ISO 27701, SOC 2 Type II, Cure53 audit. Contractual relationships with the underlying specialist providers are KryptoGO’s; volume is reconciled against the underlying provider invoices. Address screening and risk scoring on every payment are configurable per-organisation policy — see Compliance and Certifications for the full posture.
Typical integration timeline
| Path | Bucket |
|---|---|
| Inline AML risk scoring on payments | Immediate — included in payment acceptance once your organisation is provisioned, no integration work required |
| Direct forensics API queries from your application or operations stack | Under one month — typically one to two weeks for a backend team |
| Add a provider we do not currently integrate | One to three months — scoped per provider |
Current scope
- Inline AML risk scoring on every payment, address-level sanctions and PEP screening, multi-chain blockchain data including UTXO chains, Tron account reads, and aggregated price feeds are in production.
- Per-provider rate-limit handling, formal proxy-availability service-level agreements, and request-level provider attribution for finance reconciliation are areas under active maturation. Partners with high-volume needs should reach our partnerships team to discuss SLA requirements.
- Webhook notifications when an address’s screening status changes — for example, a customer becoming sanctioned post-onboarding — are a roadmap item.
- Adding additional specialist providers, including additional forensics vendors, is supported on a per-engagement basis. Contact us to scope.
Talk to us
If your compliance or forensics team needs consolidated access to AML risk scoring, sanctions screening, blockchain data, and price feeds without procuring and integrating each specialist provider independently, reach our partnerships team via the address on www.kryptogo.tw .
Where to go next
- KYB and KYC Workflow — for the entity-level sanctions and PEP screening that complements address-level screening here.
- Accept crypto payments — for the payment surface where inline AML risk scoring runs by default.
- Customer Data Platform — for how on-chain data feeds customer segmentation.
- Compliance and Certifications — for the regulatory posture behind address-level AML and sanctions screening.