Reconciliation

Regularly comparing your own ledger with the provider's and the chain's records, so a missed webhook or a failed job never leaves a balance wrong.

Notifications get lost: endpoints go down, deploys restart workers, networks drop connections. A ledger that relies only on webhooks eventually drifts. Reconciliation is the regular catch-up that finds what was missed.

A sound routine:

Treat webhooks as a prompt to act, not as the record.
On a schedule, list everything that changed since your last check and compare it with your ledger.
Credit or update anything missing. Key each credit on the provider's id, so doing it twice has no effect.
Send anything that doesn't match, such as an unknown payment or a wrong amount, to a review queue.

On Valtu

List what changed with GET /v1/deposits?after=… and GET /v1/transfers?after=…. The dashboard keeps every webhook delivery attempt for 30 days, with your endpoint's response, and can resend one or everything that was given up. More in webhooks you can trust.

Related terms

Keep reading.

WebhookAn HTTP request a service sends to your server when something happens, such as a deposit confirming, so you don't have to keep asking. IdempotencyDesigning a request so that sending it twice has the same effect as sending it once, which is what makes it safe to retry a payout after a timeout. FinalityThe point at which a transaction can no longer be reversed or replaced, the moment it's safe to credit a deposit or treat a payout as done. Deposit addressAn address assigned to one customer so that anything sent to it can be credited to that customer, with no memo or reference to get wrong.

More in deposits and payouts: Payment link · Sweep · Payout · Batch payout. The whole glossary.

Start free on testnets Read the integration guide

Put it into practice.

Every workspace starts on testnets with free test coins: same dashboard, same API. Go live when your team is ready.

Get started Talk to sales