It takes the one payment the industry still does in cash — the tip at disembarkation, whether after a charter or a stay as the owner’s guest — and moves it from the guest’s bank to the crew, with proof. The tip passes through 100% intact. Ormeria’s revenue comes later, from the crew relationship the tip creates.
Structure
Two services in one
The same flow serves two roadmaps, deliberately coordinated.
Phase 1 · Internal · now → late 2026 season
Proving the payment service, internally
Interviews and a concierge pilot on a few reachable boats inside the network — not a market release; no unknown guests, no brokers. Ormeria never holds the funds — a regulated provider does — keeping Phase 1 outside money-transmission licensing.
Phase 2 · The Ormeria launch, Feb 2027
A customer-acquisition machine for crew banking
The service goes live for real guests here. Crew receive tips directly into an Ormeria account + Mastercard — the tip becomes the acquisition event for a mobile, multi-currency, underbanked population.
The transaction
Where the money goes
One payment in, the full amount out. Ormeria operates the service but never touches the funds in Phase 1.
Guest
Pays once, at disembarkation. Bank transfer by default (no fees); card optional, processing added on top — never deducted.
100% of the tip
Regulated provider
Holds the funds in escrow / connected accounts. The split runs here — by whichever payout model wins (A / B / C, open).
100%, split applied
Crew
Paid out in Phase 1; paid into an Ormeria account + card from the Feb 2027 launch.
OrmeriaOperates the service · takes 0% of the tip · absorbs bank-rail costs · earns interchange + FX on the crew card, from Phase 2
Who uses it
Two situations, four actors
The same flow serves two disembarkation moments — only the guidance and the introducer change. Nobody here is a “user” in the generic sense — each side has its own deal with the service.
Situation 1 · The design segment
The charter
Broker-intermediated, MYBA-style. Tipping custom anchored to the charter fee (10–15%, Med). The captain puts it in the welcome pack. This is what Phase 1 validates first.
Situation 2 · Hypothesis, added 26 Jul
The owner’s guests
Private use: guests invited by the owner tip the crew when they disembark. No charter fee to anchor to — guidance runs on stay length and boat custom; the owner or captain introduces it. To fold into the H1/H2 interview scope.
The payer — not the customer
Guest
Who
A charter guest — or a guest invited by the owner, on a private stay.
Uses it
Once. Two minutes, at disembarkation. No app, no account.
Buys
Not sourcing and carrying €15k in cash — and proof it arrived.
Owes
Nothing further. Deliberately.
Wedge hypothesis rests on one data point — H1 tests it.
Gatekeeper & channel
Captain
Uses it
Adopts once: registers the boat, puts the line in the welcome pack. Nothing per charter.
Buys
No cash custody aboard, no envelope ritual — authority over the split untouched.
Power
If captains don’t put it in the welcome pack, the service doesn’t exist.
Adoption untested — H2 is the pivotal research.
Beneficiary → the real customer
Crew
Uses it
Receives the money. From Feb 2027: into an Ormeria account with a Mastercard.
Buys
100% of the tip, always — the promise crews will not reject.
Spreads it
Crew rotate between boats — the organic growth mechanism.
Operator — takes nothing
Ormeria
Does
Runs the service on Aazzur/Equals + Mastercard rails. Never holds guest funds in Phase 1.
Earns
0% on the tip. Interchange + FX on the crew card, later.
Gets
The crew relationship — acquired at the moment money is handed to them.
Backstage — invisible to all of the above
Custody
Escrow / Stripe-Connect-style connected accounts at a regulated provider. Ormeria stays outside money-transmission licensing until the real rails switch on.
Split execution
Default equal; captain may adjust percentages. Split philosophy and guest visibility deliberately deferred — nothing may depend on it being fixed.
The payout leg Open
Model A — crew-direct claim links · B — boat management account · C — captain-instructed escrow. Decided by H2 captain research, not preference. Captain’s personal account: ruled out.
Why it’s a business
The service loop
Each tip is simultaneously the service delivery and the acquisition event. That loop is why this is Ormeria’s flagship wedge — not a standalone tipping app.
1
Guest tips — cashless, in the moment
2
Crew gets paid — 100%, with proof to the guest
3
Crew opens an Ormeria account + card to receive it
4
Crew rotates — carries the account to the next boat
5
Next boat onboards — more guests tip
The tip is the acquisition event.
Phase 1 rehearses steps 1–2 internally; the loop runs in full from the Feb 2027 launch.
1Guest tips — cashless, in the moment
2Crew gets paid — 100%, with proof to the guest
3Crew opens an Ormeria account + card to receive it
4Crew rotates — carries the account to the next boat
5Next boat onboards — more guests tip
↻ back to 1 — Phase 1 rehearses steps 1–2 internally; the loop runs in full from the Feb 2027 launch
In time
Three gates
Now
Validate
H1 guest interviews (8–10) and H2 captain interviews (5–6), in parallel. Output: confirm or kill the wedge; decide payout A / B / C by autumn.
Late 2026 season
Pilot — internal
H3 — a guest actually uses it at disembarkation, on 2–3 reachable boats inside the network. Concierge behind the scenes is acceptable. Still not a market release.
February 2027
Launch
The Ormeria launch — the service’s first real use. Crew accounts + cards are core to it, not a follow-on. Every tip from then on is an acquisition event.
Boundaries
What it deliberately is not, yet
Not crew banking — until February 2027.
Not a fairness arbiter — the split works as today unless the captain adjusts it.
Not broker-distributed — captain-direct until the concept is proven.
Not payment infrastructure — provider rails only; Ormeria holds no funds.
Honest status
The guest’s cash-logistics pain being the wedge rests on one data point (Francisco’s July 2026 charter). Captain adoption is untested. The “~70% cash” stat is single-sourced. The owner’s-guests situation is a fresh hypothesis (26 Jul), not yet in the product definition. H1/H2 exist to settle all of this before anything guest-facing is built.