Skip to content

Your Institution — Transfer templates

A Transfer Template chains multiple Rail firings into a single business-meaningful Transfer (e.g. "ACH origination cycle: customer debit + sweep + Fed master credit"). The template's expected_net closes the bundle — every leg's signed amount MUST sum to that value (L1 Conservation invariant).

Total: 6 templates declared on spec_example.yaml.

MerchantSettlementCycle

(no description on the L2 YAML)

  • Expected net: 0
  • Leg rails: {{ no such element: str object['rail_name'] }}

ExternalReconciliationCycle

(no description on the L2 YAML)

  • Expected net: 0
  • Leg rails: {{ no such element: str object['rail_name'] }}

SettlementTimingCycle

(no description on the L2 YAML)

  • Expected net: 0
  • Leg rails: {{ no such element: str object['rail_name'] }} → {{ no such element: str object['rail_name'] }} → {{ no such element: str object['rail_name'] }}

BatchedPayoutBatch

(no description on the L2 YAML)

  • Expected net: 0
  • Leg rails: {{ no such element: str object['rail_name'] }}

DisbursementCycle

(no description on the L2 YAML)

  • Expected net: 0
  • Leg rails: {{ no such element: str object['rail_name'] }} → {{ no such element: str object['rail_name'] }}

CardLoadCycle

(no description on the L2 YAML)

  • Expected net: 0
  • Leg rails: {{ no such element: str object['rail_name'] }} → {{ no such element: str object['rail_name'] }}