GitHub
TransversePATH CROSSWAY

API reference

RESOLVER

Crossway stage 3 — where to send, on which rail, in which currency. A short-lived reading of the external registry, in the rail's beneficiary format.

LIVE — PIP-0014.

Private access. The Crossway API is operated by Path Global. Access is closed and granted per client and per registry, on request at pathglobal.finance. Requests are signed as in Authentication, under a key issued by Path Global, and sent from your server only.

https://api.pathglobal.finance/crossway/v1

Answers where to send, on which rail, in which currency. See the spec.


POST /resolver

{
  "registry": "pix.dict",
  "key_type": "phone",
  "key": "+5511987654321",
  "purpose": "payment_preparation",
  "nonce": "4b07c3a29d1e"
}

Response

{
  "kind": "crossway.resolution",
  "registry": "pix.dict",
  "requester": "client-fintech-a",
  "rail": "pix",
  "asset_type": "fiat",
  "asset_code": "BRL",
  "participant": { "id": "12345678" },
  "destination": { "key_type": "phone", "key": "+5511987654321", "account_type": "CACC" },
  "registry_reference": "dict-req-7fk2m9pq",
  "expires_at": "2026-10-05T10:05:00Z",
  "connector": "pathglobal-br-01",
  "attestation": "att_9kq3m7vx2pf8",
  "nonce": "4b07c3a29d1e",
  "signed_at": "2026-10-05T10:00:00Z",
  "kid": "pg_crossway_2026_01",
  "signature": "…"
}
FieldNotes
railFrom the rail register
asset_type, asset_codeAs in a PATH capability
destinationThe beneficiary format of the rail's profile. What your provider needs to execute, nothing more
registry_referenceThe registry's own reference for this read. Keep it for audit
expires_atShort. Read again rather than cache

A resolution is not a resolver answer: no standing, no commitment. It reports a registry entry. It is nobody's terms.

Then

Hand destination to your provider on the external rail. Crossway does not initiate, carry or settle the payment.

Errors

As for SONAR, plus:

CodeStatusMeaning
crossway.key.unresolvable404Nothing to resolve. Indistinguishable from not visible to you

On this page