U:RAIL Corridor

White-label framework for bank-connected corridors.

A new corridor is created by configuration — assets, participants, adapters, policies, limits, fees, cycles and screens — with no own ledger and no fork of Core. The collection bank receives local currency, the operator issues and redeems, the settlement bank pays merchants; U:RAIL makes them one payment system.

Lifecycle

One generic state machine, any corridor.

ONBOARDED → QUOTED → COLLECTION_PENDING → FUNDS_RECEIVED → COMPLIANCE_PASSED → LIQUIDITY_RESERVED → ISSUED → PAYMENT_AUTHORIZED → CAPTURED → NETTED → PAYOUT_CONFIRMED → REDEEMED/BURNED → RECONCILED → SETTLED

Collection bank

Local currency in

Signed, idempotent FUNDS_RECEIVED events matched by reference; late/partial/overpay policies configured.

FX / LP

Firm quotes & reservation

Bridge asset hidden from the customer unless disclosure requires it.

Issuer

Mint / redeem / burn

Sole issuance authority; mint gated by collection, compliance, liquidity/backing and issuer limits.

Merchant / acquirer

Signed payment request

Authorize, capture, refund; merchant claim becomes a fiat payable.

Settlement bank

Payout in fiat

Payout confirmation closes the merchant liability; failures keep it open for next cycle.

Netting

Two derived layers

Merchant net and participant net, reproducible over the immutable gross ledger.

Ownership

White-label. The partner keeps the customer.

Consumer brand, terms and data controller belong to the partner bank or licensed operator. U:RAIL can be “Powered by” or fully invisible; tenant isolation is enforced technically and contractually.