Goldsky

Goldsky for Payments

Detect customer deposits the moment they arrive

Exchanges, neobanks, on-ramps and payment apps use Goldsky to watch a large, constantly changing set of receiving addresses, and to react the instant assets arrive.

Talk to our team

Read the guide

Highlights

New deposit addresses watched the moment you add them
Your product notified the instant a deposit arrives
A searchable record of every deposit, in your own database
Running balances maintained per address, updated on arrival

Trusted by leading financial and blockchain teams

Deposit detection without the indexing infrastructure

A managed index you point at the address set you already maintain, so a new customer address starts being watched the moment your systems create it.

Issuing an address stops being a deploy

A new deposit address is a row your systems insert, picked up within a second or two. No release, no ticket, and nobody from the data team in the loop each time you onboard a customer.

Reliability you can put your name on

A 99.99% uptime SLA, dedicated infrastructure options and 24/7 support from the engineers who operate it. Missed or delayed deposits are the fastest way to lose customer trust.

A record you can reconcile against

Every matched transfer is stored with its full transaction detail, so finance, support and compliance can answer "where is my money" without digging through a block explorer.

Everything a production deposit flow needs

The building blocks of deposit detection, running as managed infrastructure.

A live address set

Watched addresses live in a Postgres table you control. Insert or delete at any time and the pipeline picks up the change within seconds.

Webhook alerts on arrival

Fire a webhook the moment a watched address receives funds, so your product can credit the customer while they are still looking at the screen.

A queryable index

Matches land in your database with token, sender, recipient, amount, block number and transaction hash, ready to join against your own ledger.

Running balances

Maintain a running balance per address in the same pipeline, so your team does not have to recompute totals from raw history.

Normalized transfer data

Curated, cross-chain transfer datasets give you one consistent schema instead of per-chain parsing for every network you add.

No polling infrastructure

Rather than polling thousands of addresses every block, the pipeline filters a managed stream down to the addresses you care about.

Built for regulated environments

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

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.

Scoping call

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

Technical deep-dive

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

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.

Scoping call

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

Technical deep-dive

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

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

Deposit detection

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to ship deposits your customers can trust?

Bring your use case to a 30-minute scoping call and leave with a concrete plan and timeline.

Talk to our team

Read the guide

Frequently asked questions

Do we have to run any indexing infrastructure?

No. Goldsky runs the indexing. You provide a Postgres database, either hosted by Goldsky or your own on Neon, Supabase, RDS or Cloud SQL.

Can we start with one chain and expand later?

Yes, and most teams do. Curated transfer datasets give you one consistent schema across networks, so adding the second chain is a source added to the pipeline rather than a second integration built from scratch. You can prove the flow on the chain that matters most to you before committing the rest of the roadmap.

Can the data land in our warehouse?

Deposits stream into Postgres or ClickHouse for querying, and into Kafka, Pub/Sub or object storage when you need to fan them out further. If your analytics stack runs on Snowflake, Databricks or BigQuery, we can deliver there too, so deposit data lands next to the rest of your finance reporting.

Does this replace our ledger?

No. Deposits are delivered into the database you already run, and your ledger stays the system of record. Goldsky supplies the onchain detection and the queryable history beneath it.

What do we get for a security and compliance review?

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 security and procurement teams need.

Where does the deposit data live, and who owns it?

You own it, in a database you choose. The index and the running balances sit in your own Postgres or ClickHouse, hosted by you or by us, under schemas you control, and the same stream can land in Snowflake, Databricks or BigQuery alongside the rest of your finance data. Your deposit history is a table you hold, not a report you request.