09 — Roadmap · 02
Crossway
PATH CROSSWAY
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 the work of mapping that last mile onto systems that already move money.
- Target
- Q4 2026 → Q3 2027
- Year
- 2026
- Window
- Q4
- Status
- now
The envelope is PATH. The rail stays the rail.
- 01UPIIndia. Unified Payments Interface. Collect requests, VPA addressing, and a confirmation that is not a PATH receipt until it is mapped.
- 02PIXBrazil. The scheme people see. Keys, QR payloads, and a return that has to become a signed receipt.
- 03SPIBrazil. Sistema de Pagamentos Instantâneos — the settlement system PIX sits on. Listed with PIX because the two are not the same object.
- 04WeroEurope. The European Payments Initiative wallet. A PATH request should be payable there without becoming a Wero-only object.
What we are doing now
Writing the mappings: which PATH object is which UPI collect, which PIX QR, which Wero instruction. Where a field has no counterpart, Crossway says so rather than inventing one. Compatibility is a published table, not an adapter that pretends the schemes are identical.
What ships
A Crossway profile per scheme: identifier kinds, request shapes, confirmation to receipt, and the errors that must not be collapsed. An implementer should be able to take a PATH request and produce a UPI or PIX payload without reading a private annex.
What it is not
A new clearing system. PATH still carries no money. Crossway does not put UPI inside PATH or PATH inside PIX. It is the last mile, spoken in their grammar. Membership of those schemes stays with those schemes.