Before You Build
OtherShut Down

37Coins

37Coins was a Bitcoin SMS wallet and remittance service that let people send and receive Bitcoin through text-message commands. It shut down after the team said SMS Wallet had not shown product-market fit and that international SMS delivery was unreliable.

View original story

Product snapshot

What it was

37Coins let users send and receive Bitcoin through SMS commands, with Android phones acting as local SMS gateways.

Who it was for

Bitcoin users sending funds to new or less technical usersUnderbanked or unbanked consumers in markets with limited banking or smartphone accessGateway operators willing to run Android phones as local SMS bridges

Problem / value

It aimed to bring Bitcoin transactions to users without smartphones, bank accounts, or desktop wallets.

Core workflow

A user could send Bitcoin through SMS commands while local gateway phones connected carrier SMS networks to the online Bitcoin wallet system.

Core dependency

The product depended on SMS carrier reliability, Android gateway phones, local gateway operators, and Bitcoin wallet infrastructure.

Product form

SMS wallet serviceBitcoin remittance workflow37Coins website and wallet account flowAndroid SMS gateway application

Pricing model

Launch coverage described gateway operators earning fees accepted from users. Public sources do not disclose a complete consumer pricing schedule, take rate, or unit economics.

Competitors or alternatives

The closure announcement said more Bitcoin services were serving underbanked and unbanked users by 2015.Live Bitcoin News mentioned coins.ph, ChangeTip, and BitGive Foundation in the broader market context.

What happened

Summary

37Coins shut down after its SMS Wallet failed to show product-market fit and international SMS delivery proved unreliable.

Outcome

37Coins and SMS Wallet shut down.

Core risk

Infrastructure-dependent payment product without reliable end-to-end delivery.

Shutdown reason

The closure announcement said the team could not deliver a quality product that showed product-market fit and that SMS delivery between carriers outside the United States was unreliable.

Demand signal

37Coins addressed a meaningful access problem: sending Bitcoin to people without smartphones, bank accounts, or desktop wallets. But the public closure note says attention and traction did not become a quality product with product-market fit.

Distribution issue

The core experience depended on carrier-level SMS delivery and local Android gateway operators. When messages failed across carriers or countries, the product could feel broken even if users wanted the outcome.

Timeline

  • December 2013: Cointelegraph reported a public Reddit launch signal and described 37coins.com as a prototype Bitcoin wallet platform.
  • 2014-2015: 37Coins operated SMS Wallet for more than a year and a half according to the shutdown notice.
  • August 2015: Finextra carried the closure announcement and CoinDesk reported the shutdown.
  • December 30, 2015: users were asked to withdraw SMS Wallet funds by this deadline.

Before you build

Why it matters

37Coins targeted a real financial-access problem, but the core experience depended on SMS delivery and local gateway reliability that the team could not fully control.

Primary check

Before building on SMS, payment rails, local gateways, APIs, or other infrastructure you do not control, prove completion reliability in the hardest target market before reading early interest as demand.

Checklist

  • Can users complete the core transaction repeatedly in the hardest target market?
  • Can failures be diagnosed and fixed without asking users to understand the infrastructure?
  • Does the operator side have enough incentive to stay reliable?
  • Would users still repeat if the social-impact story disappeared?
  • What third-party layer can break the core user promise?
  • Can you measure completion rate by market, carrier, gateway, or provider?
  • Who maintains the supply-side nodes or gateways?
  • What support cost appears when delivery fails?
  • What narrower market proves repeat use before expansion?

Relevant if

  • Your product depends on SMS, email deliverability, payment rails, platform APIs, model APIs, scraping, app stores, or regional infrastructure.
  • You need third parties or local operators to keep the network working.
  • Early users like the promise but completion reliability is uneven.

Less relevant if

  • You fully control the delivery path and can observe failures end to end.
  • Your MVP has already proven repeat usage under the hardest target-market conditions.

Pre-build tests

  • Run live transfer tests across the target carriers or providers.
  • Measure successful completion, failure rate, support tickets, and repeat usage.
  • Recruit and retain gateway operators before scaling user acquisition.
  • Test one paid or high-commitment workflow before broad social-impact positioning.

Transferable lessons

  • Test completion rate in the hardest geography before expanding.
  • Separate user interest from infrastructure reliability.
  • Validate supply-side operators and maintenance burden as part of the MVP.
  • Do not use a large underserved population as proof of near-term adoption.
  • Build a fallback path before the main value depends on a network you cannot debug.

If you build this today

A safer rebuild would start with one country, one carrier path, and one narrow remittance workflow. Test completed transfers, support load, gateway maintenance, repeat usage, and user trust before expanding the network.