Payments Rails

Settlements

Finality, reconciliation, and netting in tokenised payment systems

Settlement vs authorisation

Authorisation reserves or locks funds; settlement transfers final ownership. Card networks settle in batches days later. Digital stablecoin transfers settle in seconds to minutes depending on network conditions—but off-ramp legs may still batch with telcos, ACH, or SEPA partners.

Understanding where finality occurs prevents accounting mismatches across USDC, EURC, XOFC, and other assets.

Settlement models

ModelCharacteristics
Gross real-timeEach transfer settles individually (digital ledger)
Net batchPositions netted periodically (nostro with partner bank)
HybridDigital gross; fiat netted daily

GoldRail tenants often run hybrid: digital assets move instantly between wallets; fiat treasury rebalances once per day with liquidity providers.

Reconciliation principles

  • Digital supply matches treasury obligations under your policy per asset
  • Withdrawals matched to payout references in your finance system
  • Status events aligned with internal transaction IDs
  • FX conversion rates frozen at quote time

Gateway and UltraVault treasury wallets simplify segregation—client liabilities versus operational float.

Disputes and exceptions

When settlement fails post-authorisation, define escalation: automatic reversal (if possible), support ticket with audit reference, regulatory reporting if threshold exceeded.

On this page