Path Global · 01 — Crossway
Reach the destinations that live on other networks.
A Pix key, a PI-SPI alias, a UPI address, an IBAN. Crossway tells you which registry knows it, which participant holds it, where to send, and whether the name matches — through one signed interface. The payment stays on the rail it belongs to.
Built on the PATH protocol · @pathprotocol/sdk 0.3.0 · Access granted on request
02 — How it works
Four questions, asked of another network.
The same composition as PATH FINDER, pointed outward. Discovery reads the form of the key. The Crossway Finder — SONAR, then RESOLVER — reads the registry. A payee check closes the sequence.
Discovery
Which registry can know this key?
Answered from the key's form and the connector register. No registry is queried, so nothing about the key is revealed.
Sonar
Is it there, and at which participant?
Read from the registry at the time of the call. Budgeted, logged with the key hashed, and constant-shape when nothing is found.
Resolver
Where to send, on which rail?
Rail, currency, participant and destination, in the rail's own beneficiary format. Short-lived: a reading, not a pledge.
Payee check
Is it the person I think?
Match, close match or no match on the name you expect — or the name shown masked. Using each scheme's own check.
03 — The split
Crossway resolves. The rail settles.
What Crossway does
Identify, discover, resolve, check.
One interface for every registry it reads. One answer shape. Every answer signed, every connector attested. Your integration stays the same when the network changes.
What it does not
Not a rail. Not a directory.
No value moves through Crossway: your provider executes on Pix, PI-SPI, UPI or SEPA. No registry entry is stored beyond the answer that carried it. Crossway is a pass-through, never a mirror.
04 — Trust
Every answer is signed. Every connector is attested.
Each connector reads one registry, under the access of an authorised participant of that network or of a partner holding such access. Path Global signs an attestation for it: which registry, which operations, until when.
Every answer carries two signatures to check — the connector's, and the attestation it names. Ed25519 over canonical JSON. Revocation is checked at read, never cached. An answer whose attestation does not cover it is discarded.
{
"type": "crossway.connector_attestation",
"reference": "att_9kq3m7vx2pf8",
"connector": "pathglobal-br-01",
"registry": "pix.dict",
"operations": ["sonar", "resolver", "payee_check"],
"access": "authorised_participant",
"issued_at": "2026-10-01T00:00:00Z",
"expires_at": "2027-04-01T00:00:00Z",
"status": "active",
"signature": "…"
}
05 — Boundary
A key is a way to pay someone. Not a way to find out who they are.
Raw keys are accepted, and the limits are strict. No batch. Server-side only. Every call bound to a payment being prepared, within a per-registry allowance.
| Returned | Never returned |
|---|---|
| Which registry can hold a key | Whether a key exists, from Discovery |
| Which participant holds it | The account holder's full record |
| Where to send, in the rail's format | Any other identifier — phone, email, tax number in the clear |
| A name check, or a masked name | A full name in display mode |
| A signature and an attestation | A balance, a history, a KYC level |
06 — Coverage
Opened registry by registry.
Access is granted per client and per registry. The current status of each registry is shared with you once your request is reviewed.
| Registry | Network | Zone | Operations | Status |
|---|---|---|---|---|
pix.dict | Pix — DICT | BR | Sonar, Resolver, Payee check | Planned |
pi-spi.alias | PI-SPI — alias directory | UEMOA | Sonar, Resolver, Payee check | Planned |
upi.vpa | UPI — virtual payment addresses | IN | Sonar, Resolver, Payee check | Planned |
sepa-inst.vop | SEPA — Verification of Payee | SEPA | Payee check | Planned |
07 — On PATH
The interface is open. The service is ours.
PATH is an open protocol for the last mile of value transfer: identity, addressing, requests, authority, proof. Crossway is specified there, in the open, as PIP-0014. Path Global is a private company that operates it.
An address on PATH may declare that its holder receives on Pix or PI-SPI. When you need to go further than that declaration — into the external registry itself — that is where Crossway starts.
{
"kind": "crossway.resolution",
"registry": "pix.dict",
"rail": "pix",
"asset_type": "fiat",
"asset_code": "BRL",
"participant": { "id": "12345678" },
"destination": {
"key_type": "phone",
"key": "+5511987654321",
"account_type": "CACC"
},
"expires_at": "2026-10-05T10:05:00Z",
"connector": "pathglobal-br-01",
"attestation": "att_9kq3m7vx2pf8",
"signature": "…"
}
08 — Access
Access is closed. Ask for it.
Crossway is open to regulated payment institutions, fintechs, wallets and payment service providers. Each request is reviewed, and access is granted per registry.
- RequestTell us who you are, the registries you need, and your use case.
- ReviewPath Global reviews the request against each registry's rules.
- CredentialYou receive a signing key, scoped to the registries granted, with your budgets.