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.
By Anton Titov, Founder · Plexo Institute
Neutral infrastructure has six measurable properties, each tied to a coercion vector and a binary pass/fail test.
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.
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.
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.
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.
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.
Neutrality Blocks Six Forms Of Control
Neutral infrastructure is a route whose critical switches cannot all be captured by one actor.
Neutral route
Payment can move only when no single switch owns the path.
Jurisdiction
State shutdown
route around one legal chokepoint
Counterparty
Partner withdrawal
warm standby banks, ramps, and issuers
Currency
Single denomination
separate USD, EUR, and local options
Regulatory
One regime veto
corridor-specific compliance paths
Economic
Hidden margin
reconstructable fees, spread, and FX
Technical
Proprietary lock
portable data and protocol handoff
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?
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.
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?
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.
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?
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.
The stablecoin market is overwhelmingly USD-referenced: BIS analysis published in 2025 found that almost 99% of stablecoin market value was dollar-denominated. 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?
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.
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?
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.
The World Bank Remittance Prices Worldwide monitor reported a 6.36% global average cost to send remittances in its September 2025 release. 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.
Technical Neutrality
The operator uses open standards, interoperable data formats, and portable settlement protocols.
A counterparty is not locked into the operator's proprietary stack.
Test: If a counterparty wanted to move its volume to a competing operator tomorrow, how long would the migration take and how much of the data would be portable?
Standard REST or gRPC APIs with OpenAPI specification.
Interoperability with major stablecoin issuers and chain standards, including EVM, Solana, Tron, and XRP Ledger.
Travel Rule implementation compatible with IVMS-101.
Exportable transaction history in standard formats.
Documented integration paths with competing operators where necessary.
Operators that build proprietary messaging, proprietary tokens, or proprietary compliance APIs create migration cost. Migration cost looks like stickiness on the revenue side but looks like lock-in from the counterparty side.
A neutral operator wins on product quality, not on switching cost. If the operator is confident in the product, it should not need lock-in to retain volume. Counterparties notice this. It shows up in procurement processes.
How to Audit
The audit process is the same regardless of operator size.
Run each property through the same sequence: define the test, collect evidence, score the result, and remediate anything short of a pass.
Neutrality Becomes Real Only When It Is Tested
Neutrality claims become operational only when failed evidence loops back into remediation and retest.
Audit object
Neutrality claim
Every property must produce an artifact, a score, and an owner before it can be trusted.
- 01
Define failure test
What would prove this property is not neutral?
- 02
Collect artifact
License, routing option, pricing record, log, or protocol spec.
- 03
Score evidence
Pass, partial, or fail; partial is not accepted as proof.
- 04
Remediate and retest
Every non-pass receives owner, due date, and repeat test.
Define the test. Each of the six properties has a specific test defined above. Do not soften the test.
Collect evidence. Evidence must be verifiable: license copies, entity structures, runbooks, production logs, pricing pages, and integration specs.
Score. Pass means full compliance. Partial means observable progress but gaps remain. Fail means the property is not satisfied.
Remediate. Every partial or fail is a Board-level item with a named owner and a time-bound remediation plan.
Neutrality is a moving target. A jurisdiction shifts archetype. A counterparty merges. A currency peg breaks. A protocol update changes interoperability guarantees.
Recommended cadence: full audit annually, and targeted re-audit any time one of the six properties is externally affected by new regulation, counterparty change, or major architectural shift.
The Self-Audit Checklist
Reproducible scoring sheet. Apply each test to the operator current architecture.
The checklist turns the framework into a diligence artifact. Each row should produce a pass, partial, or fail decision with evidence attached.
| Property | Test question | Pass / Partial / Fail |
|---|---|---|
Jurisdictional | Can service continue if any one jurisdiction disables the operator? | |
Counterparty | Can service continue if any one bank, ramp, or issuer exits? | |
Currency | What share of volume continues if USDC/USDT become unavailable? | |
Regulatory | Can asymmetric-archetype corridors, such as proactive-to-reactive, be served? | |
Economic | Can a user reconstruct the full cost from published documentation? | |
Technical | How long does counterparty migration take? How much data is portable? |
Six passes means fully neutral architecture. Five passes means one remediation item. Four or fewer means material gaps: the operator is marketing neutrality it does not structurally possess.
The checklist works symmetrically. An operator can run it against itself. A counterparty evaluating the operator can run the same checklist. Serious counterparties are starting to.
Publishing the operator's own score with evidence shortens counterparty due diligence and builds durable trust. Refusing to publish is also informative.
Counter-Arguments & Limitations
Where this framework can be challenged, and the counter-counter.
Two objections belong inside the framework itself: binary tests may be too strict for a messy operating world, and the currency-neutrality test may underweight USD network effects.
The argument: No operator runs perfect counterparty redundancy across all corridors simultaneously. No operator has zero USD concentration. Strict pass/fail forces every operator into fail and makes the framework unusable as a comparative tool. A weighted gradient, such as three of six with high weights on jurisdictional and counterparty neutrality, would be more honest.
Counter-counter: Gradient framing is exactly what creates plausible deniability in incumbent infrastructure. Operators score themselves mostly neutral and counterparties have no objective basis to push back. Binary tests force the conversation: either the operator can serve the corridor when a jurisdiction disables it, or it cannot. The partial category is the gradient: observable remediation in progress with named owner and timeline. Without binary terminal states, partial becomes permanent and accountability dissolves. The framework is uncomfortable on purpose.
The argument: Almost 99% of stablecoin market value is dollar-denominated. Treating USD concentration as a neutrality failure ignores that USD network effects are why stablecoins work for cross-border payments at all. Forcing operators to maintain non-USD paths with weak current demand can waste capital on theoretical resilience.
Counter-counter: Not hypothetical for corridors exposed to sanctions, capital controls, or geopolitical payment fragmentation. Operators serving those corridors with USD-only architecture face a choice between lost volume and informal routing. EUR-denominated MiCA-compliant rails and regional settlement options are becoming production requirements for those corridors, not theoretical hedges.
The test is also forward-looking: an issuer freeze on USDC or USDT, regulatory or technical, would cascade through a highly concentrated market simultaneously. Currency neutrality is the property that price-discovers fastest under stress. Operators that build it before they need it pay ongoing architecture overhead. Operators that build it during a freeze pay corridor-loss plus reputational cost.
About the Author
About This Framework
Scope, disclosure, and method.
Published by Plexo Institute. Data vintage: 2013-2026.
Disclosure: This is the audit checklist Plexo applies to its own architecture. Plexo scores itself against each of the six tests internally on an annual cadence and publishes the score to counterparties on request as part of operator due diligence. The framework is not abstract industry observation. It is the same set of tests Plexo holds itself to.
Property set derived from observed coercion vectors in cross-border payments from 2013-2026, refreshed on 2026-05-11 for stablecoin concentration, remittance-cost, correspondent-banking, cross-border roadmap, and Travel Rule sources. The framework uses published literature from the Financial Stability Board, BIS, FATF, ISO, and IVMS working groups, plus internal operator post-mortems shared anonymously. Each property is binary at the test level, pass or fail, with a partial category for observable remediation. The framework does not assign weights between properties: all six are necessary, none is sufficient. Audit cadence recommendation reflects observed industry practice in security and compliance review cycles.
Continue Reading
The regulatory map behind Property 4 - proactive, permissive, restrictive, reactive, and which corridors each creates.
The CBR Exodus - why incumbent rails fail Property 2 when counterparty redundancy disappears.
Where these properties are tested - the architecture stack that neutrality must survive.
References
BIS CPMI, Cross-border Payments Programme (2020-2026).
Financial Stability Board, Cross-border Payments.
ISO, ISO 20022 Universal Financial Industry Message Scheme.
OpenVASP / IVMS-101, Travel Rule Data Format Standard.
FATF, Virtual Assets and VASPs Updated Guidance (2021-2024).
World Bank, Remittance Prices Worldwide (September 2025 global average).
BIS, Stablecoin growth - policy challenges and approaches (2025).
Circle, Why Liquidity Fragmentation Holds Back Global Payments (March 2026).
References
9 references- 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