Goldsky

Know when customer deposits arrive

Goldsky watches the deposit addresses you give your customers and tells your app when money comes in, so exchanges, neobanks and payment apps can credit accounts.

Talk to our team

Read the guide

At a glance

New addresses are a row in a table
Your app gets a webhook when funds arrive
Deposits are stored with sender, amount and token
Running balances for the token you track

Trusted by exchanges, wallets and payment companies

Credit customers without watching the chain

You keep the list of addresses. Goldsky checks incoming transfers against it and sends you the matches.

New customers need no deploy
Adding a customer means inserting their address into a Postgres table. The pipeline picks it up on its own.
Your app hears about deposits
A webhook goes to your app when a watched address receives funds. Your code decides what to do next, whether that’s crediting the account or holding it for review.
Support can answer tickets
When a customer asks where their money is, support can look up the deposit by address and see who sent it, how much and when.

Deposit detection on Goldsky: address lists, webhooks and balances

Your team sets up a Goldsky pipeline that compares token transfers on the chains you pick against your address list and writes the matches to your Postgres database.

Address list in Postgres

Add and remove addresses with SQL. The running pipeline reads the table as it changes.

Webhooks

Point the pipeline at an endpoint and it calls your app for each matched transfer.

Deposit table

Each match is saved with the token, sender, recipient, amount, time and transaction hash, so you can join it to your ledger.

Balances

The same pipeline can keep a balance per address for the token you track, adding deposits and subtracting withdrawals.

More chains, same setup

Goldsky’s transfer datasets share one format across chains. Adding a chain is a new source in the same pipeline.

Past deposits

Start with new transfers, or load older ones first if you want history for addresses you already have.

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 deposit detection today

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

Open in Claude Code

I'm building onchain deposit detection for a payments product 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/deposit-detection

Help me set up a Turbo pipeline that:

1. Maintains a dynamic table of the customer deposit addresses we watch
2. Filters a curated token transfers dataset down to transfers received by those addresses
3. Lands the matches in our database as a queryable index
4. Fires a webhook on arrival and maintains a running balance of the tracked token per address

## 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.

Automate crediting for crypto deposits

Bring your chains and address volume to a 30-minute scoping call and leave with a concrete plan and timeline.

Talk to our team

Read the guide

Frequently asked questions

What do we need to run ourselves?

A Postgres database for the results. Goldsky runs the pipeline. Neon, Supabase, RDS, Cloud SQL and self-hosted Postgres all work.

Does deposit detection replace our ledger?

No. Your ledger stays the system of record. Goldsky writes incoming deposits to your database, and your ledger reads them from there.

Can we start with one chain and add more later?

Yes. Each chain is a source in the pipeline, and Goldsky’s transfer data uses the same format on every supported chain.

Can we see deposits from before we started?

Yes. The pipeline can load past transfers to your addresses before it starts following new ones.

We only watch a few addresses. Do we need a pipeline?

Probably not. The Goldsky Feeds transfers API returns an address’s incoming transfers with USD values, without a pipeline or database. A pipeline makes sense once you watch many addresses or want webhooks.