Developers
Crosswire is the orchestration layer - named partner docs curated by product, plus the Crosswire MCP so your AI agent can price, scope and request offers directly. Onboarding still happens with your Crosswire contact - these are for your integration team.
Each rail links to the partner's official developer docs. External links open in a new tab.
Syntheon is the orchestration layer. One integration with Crosswire and the stack behaves as one - routing, reconciliation, FX and settlement across banking, cross-border, acquiring, digital assets and KYC without stitching each partner yourself.
The Crosswire MCP is agent-callable orchestration - the stack, callable by AI. Your agent asks Crosswire for pricing, coverage or an offer; guardrails are enforced server-side.
BaaS runs on Narvi rails, wired behind the Crosswire contract. Same partner docs, one commercial relationship, one point of contact for issues.
Virtual IBAN issuance uses the Narvi Business Banking API. Payouts and reporting land in the same programme as banking.
Accounts, IBANs and payments run on Narvi. Crosswire keeps the commercial and operational contract; your team integrates against the partner API.
OTC liquidity and settlement run through FinchTrade. Crosswire handles the routing so on/off-ramp behaves as part of the stack.
KYC and KYB run on Sumsub, feeding partner underwriting so one identity pass unlocks banking + acquiring together.
Acquiring is wired through Shift4, orchestrated behind Crosswire so routing, settlement and reporting stay unified with the rest of the stack.
Docs point to the partner. Contract, commercials and support stay with Crosswire - one point of contact, whichever rail you're on.
The Crosswire MCP is agent-callable orchestration - pricing, coverage, stack recommendations and offer creation exposed as tools any MCP client can call. Every quote is indicative, subject to KYC.