Skip to main content

Goldsky

Goldsky for Banking

Act on a sanctions update within minutes

Screen both sides of every stablecoin transfer against a watchlist your team can update instantly, and keep a record of every decision that stands up to an examiner.

Talk to our team

Read the guide

Highlights

  • Sanctions listings enforced within seconds of being added

  • Sender and recipient screened on every single transfer

  • Hits pushed to your case management system as they happen

  • Your watchlist and flagged transfers in your own database

Trusted by leading financial and blockchain teams

Public networks make continuous screening possible

Every stablecoin transfer is public and available in real time. What remains is operational: watching every flow as it happens, applying a sanctions change within minutes, and showing afterwards exactly what you did and why.

Change the list without touching the pipeline

A sanctions update reaches production as a row in a table rather than a deploy. The running pipeline applies it on its next batch, so you can tell an examiner a listing was enforced the day it was published.

Decisions you can defend

Each decision carries a full execution trace and an independently verifiable attestation produced in a trusted execution environment. When an examiner asks how you decided, you have a record rather than a reconstruction.

Regulated data stays yours

The watchlist and every flagged transfer live in your own database, which keeps regulated data inside your compliance boundary and makes residency and retention obligations tractable.

What continuous screening gives your compliance team

Screening, escalation and attestation running as managed infrastructure, with your watchlist and your provider in the loop.

Both counterparties screened

Every transfer is screened against the watchlist for both sender and recipient. Each hit identifies the matching party for your analysts.

A watchlist you update at runtime

Insert an address from any Postgres client and the running pipeline applies it on its next batch. No redeploy, and no re-sync of history.

Straight into case management

A webhook sink pushes each hit to your case management system one row at a time, while a Postgres sink keeps the durable record for audit.

Issuer enforcement events

A second pipeline decodes token-policy events into a ledger: updates, blocked transfers and burns, and pauses.

Verified and attested

A Compose task calls your sanctions or KYC provider with durable retries, then writes a tamper-evident attestation onchain through a gas-sponsored wallet.

One pattern across chains

Screening runs off transfer events, which every fungible token standard emits, so the same pipeline shape covers every chain and asset you support rather than one surveillance layer per rail.

Built for regulated environments

Controls, documentation and support your reviewers expect, ready before they ask.

AICPA SOC 2 Type II compliance seal

SOC 2 Type II

Independently audited controls, with reports available for your security review.

Dedicated infrastructure

Isolated compute and single-tenant options for your production workloads.

Granular access controls

Role-based permissions and audit logging across your whole organization.

Full observability

Monitoring, alerting and data-lineage visibility your auditors can follow.

Data residency

Cloud, on-premise or co-located, so data sits where your obligations require.

Regulation-ready data

Structured for MiCA, FATF Travel Rule and BSA/AML/KYC, with retention you set.

Deliver on your timeline

Banks, payment platforms and trading firms use Goldsky to get onchain products live in weeks. Our engineers work alongside yours from the first call through production.

1

Scoping call

We map your use case, the chains involved and the systems the data lands in, then give you a delivery estimate.

2

Technical deep-dive

Our engineers work with yours to confirm the design and the integration points.

3

Kickoff and go live

We stand up your integration and validate the data against your systems, ready for your team to build on.

Ongoing support

24/7 support in a shared channel with the engineers who run your infrastructure.

Book a scoping call

Build AML screening today

Everything your team (or AI agents) need to build a working solution today. Read the guide or copy the prompt below to have your agent help you ship it.

Hand this to your coding agent

I'm building stablecoin AML screening using Goldsky.

## Set up your tooling first

```bash
npx skills add goldsky-io/goldsky-agent
```

That installs to Claude Code, Cursor, Codex, Windsurf and 30+ other agents. Then connect Goldsky's MCP server at `https://docs.goldsky.com/mcp` however your tool does it — per-client setup is at https://docs.goldsky.com/mcp-server

Finally, use the `auth-setup` skill to install the Goldsky CLI if it's missing, and confirm I'm logged in before you start.

## What I'm building

Follow the Goldsky guide at https://docs.goldsky.com/solutions/compliance-monitoring

Help me:

1. Set up a Turbo pipeline that streams stablecoin transfers and screens both counterparties against a watchlist
2. Hold the watchlist in a Postgres-backed dynamic table we can update at runtime
3. Write flagged transfers to our database and push each hit to our case management webhook
4. Add a Compose task that verifies a hit with our sanctions provider and attests the decision onchain

## How to work

- Confirm dataset names yourself rather than assuming them
- Write the files, and create any Goldsky secrets the pipeline needs
- Validate locally — `goldsky turbo validate` for pipelines, a local task call for Compose
- Ask me for anything you can't determine: contract addresses, endpoints, thresholds, which database we're writing to
- Put credentials straight into Goldsky secrets, never into this chat

**Stop before deploying anything live**, then show me the commands to run.

AML screening

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to screen every flow in real time?

Bring your screening stack to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

Anything you can write to a table. OFAC and SDN lists, vendor feeds such as Chainalysis, TRM or Elliptic, and your own internal blocklists can all populate the same watchlist, so screening is not tied to a single provider.
Every verification runs as a Compose task with its inputs and outputs traced, and it can run in a trusted execution environment that attests the exact code executed. The decision is also recorded onchain, so the answer to "how did you decide to block this" is a record rather than a reconstruction.
No. The screening logic reads transfer events, so it works the same on any chain Goldsky supports and against any token standard. Some standards give you more to work with — TIP-20, for instance, emits issuer policy and blocked-transfer events, so on Tempo the issuer enforcement view comes for free — but nothing about the pattern depends on it.
No. Your team works in SQL against your own database: the watchlist is a table you insert into, and the flagged transfers are rows you query. Decoding chain data, keeping up with contract changes and running the indexing are ours to handle, which is why compliance teams tend to own this rather than waiting on a blockchain squad.
You own it, in a database you choose. Flagged transfers and attestations land in Postgres, MySQL or ClickHouse, and the watchlist itself is a Postgres table, hosted by you on Neon, Supabase, RDS or Cloud SQL, or by us. The schemas are yours and so is the retention policy, so regulated data stays inside your compliance boundary and your record never sits behind someone else’s export process.
Goldsky is SOC 2 Type II audited, with dedicated infrastructure options, role-based access controls and audit logging. We provide the report, DPAs and architecture documentation your reviewers ask for.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status