Goldsky

Screen stablecoin transfers against your watchlist

For banks, issuers and payment firms: Goldsky checks the sender and recipient of each stablecoin transfer against a list your compliance team keeps, and sends any match to your case system.

Talk to our team

Read the guide

At a glance

Both sides of a transfer are checked
Edit the watchlist without a code release
Matches go to your case system
Every flagged transfer is kept in your database

Trusted by banks, fintechs and blockchain teams

Run screening from your own watchlist

Stablecoin transfers happen on public networks. Goldsky reads them as they’re recorded and compares each one with the list you maintain.

Edit the list without a release
Adding an address is adding a row to a table. The running screen reads the table on its next batch, with nothing to redeploy.
A trail for each match
If you pass matches to your screening provider through Goldsky Compose, each request and response is logged. Your analysts still make the decision.
Stored in your database
The watchlist and every flagged transfer sit in your Postgres database, where your existing access rules apply.

Sanctions screening on Goldsky: watchlists, alerts and audit records

Goldsky reads the transfers, matches them against your list and keeps a record. Your analysts and your screening provider make the calls.

Sender and recipient

Both parties are checked, and each match says which side was on the list.

A watchlist table

The list is a Postgres table your team fills, from a sanctions list, a vendor feed, an internal blocklist or all three.

Case management alerts

Each match is sent to your case system as its own alert and saved to a table for audit.

Issuer actions

Some stablecoins let the issuer block transfers or pause the token. Goldsky can record those events next to your matches.

Provider checks

A Compose task can send each match to your sanctions or KYC provider, log the answer and record the outcome on a blockchain.

More networks

The screen reads the standard transfer events stablecoins emit, so the same setup carries over to other networks Goldsky supports.

Where Goldsky fits next to KYT and policy tools

Table 1. Where Goldsky’s screening pipeline sits relative to KYT and attribution vendors and policy enforcement tools.
Layer	Example providers	What they own	What Goldsky adds
Attribution and risk scoring (KYT)	Chainalysis, TRM Labs, Elliptic	Linking addresses to real-world entities, plus sanctions and risk lists	Streams the transfers these vendors screen into your own database, decoded and checked against your watchlist
Policy enforcement	Predicate, Blockaid	Rules that block a transaction before it executes	Records issuer actions such as freezes and blocklists next to plain transfers, for tokens that publish them
Screening data and audit record	Goldsky	Watchlist table, flagged transfers, alerts to case management and a logged record of each provider check	Not applicable

of stablecoin transfers fall under $3,000 on every rail measured: 82–99%
Ethereum stablecoin transfers is address-poisoning spam, across 100,137 clusters: 1 in 6+

Source: The Fintech Guide to Stablecoin Data Infrastructure

Built for regulated environments

SOC 2 Type II, dedicated and on-premises deployment, and access controls for banks, payment companies and trading firms.

SOC 2 Type II

Goldsky maintains SOC 2 Type II compliance.

Dedicated infrastructure

Single-tenant infrastructure in Goldsky-managed cloud accounts, with static IPs for allowlisting, on Enterprise.

On-premises and BYOC

Run the full stack on-prem or in your own cloud, so data and compute stay inside your boundary.

Access controls

Role-based access on every plan, plus SAML SSO and audit logs on Enterprise.

Complete, validated data

Every block is checked for completeness before delivery, and daily validation repairs any gaps.

Data for your compliance program

Transfer and identity data for MiCA, Travel Rule and BSA/AML: Goldsky supplies it, your team owns the program.

Deliver on your timeline

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

Scoping call

We learn what your digital asset product needs and give you a delivery estimate.

Proof of concept

Our engineers and yours build a working version on your own data.

Kickoff and go live

We launch it together and check the numbers against your systems.

Ongoing support

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

Step 1
Scoping call
We learn what your digital asset product needs and give you a delivery estimate.
Step 2
Proof of concept
Our engineers and yours build a working version on your own data.
Step 3
Kickoff and go live
We launch it together and check the numbers against your systems.
Ongoing
Ongoing support
24/7 support in a shared channel with the engineers who run your infrastructure.

Book a scoping call

Build stablecoin AML screening today

Copy the prompt into your AI coding agent and build a working version today.

Open in Claude Code

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.

Screen every stablecoin transfer you touch

Bring your screening stack to a 30-minute call. We’ll map it to Goldsky and leave you with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

Does this replace our blockchain analytics vendor?

No. Analytics vendors provide address attribution and risk scores. Goldsky checks transfers against your list, and their data can be part of that list.

Does Goldsky decide whether a transfer is sanctioned?

No. Goldsky flags transfers that touch an address on your list. Your compliance team reviews each one.

Which lists can we screen against?

Any list you can load into a table. A sanctions list, a vendor feed and your own blocklist can all go into one watchlist.

What do we keep for each match?

The flagged transfer, saved in your database. If matches go through Compose, you also keep a log of what your provider was asked and what it said.

Where does the data live?

In your Postgres database. Goldsky writes flagged transfers there, and the watchlist is a table in the same database.

The Fintech Guide to Stablecoin Data Infrastructure Proof of reserves and treasury Securities compliance

Goldsky for fintech Compose