Goldsky

Reconcile stablecoin payments by reference

Goldsky writes each stablecoin payment into your Postgres database as it settles, with the invoice reference attached. Your team matches payments to invoices in SQL.

Talk to our team

Read the guide

At a glance

Payments arrive with your invoice reference
Match on the reference instead of amount and date
Short and unexpected payments show up in the query
Alerts only for payments that don’t match

Trusted by payment companies, fintechs and blockchain teams

Know which invoices are paid during the day

Because each payment is in your database once it settles, your team can run the match whenever it wants.

Breaks surface early
A short or unexpected payment shows up the next time the match runs, so your team can contact the payer the same day.
Fewer manual matches
Payments join to invoices on the reference. What doesn’t join is your list of breaks.
Paid status next to the invoice
Finance can see which invoices have been paid in the same database as the invoices themselves.

Stablecoin reconciliation on Goldsky: references, matching and break alerts

Goldsky pipelines write payments to your Postgres database. The matching itself is SQL your team owns.

A reference on each payment

Some tokens carry a memo field. On TIP-20 tokens on Tempo, the invoice or order reference goes in the memo and travels with the payment.

A payments table

Goldsky reads each transfer and writes it, reference included, to a table next to your invoices.

One matching query

A single query sorts open invoices into reconciled, short-paid and unpaid. Payments whose reference matches no invoice are marked unexpected.

Break alerts

Keep a table of open invoice references and Goldsky will send a webhook only for payments that match none of them.

Checked reads

Jobs that read payment data can go through Edge RPC, which cross-checks responses and confirms each block range is complete.

Follow-up tasks

If you want, a break can start a Goldsky Compose task that retries a payout, refunds an overpayment or opens a ticket, with each step logged.

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 payment reconciliation today

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

Open in Claude Code

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.

Close stablecoin payments the day they settle

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

Which chains and tokens does this work with?

The guide uses TIP-20 tokens on Tempo, which have a memo field for the reference. Matching depends on a reference being on the payment, so talk to us about how your token carries one.

How is a payment matched to its invoice?

The reference goes on the payment when it’s sent, and the same reference is stored on the invoice. The query joins the two.

How do we keep alerts from getting noisy?

Keep a table of open invoice references. Add one when an invoice is issued and remove it when it’s paid or canceled. Goldsky alerts only on payments that match none of them.

Does this replace our accounting system?

No. Goldsky puts payments in a table next to your invoices. Your accounting system and its controls don’t change, and your team owns the matching rules.

What access does Goldsky need?

A connection string to your Postgres database, stored as a Goldsky secret, so it can write payments. With break alerts on, Goldsky also reads your table of open invoice references.