Seller Onboarding

Before users can sell on the marketplace, they need to complete seller onboarding. This connects them to Stripe Connect so they can receive payments. The process varies based on whether they’re a casual seller or a business — we call these “Individual” and “Pro” sellers.

Seller Types

We offer two paths for becoming a seller, designed for different use cases:

The Onboarding Flow

Here’s how the onboarding process works for each seller type:

Seller Status States

Sellers go through various status states during and after onboarding. Understanding these helps when debugging why a seller can or can’t do something.

Here’s what each status means and what the seller can do:

Country Selection

During onboarding, sellers choose their country. This is a one-time decision that can’t be changed later.

The country determines:

• Which region they’re in (NA or EU)
• Which currency they receive payouts in
• What tax and regulatory requirements apply

Supported Countries

Shipping Rates

Every seller gets default shipping rates based on their country — they can start selling immediately after onboarding without any additional configuration.

Default Rates

We provide sensible default rates for each supported country, covering all three shipping zones:

Default rates vary by country to reflect typical postal costs. For example, a US seller’s defaults might be $4.00 domestic small,$12.00 global small — while a French seller’s defaults are €3.00 domestic small, €10.00 global small.

Customizing Rates

Sellers can override the defaults in their shipping settings:

Package sizes are determined by product type:

• Cards: XSmall (1-5 cards), Small (6-50 cards), Medium (51-250 cards), Large (251+ cards)
• Sealed products: Based on category — cases are XLarge, boxes/bundles are Large, boosters/packs are Medium

The Stripe Connect Data Model

Here’s what we store about a seller’s Stripe Connect account:

interface UserStripeConnect {
  accountId: string           // Stripe's acct_xxx ID
  sellerType: 'individual' | 'pro'
  country: string             // ISO 3166-1 alpha-2 code
  onboardingStatus: OnboardingStatus
  payoutsEnabled: boolean     // Can they receive money?
  pendingRequirements: string[]  // What Stripe needs
  pendingVerification: string[]  // What's being verified
  requirementsDeadline?: Date    // When requirements are due
  firstSaleAt?: Date          // For KYC leniency period
  canSell: boolean            // Can they list items?
}

Embedded Components (Custom Mode)

We use Stripe Connect in custom mode with embedded components. Instead of redirecting sellers to Stripe’s hosted dashboard, we embed Stripe’s UI components directly in our app. This gives us full control over the seller experience while Stripe handles the secure data collection.

Available Embedded Components

The backend controls which components are enabled based on seller status:

Webhook Sync

Stripe sends account.updated webhooks whenever something changes about a seller’s account:

• Requirements added or removed
• Verification completed
• Payouts enabled or disabled
• Account restricted

Our webhook handler syncs this data back to the user’s profile so we always have an up-to-date view of their status.

Seller Fees

When a sale happens, we take a cut. The fee is calculated as a percentage of the order total (subtotal + shipping):

Fees are deducted when funds are released to the seller, not at checkout time. See Fund Management for details on when and how funds are released.

Common Issues

Here are problems you might encounter and how to resolve them:

API Endpoints

Code Locations