Skip to main content

Goldsky

Goldsky for Payments

Know where every dollar is while it is moving

When USDC moves natively between chains it is burned on one side before it is minted on the other. This gives your treasury one ledger that shows what has settled, what is still in flight, and what has stalled.

Talk to our team

Read the guide

Highlights

  • A single cross-chain cash position, current at any moment

  • Dollars in flight visible while they move between chains

  • Stalled transfers flagged against your own SLA

  • Volume and settlement latency for every corridor you run

Trusted by leading financial and blockchain teams

Account for dollars while they are in transit

Under CCTP, a transfer burns USDC on the source chain and mints it on the destination. For the minutes in between, that dollar exists on neither balance sheet, and your cash position is split across two ledgers.

A true cross-chain cash position

Settled balances per chain plus in-flight amounts by destination, in one query, so when someone asks where the money is your team has one number rather than an assembly job.

Nothing silently stuck

Transfers that pass your settlement SLA are flagged and checked automatically, so you hear about a delayed payment before whoever is waiting on it does.

Corridors you can manage deliberately

Volume and settlement latency by source and destination give you the evidence to take a routing change to whoever signs off on it, with the numbers already attached.

What your settlement ledger includes

Both halves of every transfer, correlated, in a database your team already queries.

Both sides of the transfer

Burns on the source chain and mints on the destination are indexed together and correlated, so each movement is one row rather than two unrelated events.

Settled, in flight, or delayed

Every transfer carries a status and a settlement time, so you can separate what has landed from what is still moving and what has taken too long.

Liquidity by chain and by corridor

Sum settled balances per chain and in-flight amounts per destination to see where your working capital actually sits at any moment.

An automatic watchdog

A scheduled Compose task picks up anything older than your threshold, checks the transfer’s attestation status with Circle, and alerts on whatever has not completed.

Every chain in one pattern

The same pipeline shape is repeated per chain and combined, so adding a corridor means adding a source rather than building a new integration.

Latency you can report on

Because both timestamps are in your ledger, settlement duration is a column: you can report median and worst-case latency per corridor without instrumenting anything.

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 a settlement ledger 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 a cross-chain USDC settlement ledger 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/cross-chain-settlement

Help me:

1. Set up a Turbo pipeline that indexes CCTP burn events across Ethereum, Base and Arbitrum into one table
2. Set up a second pipeline for the mint side on each destination chain
3. Write the reconciliation query that joins them on source domain and nonce and returns settled, in-flight and delayed
4. Add a scheduled Compose task that checks Circle's attestation API for transfers older than a 20 minute SLA and alerts on incomplete ones

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

Settlement ledger

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to see your whole cash position at once?

Bring your corridors and settlement SLA to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

Fast Transfers resolve in seconds. Standard Transfers wait for hard finality on the source chain, which is roughly 13 to 19 minutes on Ethereum. Because your ledger records both timestamps, you can set an SLA that reflects the mix you actually use rather than a worst case you inherited.
CCTP moves USDC natively across more than a dozen chains, and Goldsky indexes the ones it is live on today, including Ethereum, Base, Arbitrum, Optimism, Polygon and Avalanche. Adding a corridor means adding a source to the pipeline.
Real USDC. CCTP burns and mints the native asset, so there are no wrapped tokens and no bridge liquidity pools anywhere in the ledger you are reconciling. The dollar that leaves one chain is the same dollar that arrives on the other, which is what makes a single cash position defensible to your auditors.
No, and deliberately so. Goldsky indexes both sides into your database; the join, the status thresholds and any in-flight API you expose to the rest of your business stay yours, so treasury can change the rules without a pipeline change.
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. The ledger itself is built from public chain data landing in your own database, which usually keeps the review shorter than teams expect.
You own it, in a database you choose. Both sides of every transfer land in your own Postgres, MySQL or ClickHouse, run by you or hosted by us, under a schema you defined. The matching logic is your SQL, so your cash position is something your treasury team holds outright rather than something they read out of a vendor’s system.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status