Extension build

The Codex-executable sequence for turning 2Settle into a browser extension product without blocking on every unfinished platform feature first.

Phase A · Ready

Extension shell and shared contracts (45-60h)

Create the browser extension foundation and the API client layer it will share with the web app.

Scaffold popup, side panel, settings, and authenticated session storage.
Centralize API client helpers so extension and future mobile app do not fork request logic.
Add a module registry so unfinished features can launch as shells without blocking the core extension.

Phase B · Next

Deliver the core value proposition: users can paste a 2Settle checkout link, inspect it, fund it with crypto, and track the payment.

Resolve payment-link details from the backend and display amount, merchant, bank target, and available methods.
Fetch quotes, create the payment intent, request a deposit address, and show confirmation steps in the extension.
Replace UI-only confirmation timers with real status polling or webhook-backed transitions where needed.

Phase C · Planned

Make the extension useful for operators and merchants, not just payers.

Create payment links directly from the extension.
Generate merchant QR links and quick-copy sharing actions.
Show lightweight merchant metrics and recent transactions using the existing dashboard APIs.

Phase D · Planned

Expose the full 2Settle surface in the extension while keeping unfinished areas honest and clearly labeled.

Add Bills, Subscription, Cards, Remittance, History, and Settings sections to the extension navigation.
Use a consistent shell pattern: feature summary, current state, Open in 2Settle App CTA, and update badge.
Avoid fake success flows in shell modules so users know which actions are live versus upcoming.

Phase E · Backend First

Finish the backend work the extension depends on so it can move from impressive demo to reliable product.

Create real Payment records during checkout flows instead of only generating payment links and simulated statuses.
Persist receipts, status transitions, and transaction history in the database.
Strengthen auth, observability, and end-to-end tests around extension-critical flows.

Did this extension build plan make the implementation order feel clear?

We can keep tightening the roadmap and tracker as the build moves forward.