Skip to main content

Goldsky

Goldsky for Payments

Reconcile every settlement as it lands

Every settlement arrives in your ledger already carrying your payment reference, so matching happens on its own and breaks surface within seconds.

Talk to our team

Read the guide

Highlights

  • Settlements land in your ledger with your invoice reference attached

  • Matching that runs on a payment reference you control

  • Unpaid, short-paid and unexpected payments classified on arrival

  • Break alerts filtered against the invoices still open

Trusted by leading financial and blockchain teams

What changes when matching keeps up with settlement

Cash is applied as it arrives, the exception queue holds genuine breaks, and finance works from a position that is current through the day.

Breaks you catch the same day

Settlements match as they land, so a break reaches your team within seconds, while there is still time to chase the payer the same day.

A smaller exception queue

Matching on a reference you control removes the fuzzy amount-and-timestamp work, so your team handles genuine breaks instead of manually clearing noise.

Faster cash application

Cash is applied as it arrives, tightening working-capital cycles and giving finance a current position instead of a lagging one.

What real-time reconciliation gives your finance team

The pieces that turn settlement matching from an overnight batch into a continuous process.

Your reference, carried onchain

Match on a reference you set at payment initiation and decode into your ledger — a transfer memo, a calldata field or an event argument, wherever your rail carries it. Where a token standard reserves a field for exactly this, such as the 32-byte memo in TIP-20, the reference rides along with the transfer itself.

Deterministic matching

Settlements land in a table beside your invoices, so you match them on that reference in your own SQL instead of inferring which payment settled what.

Exceptions classified instantly

Unpaid, reconciled, short-paid and unexpected payments are all distinguishable the moment a settlement lands, not after an overnight run.

Break alerts without the noise

Keep a table of open invoices and alert only on genuine breaks, or maintain a running rollup in Postgres that updates on write with no scheduled job.

Reads you can reconcile against

Edge RPC cross-validates responses and enforces complete block ranges, so a missing log never leaves you reconciling against a settlement that is not there.

Act on a break automatically

Optionally hand an exception to a Compose task to retry a payout, issue a refund or open a ticket, with every step retried durably and traced.

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 payment reconciliation 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 real-time payment reconciliation 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/real-time-reconciliation

Help me:

1. Set up a Turbo pipeline that streams our settlement token's logs and decodes the payment reference each transfer carries
2. Land each settlement with its reference in a table next to our invoices
3. Write the SQL that matches settlements to invoices on that reference and classifies unpaid, short-paid and unexpected payments
4. Send genuine breaks to a webhook, filtered against a table of open invoices

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

Payment reconciliation

The full guide

AI Skills

For coding agents

MCP

Connect your agent

Ready to close the books in real time?

Bring your settlement and invoicing flow to a 30-minute call and leave with a concrete plan.

Talk to our team

Read the guide

Frequently asked questions

No. What makes matching deterministic is that the transfer carries a reference you defined, and that reference can live in a memo field, in calldata or in an event argument depending on the rail. A dedicated memo like TIP-20's is the tidiest version, but Goldsky decodes the reference the same way on any chain and standard it supports.
You do, at payment initiation, and you store the same encoding on the invoice. Reconciliation only works because the reference is yours to define on both sides.
Keep a table of open invoice references that your invoicing system maintains, inserting on open and deleting on paid or cancelled, and filter alerts against it. Without that, everything that has not been matched yet looks like a break.
No. Your ERP stays the book of record and keeps its own controls and approvals. Settlements are delivered into a table beside your invoices, and the join and the classification rules stay in your SQL, so your finance team changes the matching logic without anyone touching a pipeline. This is the layer that feeds cash application, not the thing that performs it.
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. Invoice data never leaves your database, since Goldsky writes settlements into it rather than reading your invoices out.
You own it, in a database you choose. Settlements land in your own Postgres beside your invoices, and the same stream can feed ClickHouse, Snowflake, Databricks or BigQuery for finance reporting. The matching rules are SQL your team wrote against a table your team owns, which is what keeps reconciliation an in-house process rather than a vendor dependency.

© Endless Sky Inc. All rights reserved.

PrivacyTermsSecurity

System status