Skip to main content
By the end of this guide you’ll understand the filtering rules that Mesh applies automatically during Link initialization, and therefore why certain integrations may not appear for your users.

​
Overview

Mesh automatically applies intelligent filtering during Link initialization to ensure users only see compatible, compliant, and viable integrations (wallets and exchanges). This improves success rates, avoids regulatory blockers, and enhances the user experience by not letting them go down dead end roads. Below is a complete breakdown of the filters we apply, categorized by use case and user type. If you need help validating provider coverage for specific asset/network combinations or regions, please reach out to your Mesh account manager.

​
Asset & Network Compatibility

Mesh only displays integrations that support at least one of the asset/network combinations provided as an eligible destination in your Link Token request. Applies to:
  • All clients
How it works:
  • If a user selects USDC on Solana, only integrations that support USDC.sol will be shown.
  • If none of the provided asset/network combinations are supported by an integration, it is excluded.

​
VASP ID Requirement

This is a Travel Rule filter. Some exchanges require the sending platform to provide a valid VASP ID when a transfer is originating from certain jurisdictions. If your business is a VASP, and Mesh does not have your VASP ID on file, and the user is in a restricted country, impacted exchanges won’t appear in the integrations catalog. Applies to:
  • Custodial platforms (e.g. neobanks, exchanges, fintechs)
How it works:
  • If your business is a VASP, and…
  • Mesh does not have a VASP ID for your client, and…
  • the user IP address is in an affected country (AE, AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, JE, KR, LI, LT, LU, LV, MT, NL, NO, NZ, PL, PT, RO, SE, SG, SI, SK), then…
  • Impacted exchanges are excluded from the integrations catalog

​
Wallet Ownership Requirement

This is a Travel Rule filter. When a user is sending to a self-hosted wallet, some exchanges enforce wallet ownership verification in certain jurisdictions. Because self-custody wallets cannot provide ownership proof, Mesh impacted exchanges out of the integrations catalog in these scenarios. Applies to:
  • Self-custody wallets
How it works:
  • If your business has a self-custody wallet model, and…
  • The user’s IP is in an affected country (AE, AT, BE, BG, CH, CY, CZ, DE, DK, EE, ES, FI, FR, GB, GR, HR, HU, IE, IS, IT, JE, KR, LI, LT, LU, LV, MT, NL, NO, NZ, PL, PT, RO, SE, SG, SI, SK), and…
  • The transfer amount exceeds 1000 EUR, then…
    • Users in the following Southeast and East Asian countries will have impacted exchanges filtered out regardless of amount: SG, HK, PH, KR
  • Impacted exchanges are excluded from the integrations catalog

​
Exchange Geography Restrictions

Mesh enforces IP-based restrictions at the provider-level to reflect each exchange’s supported regions. These rules are enforced directly based on provider policies and automatically reflected in the Link session. Applies to:
  • All clients
Examples:
  • Binance: Not shown to users with IPs in US, Canada, or Netherlands
  • Robinhood: Only shown to users with US IPs

​
Use Case Restrictions

This is a Travel Rule filter. Some providers restrict transfers based on the type of platform their user is transferring to. Mesh is bound by and abides by all exchange-level compliance requirements. When we believe that transfers to a certain client maybe blocked by a certain exchange in some geographies, we will remove that integration from the client’s catalog for users in those geographies. Applies to:
  • Varies

​
What’s next

If you need help validating integration coverage for specific asset/network combinations or user regions, reach out to your Mesh representative.
AI coding reference — a compact summary of this page’s APIs, parameters, and patterns for use by AI coding assistants (following the llms.txt standard). Human readers can safely ignore this.llms.txt — Intelligent catalog filteringMesh automatically filters which integrations appear in Link during session initialization. No client action required — filtering is automatic.5 filter types:
  1. Asset & Network Compatibility (all clients): Only integrations supporting at least one toAddresses asset/network pair are shown.
  2. VASP ID Requirement (Travel Rule — custodial platforms): If your business is a VASP, Mesh lacks your VASP ID, and user IP is in an affected country (EU + NZ, SG, KR) → impacted exchanges hidden.
  3. Wallet Ownership Requirement (Travel Rule — self-custody wallets): If destination is self-custody wallet, user IP in affected country, and transfer > 1000 EUR (or any amount in SG, HK, PH, KR) → impacted exchanges hidden.
  4. Exchange Geography Restrictions (all clients): Provider-level IP restrictions. Examples: Binance hidden for US/Canada/Netherlands IPs; Robinhood shown only for US IPs.
  5. Use Case Restrictions (varies): Some providers restrict transfers based on platform type and geography.
Action: Contact Mesh account manager to validate coverage for specific asset/network combinations or user regions, or to provide VASP ID.