POWERED BY SOLANA

CoffeeChain

Universal loyalty and micro-payments for cafes and coffee drinkers, powered by blockchain technology

Scroll to explore
↓
Overview

Democratizing Coffee Loyalty Programs

☕

CoffeeChain is a blockchain-based loyalty and payment system that brings the benefits of robust rewards programs to independent coffee shops. Built on Solana, it enables any café to launch a stablecoin-backed loyalty program in minutes, unlocking interoperability and financial utility that traditional systems cannot offer.

🏪
0
K
Independent coffee shops nationwide
☕
0
M
Daily coffee drinkers in the US
💳
0
B
Starbucks stored value card balance
🚀
0
K
Estimated cost to launch
The Opportunity

Why should Starbucks and Dunkin' be the sole beneficiaries?

We know people love to earn rewards and transact electronically for their coffee every day, but the status quo has issues.
1
Bring beloved coffee loyalty programs to independent cafes
Enable small cafés to offer the same robust rewards programs that major chains provide
2
Transparent, tamper-resistant points ledger
Blockchain technology ensures complete transparency and security for all transactions
3
Instant, low-cost settlement on the blockchain
Fast, affordable transactions that work for small businesses and their customers
4
Interoperable rewards across cafes
Earn and redeem BeanPoints across a network of independent cafes—something not offered by any single chain's closed loyalty program
Core Value Proposition

Decentralize and democratize the closed-loop coffee rewards economy

Enable any coffee shop to launch a stablecoin-backed loyalty program in minutes, unlocking interoperability and financial utility that traditional systems cannot offer.

⚡
Architecture
A set of audited programs (smart contracts) on Solana. This provides the necessary speed and low cost for real-world retail transactions.
💰
USDC-Backed
Merchant's loyalty points ("BeanPoints") are issued as SPL tokens, each unit backed 1:1 by USDC held in a transparent, verifiable reserve.

BeanPoints

BP
BeanPoints
Stable payment currency backed 1:1 by USDC. Users deposit USDC to receive BeanPoints, then spend them at participating cafes. BeanPoints earned at each café are non-transferable between merchants, ensuring true loyalty while giving merchants control over redemption terms.
Product Decisions

Why we made these calls

Solana over Ethereum

Coffee transactions need to be fast and cheap. Solana's ~400ms finality and sub-cent fees make it viable for a $5 latte. Ethereum L1 gas fees ($2-10) would eat the entire transaction. Even L2s like Polygon add unnecessary bridging complexity for merchants who just want it to work.

What we'd revisit: If Ethereum L2 fees drop below $0.01 consistently, the larger developer ecosystem could make it worth switching.

USDC-Backed, Not a Custom Token

Merchants won't adopt a system where their revenue fluctuates with crypto markets. USDC backing means 1 BeanPoint = $0.01 always. No volatility risk, no token speculation — just a digital dollar for coffee. This also avoids SEC securities classification concerns that come with custom tokens.

What we'd revisit: If stablecoin regulation changes significantly, we'd evaluate alternatives like USDT or a protocol-native stablecoin.

Non-Transferable Loyalty Points

This was the hardest call. Universal redemption sounds better for users, but merchants would never opt in — they'd be subsidizing competitors' customers. Non-transferability means each merchant controls their own economics, which is essential for adoption. The universal wallet still lets users pay anywhere; it's only earned rewards that stay merchant-specific.

What we'd revisit: Once network density is high enough, a shared rewards pool with merchant opt-in could unlock cross-promotion.

Architecture at Scale

Where the architecture has to leave Solana

Solana is the right rail for the on-chain ledger — sub-second finality, sub-cent fees, a transparent reserve. It is not a fix for fiat on/off-ramps, KYB at merchant onboarding, money-transmitter compliance, or settlement to a cafe owner's operating account. Those are bank problems. The honest version of the architecture is two layers, not one.

01 On-chain
ledger
User wallet (USDC) → CoffeeChain PDA · USDC reserve → Mint BeanPoints (SPL) → Merchant program account
Trustless, transparent, auditable. Reserve held in a Program-Derived Address. Total BeanPoint supply equals USDC in the PDA, always.
02 Banking
layer
Merchant burns BeanPoints → Custody · KYB · regulated reserve → Fiat settlement (FedNow / RTP / ACH) → Merchant operating account
Required at scale. Where compliance, settlement, and the merchant's actual relationship with money lives. This is the layer JPM Wallet and Kinexys are built for.

Four ways the second layer gets built

Real-world patterns for getting USDC into a merchant's bank account, ordered the way a platform actually walks into the question — from first instinct to where the architecture lands at scale.

