framework
Six Properties of Neutral Infrastructure
Neutrality is not a marketing claim. It is six measurable properties: jurisdictional, counterparty, currency, regulatory, economic, and technical. An operator either satisfies them or it does not.
Published
Neutral infrastructure has six measurable properties, each tied to a coercion vector and a binary pass/fail test.
Reader Brief
Neutrality is not a marketing claim. It is six measurable properties: jurisdictional, counterparty, currency, regulatory, economic, and technical. An operator either satisfies them or it does not.
Reading Guide
Four moves that turn neutrality from rhetoric into a measurable architecture audit.
The framework moves from six coercion vectors to six pass/fail tests, then into the operating cost of redundancy, the TAM effect of regulatory reach, and a reusable due-diligence checklist.
Six properties equal six coercion vectors with binary pass/fail tests.
Cross-border infrastructure can be disabled from any direction: a sanctioning regulator, a counterparty bank, a stablecoin issuer, a license authority, a monopoly operator, or a protocol gatekeeper. Each vector maps to one of six properties: jurisdictional, counterparty, currency, regulatory, economic, and technical. Each property has a defined test. Partial is a failure flagged for remediation, not a soft pass. Six passes means neutral architecture. Five passes means one remediation item. Four or fewer means material gaps the operator is marketing past.
Counterparty neutrality is the most expensive property, and the most often skipped.
Banking redundancy is real money: each partner requires KYB, account minimums, ongoing compliance overhead, and relationship management. Most operators concentrate because it is cheaper. A neutral operator pays the diversity tax deliberately: two banks per corridor with active volume, two stablecoin issuers integrated with automated routing, and two on/off-ramp providers per jurisdiction. The failure mode is rationalization: "we have a backup provider identified." An unactivated backup is not a warm standby. Counterparty neutrality requires runbook-tested switchover times, documented Board-level metrics, and ongoing volume on the redundant relationship. Without that, the operator has a single point of failure with a story attached.
Regulatory neutrality is the only property that grows TAM; the other five protect it.
Operators that serve only proactive-to-proactive corridors miss the majority of cross-border demand. Operators that serve only permissive-to-permissive corridors are vulnerable to proactive regimes catching up. The flows that matter, and that incumbents cannot legally touch, are the asymmetric pairs: MiCA CASP on one side, trading-rules-only emerging market on the other. The architectural requirement is configurable compliance modules, a licensed entity on the proactive side, a compliant partner on the reactive side, and corridor-level risk scoring. The five protective properties keep the operator alive. Property 4 is what makes the operator larger than competitors that cannot survive in regulatorily asymmetric corridors.
The checklist works symmetrically: operator self-audit and counterparty due diligence use the same six tests.
An operator runs the checklist against itself. A counterparty evaluating the operator runs the same checklist. Serious counterparties are starting to. Each property has a verifiable evidence requirement: license copies, entity structures, runbooks, production logs, pricing pages, and integration specs. Score pass, partial, or fail with a named owner and time-bound remediation for every non-pass. Recommended cadence: full audit annually, and targeted re-audit on any external change such as new regulation, counterparty merger, currency peg break, or protocol update. Publishing the operator score with evidence shortens counterparty due diligence and builds durable trust. Refusing to publish is also informative.
Why Neutrality Matters
A neutral operator has designed out the switches that single actors can flip.
Cross-border infrastructure sits in a position where coercion can come from any direction: a sanctioning regulator, a competing operator, a counterparty bank, a currency issuer, or a protocol gatekeeper. A neutral operator has designed out each of those coercion vectors. A non-neutral one has a switch someone else can flip. Neutrality does not mean politically unattached. It means structurally resilient to any single actor decision to disable the operator. The six properties below are the measurable components of that resilience.
Why checklists beat manifestos.
Most neutrality claims are rhetorical. An operator says "we are neutral." A counterparty asks "neutral how?" and gets a brand answer rather than an architectural one. A checklist format forces specificity. Each property has a test. The test either passes or fails. Partial is a failure flagged as such. This is the same principle that works for security audits, compliance reviews, and infrastructure reliability reviews.
Jurisdictional Neutrality
No single jurisdiction can disable the operator by unilateral action.
Licenses, entities, and critical infrastructure are distributed across multiple non-aligned regimes. **Test:** If any one jurisdiction, including the US, EU, UK, China, Russia, or Iran, revokes the operator license or seizes its local entity, can the operator continue serving corridors that do not route through that jurisdiction?
What this looks like in architecture.
- Multi-jurisdictional licensing: primary licenses in at least two non-aligned regulatory blocs, such as UAE VARA, Singapore MAS, or Swiss FINMA. - Entity structure that does not consolidate in any single jurisdiction's tax or supervisory perimeter. - Critical infrastructure, including key management, settlement nodes, and data storage, distributed across jurisdictions. - Corridor-level jurisdictional routing: if Corridor A does not touch Jurisdiction X, Jurisdiction X cannot disable Corridor A.
Common failure mode.
Single-jurisdiction VASP license with an offshore holding company. On paper this looks neutral. In practice, if the licensed VASP is shut down, the offshore entity has no operational rails to run. The holding company is a legal structure, not an infrastructure substitute. This is why the test has to be: can the operator continue serving corridors, not does the operator have entities in multiple places.
Counterparty Neutrality
No single bank, exchange, payment service provider, or issuer can disable the operator by unilateral action.
Every critical relationship has a warm-standby equivalent. **Test:** If any one banking partner, on/off-ramp provider, or stablecoin issuer refuses to serve the operator, does service continue without material degradation?
What this looks like in architecture.
- Two or more banking partners in every corridor, with active volume on each. - Two or more stablecoin issuers integrated with automated routing. - Two or more on/off-ramp providers per jurisdiction. - Documented failover runbooks with tested switchover times. - Counterparty diversity as a Board-level risk metric, not an engineering detail.
Why this is harder than it looks.
Banking redundancy is expensive. Each banking partner requires KYB, account minimums, compliance overhead, and ongoing relationship management. Most operators concentrate because it is cheaper. A neutral operator pays the diversity tax deliberately. Counterparty neutrality is almost always the most expensive of the six properties to maintain. Operators that skimp here tend to rationalize it as "we have a backup provider identified," but an unactivated backup is not a warm standby.
Currency Neutrality
The operator is not structurally dependent on a single currency or issuer.
USD-denominated stablecoins, EUR-denominated rails, and local-currency tokenized deposits are all supported and routable. **Test:** If USDC or USDT became unavailable tomorrow because of issuer action, sanctions, or technical failure, what percentage of the operator volume would continue without interruption?
What this looks like in architecture.
- Native multi-currency routing: no hard-coded USD path. - At least two stablecoin issuers per denomination. - EUR, GBP, SGD, AED, and BRL-denominated routes where corridor economics justify them. - Local-currency tokenized deposit integration where available. - Automated rebalancing between denominations based on corridor demand.
Why USD-only architectures fail this test.
The stablecoin market is overwhelmingly USD-referenced: BIS analysis published in 2025 found that almost 99% of stablecoin market value was dollar-denominated [8]. An operator that runs exclusively on USDC or USDT has currency concentration risk by default. Issuer action against either would collapse volume. Currency neutrality does not mean avoiding USD. It means having architectural capacity to route volume away from USD when needed. Operators with EUR, GBP, and SGD-denominated paths already in production are the ones that pass this test.
Regulatory Neutrality
The operator can serve jurisdictions across proactive, permissive, restrictive, and reactive regimes without requiring one model to dominate.
Regulatory neutrality means the architecture can adapt at the corridor level instead of forcing every endpoint into the same regime. **Test:** Does the operator architecture allow a corridor to exist when one endpoint is in a proactive jurisdiction, such as a MiCA CASP regime, and the other is in a reactive jurisdiction with trading-only rules?
What this looks like in architecture.
- Compliance modularity: KYC rules, Travel Rule thresholds, and sanctions-screening parameters are configurable per jurisdiction, not hard-coded. - Licensed entity on the proactive side, compliant partner on the permissive or reactive side. - Corridor-level risk scoring that adapts to the regulatory archetype of each endpoint. - Ability to suspend corridors selectively without affecting unrelated flows.
Why this property predicts long-term survival.
Operators that can only serve proactive-to-proactive corridors miss the majority of cross-border demand. Operators that can only serve permissive-to-permissive corridors are vulnerable to proactive regimes catching up. Operators that can serve the full matrix, including asymmetric pairs, capture the flows that incumbents cannot legally touch. This is the property that translates directly into TAM. The other five protect the operator. This one grows it.
Economic Neutrality
Pricing is transparent. Spread, fees, and FX margins are disclosed separately.
Economic neutrality means there is no hidden extraction from the user or the counterparty. **Test:** Can an end user or counterparty reconstruct the full cost stack of a transaction from published documentation without asking the operator to explain?
What this looks like in architecture.
- Fee schedule published separately from FX spread. - Mid-market FX rate disclosed against transaction rate at each quote. - Corridor-specific pricing pages with worked examples. - No minimum-volume tiering that extracts from smaller users. - Counterparty-facing cost disclosure at contract level.
Why this is rare in cross-border payments.
The World Bank Remittance Prices Worldwide monitor reported a 6.36% global average cost to send remittances in its September 2025 release [7]. Most of the cost is hidden in FX spread rather than in named fees. An operator with a 1% fee and a 3% spread is more expensive than an operator with a 3% fee and 0% spread, but the second operator looks more expensive. Economic neutrality rejects this pricing asymmetry. An operator that meets this property gives up margin in the short term and earns counterparty trust that compounds. Wise, formerly TransferWise, pioneered this model in consumer. Institutional equivalents are now appearing.
Evidence And Sources
This raw HTML export preserves source visibility for crawler and contractor review. Indexing decision: index, follow.
- Correspondent Banking and Remittances - FATF
- Cross-border Payments Programme - BIS CPMI
- Correspondent Banking Data Report - Financial Stability Board
- ISO 20022 Universal Financial Industry Message Scheme - ISO
- Travel Rule Data Format Standard - OpenVASP / IVMS-101
- Virtual Assets and VASPs Updated Guidance - FATF
- Remittance Prices Worldwide - World Bank
- Stablecoin growth - policy challenges and approaches - BIS
- Why Liquidity Fragmentation Holds Back Global Payments - Circle