Skip to content

Your Institution — Rails

Each Rail is a single money-movement primitive. TwoLegRail posts one debit + one credit; SingleLegRail posts a single leg (must be reconciled by a Transfer Template or aggregating rail).

Total: 4 rails declared on spec_example.yaml. The accounts diagram on the overview shows every rail as a labeled edge.

ExternalRailInbound — ach

(no description on the L2 YAML)

  • Shape: Two-leg (('ExternalCounterparty',) → ('CustomerSubledger',))
  • Posted requirements: external_reference
  • Aging — pending: legs SHOULD post within 1 day, 0:00:00 (Stuck Pending matview surfaces violations)
  • Metadata keys: external_reference

ExternalRailOutbound — wire

(no description on the L2 YAML)

  • Shape: Two-leg (('CustomerSubledger',) → ('ExternalCounterparty',))
  • Metadata keys: external_reference

SubledgerCharge — charge

(no description on the L2 YAML)

  • Shape: Single-leg (('CustomerSubledger',), direction Debit)
  • Aging — unbundled: posted legs SHOULD bundle within 4:00:00 (Stuck Unbundled matview surfaces violations)
  • Metadata keys: merchant_id, customer_id, settlement_period

PoolBalancing — pool_balancing

(no description on the L2 YAML)

  • Shape: Two-leg (('NorthPool',) → ('SouthPool',))
  • Aggregating: YES — bundles SubledgerCharge
  • Metadata keys: business_day