LamportPay Whitepaper

USDC payments do not require a swap. LamportPay selects a conversion route from the enabled asset and its network:

• Solana / SPL assets → Jupiter → USDC. Jupiter supplies the conversion quote, including route costs and price impact. LIVE · read-only market quotes are available in the sandbox build; mainnet swap execution is DISABLED.
• Major digital assets → Hyperliquid → USDC. IN PROGRESS. This route is being built for deeper liquidity on assets such as BTC and ETH; it is not enabled for deposits.

Additional asset intake requires an explicit allowlist and a validated conversion route, not just a wallet balance.

The app offers configured destination countries and fills the payout currency from a country reference table. That reference is not a promise of coverage: Stables quotes determine whether a country/currency pair is available, and Stables validates the required bank fields. The sandbox build restricts the country picker to the destinations the Stables sandbox completes: the United States (USD), the United Kingdom (GBP), India (INR) and the Philippines (PHP). Nigeria (NGN) and Pakistan (PKR) are planned. Production coverage is not confirmed. Limits are shown in the payment app and checked before approval.

Beyond the current payout infrastructure, LamportPay plans a network of specialist payout partners, built corridor by corridor across six regions: North America, Europe, Asia, South America, Africa and Oceania. For each corridor the route is chosen on coverage, available liquidity, FX and total conversion cost, and settlement conditions. These regional partners are PLANNED and not yet confirmed.

The eight-step journey is a user-facing progress indicator, not a separate settlement ledger. Before transfer creation, LamportPay records payment setup, verification and quote stages. Once a Stables transfer exists, its status is authoritative and the app follows it without moving a payment backwards.

Signed webhooks are the primary update path. Live status reads and background reconciliation recover missed updates; a temporary provider error preserves the last stored status. Completion requires Stables to report completion, not merely a wallet signature. Some sandbox destinations may remain processing.

Refunds, compliance checks and manual reviews are operations cases, not invented payment states. A sandbox receipt records a demonstration only.

LamportPay's approved platform fee is 2% of the total the user sends, taken out of that total once. For a 150 USDC payment, 3 USDC is the LamportPay fee and 147 USDC is allocated to Stables—not 153 USDC leaving the wallet. Partner, swap and network costs remain separate and are disclosed before approval. The payment app displays the fee amount.

LamportPay fee

One fee, taken out of the total you send—not an extra conversion fee plus a swap fee. The app shows the fee amount before approval.

Payout partner fee

Stables costs are quoted separately. They are not included in LamportPay’s fee.

Swap & network costs

Any Jupiter swap costs, price impact and Solana network fees are separate. The sandbox build does not execute mainnet swaps or move payment funds.

Optional minimum and maximum fee bounds are off by default. In production, LamportPay's revenue transfer is separate from the Stables deposit within the user-signed transaction; no additional LamportPay swap fee is charged. The sandbox build collects no real revenue.

Early access: the first 10 people who join from the website's launch popup pay no LamportPay fee. Payout partner and network costs still apply to them.

The roadmap is tracked phase by phase. Phases 1–7 are complete; Phase 8 (security review and go-live) is the current focus and the main use of new funding. Later phases are goals, not confirmed partnerships or dates.

• Phase 1: Product core (Done). Defined the product: crypto in, local money out — non-custodial, one simple fee.✓ Business model and 2% fee model · ✓ Non-custodial payment design · ✓ Licensed payout partner selected (Stables)
• Phase 2: Infrastructure (Done). Set up the database, server logic and cloud hosting the platform runs on.✓ SQL (Postgres) database designed by the team · ✓ Node.js server logic, webhooks and reconciliation · ✓ Cloud hosting, test and live mode separation
• Phase 3: Planning and architecture (Done). Mapped every payment step, every phase gate and every compliance hand-off.✓ Phase plan with gates per phase · ✓ Payment journey and status model · ✓ Security and data-handling rules
• Phase 4: Frontend and app (Done). Built the website, the payment app and the admin tools.✓ Marketing website and docs · ✓ Payment app with wallet sign-in · ✓ Admin dashboard for operations
• Phase 5: Payment engine (Done). The engine that quotes, records fees and tracks each payment to the bank.✓ Quotes, fee calculation and fee ledger · ✓ Payment tracking and live status sync · ✓ Append-only audit log
• Phase 6: Testing (Done). Ran the full journey end to end in the partner sandbox with no real funds.✓ Sandbox payouts: US, UK, IN, PH · ✓ Automated tests and CI checks · ✓ Error and recovery cases
• Phase 7: Integrations (Done). Connected the partners that move value from wallet to bank.✓ Solana wallets (USDC, SOL) · ✓ Jupiter swap quotes · ✓ Stables payout and hosted verification (sandbox)
• Phase 8: Security review and go-live (In progress). Core security controls are built. This phase funds a full independent audit, penetration testing and hardening before a controlled mainnet launch.✓ Non-custodial: we never hold funds or keys · ✓ Signed webhooks and one-time wallet signatures · ✓ Admin sign-in with password + email code · ✓ Security scans passed, no critical issues · ○ Independent external security audit · ○ Penetration testing and hardening · ○ Monitoring, alerting and incident response · ○ Solana mainnet launch and Stables production payouts
• Phase 9: Marketing and go-to-market (Planned). Reach the first real users, then grow with content, community and partners.✓ Website, blog and FAQs live · ✓ Colosseum hackathon submission · ✓ Company channels live on X and LinkedIn · ○ First users from our own network · ○ Community campaigns on X, Telegram, Discord · ○ Content, SEO and creator partnerships · ○ Referral rewards and targeted ads
• Phase 10: Liquidity and asset integrations (Planned). Accept more assets through more liquidity. Hyperliquid work has started.○ Hyperliquid liquidity route (in progress) · ○ Bitcoin, Ethereum and major cryptocurrencies · ○ More liquidity-provider APIs
• Phase 11: Automation and security systems (Planned). The systems that run the platform safely every day: automation, data rules and controls.✓ Database access rules on every table · ✓ Tamper-proof audit log and fee ledger · ✓ Rate limits and emergency payment controls · ✓ Automated secret and dependency scans · ✓ Automatic payment status sync and reconciliation · ✓ Free Ask AI assistant (Lammy) for customer questions · ✓ Complaints routed to the admin dashboard · ○ Automatic email and in-app payment updates · ○ Daily reports and alerts for operations
• Phase 12: Partnerships and market expansion (Planned). More partners and more countries. Not confirmed yet.○ Circle and Tether partnership talks · ○ More payout API providers · ○ New countries such as Nigeria and Pakistan · ○ Regional payout partner network across six regions
• Phase 13: Global payout ecosystem (Planned). A worldwide crypto-to-bank network for people and businesses.○ Remittance for families and workers · ○ B2B payouts for businesses · ○ All major cryptocurrencies, more chains and mobile

These controls do not guarantee a risk-free service or establish a completed security certification. Production remains disabled until the dedicated security phase (independent audit, penetration testing and hardening), end-to-end validation and operational readiness are complete.