Payments rarely arrive exactly when they are needed. A large outflow may fall due in the morning while the matching inflow lands in the afternoon. Bridging that gap — intraday credit against flows that are visible but not yet settled — is one of the most useful, and most delicate, functions a settlement network can offer.

Why the gap exists

Incoming flows are visible before they are final. A payment in progress has a counterparty, an expected path and a likely arrival time; it simply has not settled yet. If the network can see those flows with confidence, it can reason about a shortfall in the knowledge that cover is on its way. The difficulty is not identifying the gap but deciding what counts as reliable enough to bridge.

Outlook, not a promise

This is a forward-looking direction rather than a current product. It belongs to a later stage of the roadmap, where the network becomes a shared balance sheet of participants and intraday liquidity markets and guarantees can develop. Today SUPA operates a zone model where units run on licensed partners' rails; it is not a bank and does not take deposits. Any credit-like function would depend on licences, participant rules and local law. This article is general information, not financial or legal advice.

The controls that make it safe

Whatever the instrument, the governance is the design:

  • Limits and approval thresholds set by the participant, applied below the model where no agent can argue with them.
  • Over-limit operations turning into a human approval request rather than an automatic rejection.
  • Reliance confirmations, sanctions screening, agent mandates and network anomaly signals checked once per operation.
  • Every entry traceable to a principal, an agent and a policy version in a double-entry ledger.

In short

  • Timing mismatches, not total liquidity, create most gaps.
  • Visible incoming flows can support a bridge in principle.
  • Intraday credit sits in a later roadmap phase, not today.
  • Limits, approvals and evidence are what make it safe.

Follow the network's development path → /protocol/