Skip to content

PHASE5-SANDBOX-TO-B2B-PLAN.md

Latest commit

 

History

History
102 lines (71 loc) · 3.62 KB

PHASE5-SANDBOX-TO-B2B-PLAN.md

File metadata and controls

102 lines (71 loc) · 3.62 KB

Phase 5: Sandbox Live → B2B-Only Plan

Overview

Go live with the current sandbox (no real money) and position EmbiPay for a future B2B-only conversion. This avoids consumer-facing compliance while creating a path to monetization.

Phase 5A: Sandbox Go-Live (No Real Money)

Goal: Public launch of EmbiPay as a programmable sandbox for AI agent budgeting and lending. No payment provider, no real funds.

Checklist

  • Positioning & messaging

    • Emphasize: "Not a bank. Not real money. A programmable financial sandbox for agents."
    • Add clear disclaimer on signup, dashboard, and docs
    • Terms of Service: sandbox-only, experimental use

  • Production readiness

    • Analytics, health checks, monitoring in place
    • Rate limits, webhooks, SDKs published
    • Security: RLS, hashed keys, audit trail
    • Staging vs prod env separation (optional)

  • Launch

    • Developer Hub, docs, and sandbox live
    • npm/PyPI packages discoverable
    • Optional: waitlist or contact form for B2B interest

Risks (Sandbox)

  • None for payment/compliance—no real money.
  • Use disclaimers to avoid user expectations of real financial services.

Phase 5B: B2B-Only Conversion Path

Goal: When ready for real money, convert to B2B only to minimize regulatory scope.

Why B2B

  • Lower consumer-protection exposure — B2B contracts vs consumer disclosures
  • Simpler KYC — Business verification (EIN, incorporation docs) vs per-consumer ID
  • Fewer licenses — Money transmitter rules often have B2B carve-outs or lighter requirements
  • Partner-led — Use licensed payment providers (Stripe Connect, Dwolla, etc.) who hold the license

Prerequisites Before B2B Conversion

Area Action
Payment provider Integrate Stripe Connect, Dwolla, or similar; they handle card/bank rails and much of compliance
KYC (business) Collect: company name, EIN, address, authorized signers; use provider’s verification or partner (Plaid, Onfido)
Terms B2B agreement: business use only, no consumer accounts, indemnification
Account model Introduce “organization” or “tenant” layer: one org = one business, multiple agents/wallets under it
Pricing Usage-based (per wallet, per transaction, or tiered)

Architecture for B2B

Organization (B2B tenant)
  ├── Admin(s) — business users
  ├── Agent wallets — under org
  ├── Pools, loans — scoped to org
  └── Billing — tied to org (Stripe Customer)

Timeline (High-Level)

Stage What When
5A Sandbox go-live Now
5A+ Gather feedback, waitlist for B2B 1–3 months
5B.1 Org/tenant model, Stripe Connect integration When ready
5B.2 Business KYC, B2B terms Before real-money launch
5B.3 Soft launch with selected B2B partners Pilot
5B.4 General B2B availability After pilot validation

What to Build Now (Phase 5A)

  1. Disclaimers — Add to signup, dashboard, and docs
  2. Terms of Service — Sandbox-only, experimental
  3. B2B waitlist / contact — Capture interest for future conversion
  4. Org model (optional) — Lightweight “workspace” or “org” concept to prepare for B2B

What to Defer Until 5B

  • Payment provider integration
  • Real-money flows
  • Business KYC
  • Billing/monetization

This plan keeps the sandbox live and compliant today while defining a clear B2B-only path for future real-money operations.

See also: Marketing Plan — developer-led and B2B pipeline.