In brief
- By its own documentation, Mesh is a routing layer: the user’s crypto stays in their exchange account or wallet until a transfer that Mesh sends on the user’s instruction delivers it to an address the integrating platform chose.
- FinCEN’s list carries a money services business entry for Mesh Connect LLC, received 12 August 2026, while the end-user terms, signed with Mesh Connect, Inc., still say the company does not engage in payment processing; which flows run under the registration is not explained.
- Who converts differs by flow and by source: Mesh credits its SmartFunding engine or PayPal, Kalshi’s help centre credits Zero Hash, and the party that executes Mesh’s own conversions is not disclosed.
Reader question: is Mesh aggregation, custody or routing, and where do the assets sit during a transfer?
Mesh sells one integration that lets an app, exchange or payment company pull crypto from a user’s account elsewhere, such as an exchange account or a self-custody wallet, for deposits, checkout payments and payouts. It began in 2020 as a consumer app, Front Finance, and now trades as Mesh Pay from meshpay.com; its developer documentation still sits at docs.meshconnect.com. This profile traces one transfer hop by hop from Mesh’s terms, docs and case studies, partner pages and two registers, read on 29 and 30 September 2026. We did not integrate Mesh or send a transfer; the flow is what the documents say, not what we tested.
What is verified today
Register-verified: FinCEN’s money services business list (export of 29 September 2026) contains Mesh Connect LLC, trading as Mesh Pay, San Francisco, with activity code 409 (money transmitter) and a received date of 12 August 2026. The export carries no registration numbers, so the number Mesh publishes, 31000338087527, is company-reported. A FinCEN entry is a federal registration; it does not establish state operating authority. ESMA’s interim MiCA register of 30 September 2026 has no Mesh or Front Finance entry (background: how ESMA plans to supervise MiCA firms).
Company-reported: live developer documentation for the Link flow and transfer API. Customer evidence has different strengths, and only Shift4’s is partner-authored; it is set out per partner in the settlement table below. Other names on Mesh’s site: Revolut (company-reported in use for wallet verification and deposits, since December 2024), World App (announced June 2026), Deel (announced August 2026) and Bybit Pay (announced September 2026).
Entity and authority
| Entity | Role in the documents | Licence or registration | Status (30 Sep 2026) |
|---|---|---|---|
| Mesh Connect Inc. (also written “Mesh Connect, Inc.”) | Party to the business terms (Delaware law) and the end-user terms; named in the privacy notice; site copyright holder | None claimed; the end-user terms call it a technology provider of a “communications tool” | Company-reported |
| Mesh Connect LLC (DBA Mesh Pay) | Holder of the licences on Mesh’s licences page | FinCEN money services business | Verified on the FinCEN list; registration number company-reported |
| Mesh Connect LLC | Same | Michigan MT0027385 and Missouri MO-26-10184 money transmitter licences; NMLS ID 2852070 | Could not be verified: licences page reviewed, state registers and NMLS not queried |
| EU entity, if any | Privacy notice cites MiCA obligations “as a crypto-asset service provider and/or money transmitter” | None named | Not yet verified: no matching entity in ESMA’s interim register on 30 Sep 2026; which affiliate the notice means is not stated |
The relationship between Mesh Connect Inc. and Mesh Connect LLC is not yet verified. No Mesh page states it; SEC EDGAR has no filer under either name or Front Finance; California’s business register blocked our request; Delaware’s search is CAPTCHA-gated and was not attempted (all 30 September 2026). We assume no parent or subsidiary link. The licences page lists two states and says more US and international licences are being pursued.
Product scope, availability and eligibility
Documented flows are deposits, checkout payments, on-ramp purchases through Binance Connect or other providers, payouts funded from a client’s existing exchange and wallet balances, and wallet verification. Mesh also markets wallets that platforms can create for users; who manages their keys is not publicly disclosed. Neither where a business may contract nor which end users are eligible or restricted could be determined: the terms, privacy notice and docs we read carry no country list, so eligibility has to be confirmed per route and per partner. Mesh’s docs list 35 networks and 22 stablecoins, with USDC and USDT the most widely supported, and ten exchange entries, of which Krak Pay is in beta, OKX Pay in development and Kraken marked TBD; Coinbase is listed for the US and EMEA, Robinhood for the US only. The business terms name only Delaware law and San Francisco arbitration. Pricing and business onboarding criteria are not publicly disclosed: the site’s product pages, the business terms and the go-live guide, which covers only technical steps, carry neither.
Funds-flow map: one aggregated transfer
Our synthesis, in two parts. First the generic flow Mesh documents for a deposit or payment through its hosted Link; then how three named partners settle, each a separate arrangement.
| Hop | Where the asset sits | Who acts | Evidence |
|---|---|---|---|
| 1. Connect | User’s exchange account or self-custody wallet | The user signs in through Link; Mesh runs the login and OAuth calls, may receive the user’s credentials, and stores and refreshes the exchange authorisation (Managed Tokens). | Mesh docs and terms |
| 2. Configure | Unchanged | The platform’s server sets transfer type, destination address, amounts and networks. | Mesh docs |
| 3. Fund and convert (if needed) | Per Mesh, inside the user’s account; during a swap or bridge: not publicly disclosed | SmartFunding can draw on up to five sources in the connected account; for PayPal, Mesh says it “converts the asset inside the buyer’s own account or wallet”. Whether the exchange, a bridge or a Mesh entity executes it is not publicly disclosed. | Mesh blog; unknown |
| 4. Send | In transit; exchange transfers leave from the exchange’s omnibus hot wallet | Mesh’s API calls these transfers “initiated by Mesh”; its callback fires when the source acknowledges the request, not on chain confirmation. In manual deposits the user sends. | Mesh docs |
| 5. Arrive | Address set in hop 2 (platform or merchant wallet) | The platform; what happens next depends on the partner | Mesh docs |
| Partner | Reported settlement | Conversion executor | Evidence status |
|---|---|---|---|
| Shift4 (merchant payments) | Shift4: payments “converted to US dollars and settled to the merchant” | Not publicly disclosed: Mesh credits SmartFunding without naming who executes it; Shift4 does not say | Partner-authored: Shift4 named Mesh on 28 Oct 2024, rollout “in stages”. Mesh says the Shift4 product is live in 75+ countries, which describes Shift4’s reach, not general Mesh availability: company-reported in use |
| PayPal (Pay with Crypto) | Merchants receive US dollars (Mesh, citing PayPal’s help centre) | Per Mesh: SmartFunding inside the buyer’s account, then PayPal’s side through PYUSD; PayPal’s release does not say | PayPal launched the product on 28 Jul 2025 but its release does not name Mesh: company-reported in use |
| Kalshi, US users (deposits) | Not stated | Zero Hash, which Kalshi says processes US crypto transfers and converts to and from fiat | Partnership announced by Mesh 5 May 2026; Kalshi’s help centre names Zero Hash, not Mesh: company-reported in use |
What the map resolves. No document we read describes the asset entering an account Mesh holds. That is an absence of description, not proof, because the executor of conversions and bridges is undisclosed. Mesh does hold credentials or tokens and sends the instruction, and for some flows says it converts. Its own pages disagree on how far that goes: the deposits page says Mesh “never holds, routes, or touches customer funds” and, on the same page, that “Mesh handles the routing, conversion, and delivery”; the Deel page says Mesh is “never in the flow of funds”. Mesh Connect LLC nonetheless registered with FinCEN as a money transmitter, and the privacy notice cites duties “as a crypto-asset service provider and/or money transmitter”, while the end-user terms (2 July 2025, Mesh Connect, Inc.) predate the registration and still disclaim payment processing. Which hop, if any, Mesh treats as money transmission, and under which entity, is not publicly disclosed. The end-user terms cap Mesh’s liability at $10.
Dependencies
Every transfer depends on the source exchange or wallet executing it (the docs list ten exchange entries, some in beta or development) and on the settlement partner; on-ramp purchases depend on Binance Connect or other providers. Bridge operators and conversion liquidity providers are not publicly disclosed.
Alternatives
Closer options for a platform that wants crypto moved and settled for it are licensed infrastructure firms that hold the assets themselves. Two with register-checked entities:
| Point | Mesh | zerohash | Bridge (Stripe) |
|---|---|---|---|
| Holds the user’s crypto | No, per Mesh; assets stay at the source exchange or wallet | Yes: EU client assets sit in omnibus wallets of a zerohash foundation | Yes: under its US terms Bridge is custodian of the user’s wallet |
| US federal registration (FinCEN list) | Mesh Connect LLC (409) | zerohash llc (409, 414, 415) | Bridge Building Inc. (409, 499) |
| US state coverage claimed | 2 licences (company-reported) | “51 U.S. jurisdictions” (company-reported) | Not compared here |
| MiCA entry on ESMA (30 Sep 2026) | None | zerohash europe B.V. (AFM), custody included | Bridge Building S.A. (CSSF), custody included |
Mesh fits a platform that wants to pull crypto its users already hold and accepts Mesh’s own statement that it never takes custody; who holds the asset during a swap or bridge should be confirmed for the route in question. zerohash or Bridge fit a platform that wants a licensed firm to hold, convert and settle. They also combine: at Kalshi, per the two companies’ pages, Mesh handles deposits and Zero Hash converts for US users. A platform whose users start with fiat needs a ramp such as Transak, the fiat on- and off-ramp, which sells crypto to the user as principal; Mesh itself routes fiat purchases to ramps.
Limitations and unknowns
- Michigan and Missouri licences and NMLS ID 2852070: company-reported and could not be verified; state registers and NMLS were not queried, so no lookup was attempted (licences page read 30 September 2026).
- Inc. versus LLC relationship: not yet verified. EU authorisation and responsible entity: not yet verified (privacy notice cites MiCA obligations; no matching entity in ESMA’s interim register). FCA, Singapore and India registers: not checked.
- Integration count: conflicting evidence. The docs say 225 wallet integrations and ten exchange entries, while Mesh’s marketing says 300+ platforms.
- Reach: 400 million users (March 2025) and 900 million (January 2026) are undefined company figures, not evidence of Mesh’s own transaction volume, which is not publicly disclosed.
- SOC 2 Type II: company-reported; no report date, auditor or scope published.
Key facts (as of 30 September 2026)
- Series C: $75 million at a $1 billion valuation, led by Dragonfly (January 2026; total raised over $200 million, company figure). A Binance-led round reported in July 2026 is unconfirmed.
- Terms dates: business terms 5 May 2026, end-user terms 2 July 2025, privacy notice 23 September 2026, licences page 13 August 2026
Sources
- FinCEN: MSB Registrant Search; ESMA: interim MiCA CASP register
- Mesh: licences, end-user terms, privacy notice, docs: concepts, deposits
- Shift4: crypto payments release, October 2024
- Kalshi: crypto deposits
- Mesh: how PayPal and Mesh work together
Last updated: 30 September 2026. Next recheck triggered by: a change to Mesh’s licences page or new state licences; new end-user terms; any Mesh entity on ESMA’s register; a closed funding round; a change in the docs’ custody or transfer wording; a published SOC 2 report date.
