07 — PIPs · PIP-0003
Crossway rail profiles
Named mappings from PATH’s last mile onto rails that already settle — UPI, PIX, SPI, Wero.
- Number
- PIP-0003
- Status
- draft
- Type
- Networking
- Author
- PATH
- Date
- 2026-09-09
- Source
- On the register
Why
PATH does not replace an instant rail. It names the last mile — who, where, what is owed, who may act, whether it arrived — in a form another scheme can read. Crossway is that mapping. Without a PIP, each integrator invents a private translation and two PATH addresses that should be able to meet, cannot.
What a profile is
A profile is a published table: PATH object → rail object. It is not a new pillar. It does not add a colour, a wallet, or a PATH rail. Liquidity stays reserved.
| PATH | Rail |
|---|---|
| PATH ID | The scheme’s customer reference, where one exists |
| PATH ADDRESS | Where the scheme already delivers |
| PATH REQUEST | The claim the scheme already collects |
| PATH CONNECT | Who may instruct the scheme |
| PATH SETTLEMENT | The scheme’s own proof, quoted rather than replaced |
First profiles
UPI, PIX, SPI, Wero. Each profile is a later PIP or an annex. This PIP only fixes that a profile is a document, that it is public, and that a network which claims Crossway without publishing the table is non-conformant.
What it is not
It is not admission to those rails. PATH cannot seat a member at UPI. A club that wants to speak UPI still admits under its own rulebook, and the rail still admits under its own.