Cowrie Research

avian-labs

4 min read

Avian Labs, Inc.

  • Name: Avian Labs, Inc.
  • URL: https://morsemoney.com/legal
  • Category: cross-border money-services operator / stablecoin wallet-and-card operating company / compliance and card-program boundary
  • Summary: Avian Labs belongs in companies/ because the sticky dependency is not only that Morse lets users send and spend money. It is that one named operator defines the regulated perimeter, country coverage, account-details receiving workflow, card-application and management shell, support and security posture, and how fiat rails, wallet balances, and third-party card-program partners get packaged into one inherited product environment. The practical leverage is not a transfer button. It is the company boundary that decides who gets access, under what regulatory and partner structure, and with which offchain support and corridor rules.
  • What it does:
    • Operates the broader Morse consumer money stack spanning international transfers, account-details receiving rails, wallet funding and withdrawal, card access, and country-specific operating guidance
    • Packages help-center support, regulator-facing disclosures, and country-by-country product availability as first-party workflow rather than leaving users to assemble rails themselves
    • Serves as the regulated operating shell presented to users through US money-services registration, MiCA / CASP authorization in the Netherlands, and an NMLS-identified US entity
    • Acts as the platform provider for the Morse prepaid card flow, while depending on Lead Bank as issuer and Bridge as card-program manager
    • Owns the application, access, and management layer around the card and broader app relationship even though important banking and card functions are delegated to named partners
  • Key claims:
    • The legal page identifies the operator as Avian Labs, Inc., says it is a registered Money Services Business in the United States, and says Avian Labs is authorized as a CASP under MiCA by the AFM in the Netherlands with registration number 41000005, which is enough to justify a named legal-entity boundary
    • The same legal page identifies Avian Labs USA, Inc. with NMLS ID 2639252, which reinforces that the operating shell is not just a casual app brand
    • The homepage frames Morse as a unified cross-border product for receiving payments, spending, investing, sending, and converting money, which signals a company-run money stack rather than one narrow protocol surface
    • The Help Center splits the product into Move money around the world, Get paid via Account Details, Spend worldwide with Morse Card, Manage your Morse Wallet, Morse Invest, Stay secure on Morse, and Find information by country, which is a strong sign that support, corridor policy, and product packaging belong to the company layer
    • The legal disclosures explicitly say Lead Bank issues the prepaid debit Visa card and Bridge manages the card program, while Avian Labs is the platform provider responsible for application, access, and management of the card, which is exactly the kind of partner-composed control surface that belongs in companies/
  • Whitepaper: No standalone Avian Labs whitepaper is the important artifact here. The clearest primary materials are the Morse homepage, llms.txt, help center, and legal disclosures, captured in ../whitepapers/avian-labs-primary-sources-2026-08-12.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep morse on the product surface: transfer flows, wallet behavior, account-details UX, card usage, fee framing, and the user-visible app stack.
  • Keep this note on Avian Labs as the named operator that defines the regulated perimeter, publishes country and security guidance, controls the application-and-support shell, and composes Lead Bank plus Bridge into one product users inherit.
  • That split matters because how does Morse behave as a product? and which company controls the access, compliance, support, and partner-composition shell around it? are related but not identical questions.

Control surface

  • Practical leverage sits in country availability, user support and help-center truth, wallet and card access workflow, regulated-entity perimeter, partner selection, card-program packaging, and the company-managed application / access shell above the app.

  • The sticky dependency is not merely a remittance flow. It is that users inherit a company-run support, compliance, corridor, and card-partner graph before any cross-border transfer or wallet withdrawal succeeds.

  • Read Avian Labs first as the operating company boundary around Morse, not as a neutral financial rail.

  • Last reviewed: 2026-08-12 UTC

Graph View

Backlinks