EDEBIT
(Part of an IBM Partner Programme)
EDEBIT Stablecoin Ecosystem
EDEBIT is a stablecoin built as a BEP-20 token on Binance Smart Chain (BSC), designed for microtransactions, fiat onboarding, and merchant integration across Web3 /Web2 platforms
The linking of EDEBIT to the .EDEBIT Web3 top-level domain (TLD), creates a decentralized payment and identity ecosystem where subdomains act as merchant storefronts or personal wallets
Web3 Twin: .EDEBIT (e.g., ShopName.EDEBIT)
Web2 Twin: edebit.site – onboarding, fiat on-ramp, KYC, support
Use Cases
Merchant Payments
Merchants register a subdomain (e.g., store.edebit)
Accept payments in EDEBIT tokens
Integrate Web3 checkout on Web2 twin
Freelancer Wallets
Users get a wallet and subdomain (e.g., Joseph.edebit)
Receive and store stablecoins, use for payments or cash out
Remittance and P2P
Micropayments
Send EDEBIT to another EDEBIT domain (e.g., send 20 EDEBIT to xyz.edebit)
10-Slide Investor Deck (Compressed & Boardroom-Ready)
Slide 1 — Title
Pay to Domain
Human-Readable Payments for Crypto & Stablecoins
Subtitle: Domains become payment infrastructure.
Slide 2 — The Problem
Crypto payments are still broken for everyday use.
Long addresses → irreversible mistakes
Wrong network → lost funds
Stablecoins ≠ currencies for users
Wallet UX assumes technical expertise
Result: low conversion, high support cost, slow adoption.
Slide 3 — The Insight
Payments need:
Names, not addresses
Currencies, not tokens
Resolvers, not custody
Domains are the missing abstraction layer.
Slide 4 — The Solution
Pay to Domain
Users send to:
jamaica.1
store.web-3
USD.EDEBIT
Resolvers translate domains into:
asset
network
address
routing policy
No custody. No new token. No key risk.
Slide 5 — How It Works
User enters a domain
Wallet calls resolver API
Resolver returns verified route
Wallet builds a normal transaction
User signs and sends
From the wallet’s POV: better address resolution.
Slide 6 — Currency Domains (.EDEBIT)
Domains can represent currencies, not just wallets.
USD.EDEBIT:
Routes payments to the best stablecoin
Selects lowest fees / fastest settlement
Adapts to recipient capabilities
Wallets don’t need FX logic.
Slide 7 — Business Model
Domain leasing (payment identities)
Resolver & API access (usage-based SaaS)
Currency routing fees (.EDEBIT)
White-label onboarding for partners
Recurring, infrastructure-grade revenue.
Slide 8 — Why This Is Hard to Copy
Domain-centric payment identity (not just ENS-style mapping)
Currency routing encoded as policy, not tokens
Non-custodial, resolver-based trust model
Wallet + browser + Web2 compatibility
Agentic AI optimising routing and UX over time
Each layer is simple alone — defensible together.
Slide 9 — Go-to-Market
Phase 1: Wallet integrations
Phase 2: Browsers & payment links
Phase 3: Merchants + fiat on-ramps
Phase 4: Standards & consortium adoption
Network effects compound with every domain published.
Slide 10 — The Ask
Strategic wallet & payment partners
Early enterprise merchants
Capital to scale standards adoption
Vision: Domains become the universal payment namespace.
