← back

Maritime Stablecoin Payments

stablecoin rails for the shipping industry, and why the timing window closed

download full research .md
tldr
initial theory
maritime shipping moves $100B+ annually across dozens of currencies with 42-day average settlement. stablecoins should compress this to minutes.
hypothesis
a stablecoin-native payment layer could capture float yield, reduce FX costs, and free working capital for mid-size ship management companies.
validated by
15,000+ words of desk research, 4 insider interviews, competitive landscape mapping, 3 business model explorations
verdict
deprioritized
skills
market sizingprimary researchcompetitive analysisstablecoin infrastructurecross-border paymentskill discipline
market metrics
$100B+
annual cross-border shipping payments
42 days
average settlement cycle
36%
of ship managers cite cash-flow as top pain
$55M
estimated annual float yield opportunity
market segments
segmentannual volumepain levelstablecoin fitverdict
crew payroll$8-12Bhigh — multi-currency, slow, error-pronestrong — recurring, predictable, price-sensitivebest entry
port disbursements$25-35Bmedium — fragmented agents, opaque feesmedium — requires agent network migrationpossible
vendor payments$30-40Bmedium — standard B2B pain, nothing maritime-specificlow — generic cross-border problemgeneric
brokerage / charter$20-30Blow — large counterparties, established railslow — trust-based, relationship-drivenpoor fit
primary research
research method: 4 insider interviews across ship management, crew payroll operations, maritime fintech, and port agency. each interview tested specific assumptions from desk research against operational reality.
assumptiondesk research saidinsiders saidimpact
crew payments are slow and painful42-day average, multi-currency nightmarepartially true — payroll is painful but ship managers have workarounds; the real pain is compliance, not speedweakened
42-day settlement is the normindustry average from trade pressmisleading — 42 days is for charter hire disputes, not routine crew pay; crew payroll settles in 7-14 days via existing fintechdebunked
FX savings would drive adoption3-5% FX spread on emerging-market currenciesreal but insufficient — ship managers negotiate bulk FX rates; savings would be 0.5-1% at best, not enough to change behaviorweakened
ship managers would welcome stablecoinscrypto-curious industry seeking modernizationfalse — extreme regulatory caution; compliance officers veto anything with "crypto" in the name; need bank-grade rails or nothingdebunked
thesis evolution
dimensionoriginal thesisafter research
target pain42-day settlement crushing working capitalsettlement is 7-14 days for routine payments; working capital pain is real but overstated
value propinstant settlement + FX savings + float yieldFX savings marginal; float yield real but small; compliance cost dominates decision-making
go-to-marketdirect to mid-size ship managers (50-200 vessels)must go through existing platforms (Marcura, ShipMoney); direct sales cycle is 12-18 months
competitive moatfirst mover in maritime stablecoinsMarcura already building; JPM Kinexys live for large counterparties; window is closing
maritime payroll flow (current state)
ship master
shore verification
corporate treasury
SWIFT / fintech
debunked: "Maersk ran a USDC trial for crew payroll."
this claim circulated in crypto-maritime circles throughout 2023. primary research found zero evidence. Maersk's treasury team confirmed they explored blockchain for documentation (TradeLens, now shut down) but never trialed stablecoin payments. the rumor likely originated from a conflation of TradeLens with a separate Circle partnership announcement that was supply-chain focused, not payments.
business models explored
modeldescriptionrevenuefeasibility
direct productbuild a stablecoin payroll platform, sell directly to ship managersSaaS + FX spread + float yieldlow — 12-18 month sales cycle, compliance veto risk
FDE integrationembed stablecoin rails into existing maritime fintech (ShipMoney, Marcura) as infrastructureper-transaction fee + float sharemedium — requires partner willingness, already building in-house
build for Marcuraposition as acqui-hire or dev shop; build the stablecoin module Marcura needsservices + equity / acquisitionmedium — Marcura well-funded, may prefer internal build
why deprioritized
competitive timing
Marcura raised $15M and began building stablecoin settlement in-house. JPM Kinexys went live for large maritime counterparties. the window for a startup to wedge in is narrowing to months, not years.
top of market captured
the largest ship managers (200+ vessels) already have treasury operations sophisticated enough to capture most of the value proposition internally. the mid-market is where opportunity remains, but it's harder to reach and lower margin.
regulatory wall
maritime payments cross 30+ jurisdictions per voyage. compliance officers at ship management companies universally vetoed "crypto-adjacent" solutions. rebranding as "digital dollar settlement" helps but doesn't eliminate the objection.
primary research gap
desk research painted a much rosier picture than reality. the 42-day settlement figure was misleading, FX savings were overstated, and crypto receptiveness was fabricated by the trade press. without primary research, this would have been a costly mistake.
infrastructure gap
building stablecoin rails that satisfy maritime compliance requires banking partnerships, money transmitter licenses in 10+ jurisdictions, and integration with legacy maritime ERP systems. estimated 18-24 months and $2-4M before first revenue.
important framing: deprioritized does not mean the thesis is wrong. stablecoins will eventually dominate maritime cross-border payments. the question is whether a startup can capture that transition, or whether incumbents (Marcura, banks) will absorb it. the research says incumbents win this one.
kill criteria matrix
criterionthresholdresultpass/fail
pain intensitymust be top-3 operational pain for target buyerpayments are top-5 but compliance and crewing rank higher; pain is real but not acute enough to drive fast adoptionborderline
economic upside$50M+ ARR opportunity within 5 years$15-25M ARR ceiling for crew payroll niche; broader maritime payments could reach $50M but requires 3+ year buildborderline
distribution accesspath to 10 paying customers within 12 monthssales cycle is 12-18 months; earliest realistic revenue is month 18-24 via direct sales, or month 9-12 via platform partnershipfail
regulatory pathclear licensing path in 2-3 key jurisdictionsrequires money transmitter licenses in Singapore, UK, and Panama minimum; 12-18 month timeline; $500K-1M legal costfail
competitive landscape
playerapproachstrengthweakness
Marcuramaritime-native payments platform adding stablecoin settlement700+ ship manager clients, deep domain expertise, $15M fundingslow product cycles, legacy tech stack
JPM Kinexysbank-grade blockchain settlement for large maritime counterpartiesregulatory compliance built-in, JPMorgan brand trust, live productenterprise-only, ignores mid-market, no crew payroll focus
my startupstablecoin-native payroll layer for mid-size ship managersspeed, focus, stablecoin-native architecture, niche targetingno distribution, no maritime credibility, no licenses, no funding
lessons learned
verdict: deprioritized, not abandoned
the thesis survived initial evaluation but the timing window is too narrow. the 15,000+ words of research are worth more as demonstrated thinking than as a company.
research artifacts
artifacttypedescription
market sizing modelspreadsheetbottom-up TAM/SAM/SOM for maritime cross-border payments by segment
competitive landscape mapresearch doc12 players mapped across maritime fintech, stablecoin infra, and traditional banking
primary interview transcriptstranscripts4 anonymized interviews with ship managers, payroll ops, fintech, and port agents
regulatory pathway analysisresearch doclicensing requirements across Singapore, UK, Panama, Marshall Islands, and Liberia
business model canvasframework3 models (direct, integration, acqui-hire) with unit economics and go-to-market plans
kill decision memomemoformal write-up of deprioritization rationale, shared with advisors for feedback