Morse

  • Name: Morse (formerly Sling Money)
  • URL: https://morsemoney.com/
  • Category: global money-transfer app / stablecoin wallet-and-card integration surface / cross-border payments control plane
  • Summary: Morse at the project layer is the consumer-facing money app inside the broader Avian Labs company shell. The useful product cut is how users actually move money: transfers, account-details receiving rails, card usage, wallet deposits and withdrawals, fee framing, and country-facing operating guidance exposed through one app experience. The broader operator boundary now lives in avian-labs, which is the cleaner place to reason about the regulated perimeter, partner composition, card-program structure, support truth, and access workflow.
  • What it does:
    • Lets users send, spend, invest, and get paid across borders through one app-oriented money stack
    • Supports international money movement across 150+ countries and 40+ currencies according to the homepage and llms.txt
    • Exposes multiple operating surfaces through its help center: moving money, account settings, Account Details for getting paid in USD/EUR/MXN/BRL, Morse Card usage, wallet deposits and withdrawals, and country-specific guidance
    • Offers a wallet surface for adding and withdrawing digital currencies alongside fiat-oriented transfer and card rails
    • Publishes simple fee framing: most transactions free, real exchange rate with no markups, and small flat fees for certain non-local or post-free-tier international transfers
    • Packages these flows into one app-facing product rather than making users stitch together separate remittance, wallet, and card tools
  • Key claims:
    • Morse’s official llms.txt describes it as “a money transfer app for sending money internationally” with “Fast, low-fee transfers to 150+ countries”
    • The homepage says users can receive payments from the US in 150+ countries and can spend, invest, send, or convert their dollars anytime, which is a stronger product framing than just another remittance app
    • The fees page says most transactions are free, that users get the real exchange rate with no markups, and that some non-local or additional international transfers cost $0.50
    • The help center reveals the real product surface more clearly than the marketing homepage by separating money movement, account-details receiving rails, card usage, investing, wallet management, security, and country-level operating rules
    • Morse’s legal materials make clear that the broader operating shell is not just the app brand: Avian Labs runs the platform layer, Lead Bank issues the card, and Bridge manages the card program
  • Whitepaper: No canonical Morse whitepaper or litepaper surfaced in this pass. The clearest current product-layer sources of truth are Morse’s homepage, llms.txt, fees page, help center, and legal disclosures; see ../whitepapers/morse-primary-sources-2026-04-27.md and ../whitepapers/avian-labs-primary-sources-2026-08-12.md.
  • Sources:

Internal linkages

  • Company boundary for the regulated shell, card-program composition, and support/corridor truth: avian-labs.
  • Useful adjacent company reads: bridge-xyz, openpayd, and bvnk.

Protocol / company boundary

  • Keep this note on the product surface users actually touch: sending, receiving through account details, wallet deposits and withdrawals, card use, fee framing, and the app-level integration of those flows.
  • Use avian-labs when the sharper question is who controls the regulated perimeter, support workflow, country availability, card application and access shell, and partner composition with Lead Bank and Bridge.
  • That split matters because how does Morse work as an app? and which company controls the compliance, support, and card-partner shell around it? are related but not identical questions.

Control surface

  • At the product layer, practical authority accumulates around fee presentation, transfer and withdrawal UX, account-details usage, card behavior, wallet-funding paths, and the country-specific guidance surfaced inside the app shell.

  • The broader operator dependency sits one layer up in avian-labs: regulated status, support truth, card-program composition, user application and access workflow, and the operational rules that shape which corridors and product features stay available.

  • Useful consumer money-movement product note, but the more durable authority sits at the company boundary above it.

  • Last reviewed: 2026-08-12 UTC