Blog · Marketplace Engineering · 8-min read

Stripe Connect: Destination Charges vs. Separate Charges and Transfers (2027 Engineering Architecture)

Stripe Connect payment routing architecture diagram showing Destination Charges vs Separate Charges and Transfers

When architecting a two-sided marketplace on Stripe Connect, the single most critical structural decision is choosing between Destination Charges and Separate Charges and Transfers. This choice dictates how funds flow through your platform ledger, whether you can support multi-vendor shopping carts, who absorbs dispute financial liabilities, and how you satisfy FinCEN money transmission thresholds.

Marketplace Architecture Scope

Scope Your Marketplace Payment Architecture

We review your transaction flows, payout hold periods, and multi-vendor cart requirements to design a production Stripe Connect integration in 24 hours.

Request Payment Architecture Scope

1. Destination Charges: Single-Vendor Simplicity

In a destination charge, the buyer transacts directly with the platform, but the gross balance is immediately routed to a designated connected account. The platform specifies an application_fee_amount, which stays in the platform account as revenue:

const paymentIntent = await stripe.paymentIntents.create({
  amount: 15000, // $150.00 total
  currency: 'usd',
  application_fee_amount: 2250, // 15% platform take rate ($22.50)
  transfer_data: {
    destination: 'acct_1MnbX82Lwk9Z',
  },
});

Pros: Immediate transfer execution, minimal state tracking required, automatic tax documentation via Stripe 1099-K reporting.
Cons: Cannot split a single transaction across multiple vendors. Funds cannot be held past the seller's standard payout schedule without account-wide payout delay configurations.

2. Separate Charges and Transfers: Multi-Vendor & Escrow Control

Separate charges and transfers decouple the buyer payment from the seller disbursement. The platform collects gross funds, holds them in platform balance, and executes programmatic transfers to one or many connected sellers upon delivery verification:

// 1. Charge customer total cart balance across multiple vendors
const charge = await stripe.charges.create({
  amount: 32000, // $320.00
  currency: 'usd',
  source: paymentSourceToken,
  transfer_group: 'ORDER_GRP_59281',
});

// 2. Programmatic transfer to Seller A (e.g. $180.00 net)
await stripe.transfers.create({
  amount: 18000,
  currency: 'usd',
  destination: 'acct_SellerA_ID',
  transfer_group: 'ORDER_GRP_59281',
});

// 3. Programmatic transfer to Seller B (e.g. $92.00 net, retaining $48 platform fee)
await stripe.transfers.create({
  amount: 9200,
  currency: 'usd',
  destination: 'acct_SellerB_ID',
  transfer_group: 'ORDER_GRP_59281',
});

3. Architectural Decision Framework

Requirement Recommended Flow Key Technical Factor
1-on-1 Services / Single Bookings Destination Charges Fastest time to market (40-60 engineering hours)
Multi-Seller Retail Marketplace Separate Charges & Transfers Supports cart grouping via transfer_group
Inspection / Escrow Window (>48 hrs) Separate Charges & Transfers Platform retains control until delivery webhook

Next Steps for Marketplace Founders
Choose Your Conversion Path
Path 1 -- Inspect Production Code

Tour live custom marketplaces, Sharetribe builds, and payment flows engineered by our team.

View Client Case Studies →
Path 2 -- Scope & Pricing

Review fixed-price 8-12 week marketplace build scopes, milestone contracts, and warranties.

Explore Marketplace Pricing →
Path 3 -- Architecture Review

Direct 15-minute scoping call with Saif Akhtar (Head of Product & Engineering). No sales reps.

Book 15-Min Scoping Call →
No items found.

See what your project would cost.

Tell us what you're building. After an intro call with our founders, you'll hear back within 72 business hours: a written scope with an hour range and a hard ceiling, or the questions we need answered first.

Get an estimate
Book a call