Send money that
waits for proof.

Yazo locks a dollar-priced payment until the person receiving it shows their delivery code. The vendor can't take it early. Neither can Yazo.

No account. No card. No "3-5 business days."

Your orders

$40.00 42,106 sats

Fatima's order

Awaiting her code

$40.00 42,106 sats
Paid and held

This is the real dashboard's order row, live - not a screenshot. Launch the full thing →

The problem

A transfer isn't delivery.

Cash sent abroad gets lost to fake payment alerts, skimmed by a middleman, or just never confirmed. So people send less, or only to someone they already trust completely.

Sent is not the same as delivered.

$0bn

sent into Nigeria in 2025

0%

average cost to send it, against a 6.36% global rate

#1

Nigeria's rank worldwide in cross-border crypto flows

A vendor arranging tomatoes and peppers at Bodija Market in Ibadan, Nigeria, with a POS and mobile data stand behind her.

How it works

Four steps. Nobody has to trust anybody.

Each one is enforced by the Lightning network itself. Not by a dashboard. Not by us.

1

Order

Pick an amount and who it's for. Yazo issues a Lightning hold invoice for that exact sum.

2

Pay

You pay the invoice. The network holds the payment. Not spent. Not released. Just held.

3

Show the code

The recipient gets a one-time code. It only gets shown once the goods are actually in hand.

4

Released

The code unlocks the hold. The vendor is paid in seconds. No waiting. No middleman.

The guarantee

Even we can't take it early.

A Lightning hold invoice only pays out to whoever can produce its preimage. Yazo derives that from a secret that only the recipient holds, and never stores it.

  • ✓ The vendor: never sees the recipient's secret
  • ✓ Yazo's servers: store only a salt and a payment hash, never the secret or the preimage
  • ✓ Whoever steals the entire database: same reason
  • ✓ Nobody, if it's never delivered: the hold expires and the payer is refunded automatically
preimage   = sha256(DOMAIN, salt, secret) paymentHash = sha256(preimage) // the server stores only this line: { salt, paymentHash }

Security

Audited like it holds real money.

Every claim on this page has a test behind it. Yazo's founder is also its solo auditor, and the full threat model is public: what's defended, and what plainly isn't.

56automated checks

Read the full audit →
  • This is a testnet demo. No real funds move yet.

Questions

Before you ask

What happens if the item never arrives?
The hold expires automatically (six hours by default, configurable up to the ceiling below), and the payment returns to the sender. Nobody has to ask for a refund; a watcher does it on its own.
What's the longest Yazo can hold a payment?
24 hours, today - a hard ceiling, not a setting. A Lightning payment that stays locked too long risks forcing the channel carrying it to close, so holding it indefinitely isn't actually safer, it's a different failure mode. That means Yazo is a good fit for same-day and next-day delivery right now; a delivery that genuinely needs longer isn't a fit yet. An on-chain version of the same lock, with no 24-hour limit, is next on the roadmap - see the roadmap for how.
Can the vendor take the money before delivery?
No. The payment only releases when the recipient's code unlocks it. The vendor never has that code until the recipient chooses to show it.
What if the code gets lost?
QR codes carry 128 bits of randomness, so there's no realistic way to guess one. If it's genuinely lost, the hold still expires on schedule and the money returns to the sender.
Is this real money?
Not yet. This build runs on Lightning's test network for the hackathon. The escrow logic is real and runs against a live two-node network; the funds moving through it are test funds.
Why Lightning, and not a stablecoin on another chain?
Lightning has a primitive most chains don't: a payment that can be held, then either released or returned, enforced by the network itself. Not by Yazo. Not by an admin button.