Pattern 01
DIY via crypto exchange
USDC → Coinbase / Kraken → sell for USD → ACH → merchant bank
Cost~0.5% exchange fee
FrictionExtreme — every merchant manages a Coinbase Pro account, KYB, manual exports, tax events on every withdrawal
SettlementT+1 to T+3
Doesn't scale past ~100 cafes. No indie owner is doing this weekly.
Pattern 02
Stablecoin-to-fiat infrastructure
USDC → Bridge.xyz / Conduit / Beam API → ACH or wire → merchant bank
Cost~0.5% – 2% per conversion
FrictionMedium — one-time KYB through the provider, then API-driven; merchant doesn't touch crypto rails directly
SettlementSame-day to T+1
Workable for thousands of merchants — but you've added a counterparty who can fail, get acquired (Bridge → Stripe, 2024), or change pricing. Concentration risk is real.
Pattern 03 · First instinct
Embedded fintech rails · Stripe Connect & Treasury
BeanPoints → Stripe Connect / Treasury (rides Goldman, Evolve historically) → KYB at onboarding → ACH or RTP → merchant operating account
CostStripe fee stack on payments + Treasury fees; predictable, fintech-standard
FrictionLow — well-trodden onboarding, polished docs, ships in ~2 weeks
SettlementSame-day to T+1; RTP where supported
The default move for any platform launching today. The wall comes later — when an audit committee asks about sponsor-bank concentration (Synapse, Evolve), when multi-currency gets serious, when enterprise procurement enters. Right answer for CoffeeChain v1 through ~v50. Not where you want to be at v100.
Pattern 04 · Scales
Embedded bank rails · the JPM Wallet pattern
BeanPoints → bank custody → KYB at onboarding → real-time settlement → merchant operating account
CostHigher headline rate, lower TCO once compliance, KYB, dispute handling, and reconciliation are included
FrictionLowest — merchant onboards once, never touches crypto rails, gets a familiar bank statement
SettlementReal-time (FedNow / RTP) or T+0
The answer at scale. Bank charter — not partner bank — so the audit-committee question stops being a question. JPM is productizing exactly this with Kinexys: bank-grade rails on public chains, with the deposit-status legal posture that Stripe-on-Goldman structurally can't match.
Solana solves the ledger. A bank solves the rails. Both are needed at scale.
The on-chain layer is what makes BeanPoints trustlessly auditable — every reserve dollar visible, every merchant balance verifiable, no hidden ledger. The banking layer is what makes BeanPoints actually useful for an indie cafe owner who just wants to pay rent. CoffeeChain v1 ships on the on-chain layer alone. CoffeeChain v100 — thousands of merchants, millions in stored value, regulated reserves — needs both. That's the architecture J.P. Morgan Payments is building for embedded finance customers, and it's where this work points next.
Customer Experience

What the dApp looks like in practice

Explore the fully interactive CoffeeChain app

Open Full App →

Customer Experience:

  • Deposit USDC into your account in exchange for BeanPoints (1:1 stable payment currency for use at participating cafes)
  • Pay with BeanPoints at participating cafes and earn rewards with each purchase, tracked on the blockchain
  • BeanPoints earned at each café are non-transferable between merchants, ensuring true loyalty. Merchants control redemption terms and rewards rates
👤
USER
→
💵
LOAD CASH
TO BP
→
☕
ORDER
COFFEE
→
⭐
EARN
REWARDS
Business Model

The Business Model

With ~40,000 independent coffee shops nationwide serving 150 million daily coffee drinkers, the opportunity for a universal loyalty system is substantial.
Total Addressable Market
~$4.4B
Based on Starbucks' $1.75B stored value across 16K locations (~$109K per location), scaled to 40K independent shops. Formula: ($1.75B ÷ 16K) × 40K = $4.4B
Market Size
40K Shops
150M Drinkers
Independent coffee shops nationwide with millions of customers who lack access to robust loyalty rewards programs
Revenue Model
Dual Stream
Small flat fee for merchants to mint their loyalty program + yield generation from points held in protocol reserves
Competitive Analysis

How We're Different

There are existing platforms providing coffee rewards on chain, however our dApp is differentiated in several ways:

Feature
Traditional Chains
CoffeeChain
Established user base & brand trust
✓
✗ Requires merchant & user acquisition
Zero onboarding friction
✓
✗ Requires wallet setup (though abstracted)
Available to independent cafes
✗
✓
Universal wallet across cafes
✗
✓
Stablecoin-backed (no volatility)
✗
✓
Transparent, on-chain point ledger
✗
✓
Decentralized & permissionless
✗
✓
Interoperable rewards potential
✗
✓ Merchant opt-in roadmap

CoffeeChain doesn't need to beat Starbucks — it needs to give independent cafes tools they've never had access to.

Integrating crypto payments into everyday life—one coffee at a time