# Stripe Connect charge types: pick by who the customer is paying
Connect charges fall into two categories. Get this wrong and fees debit the wrong account, disputes hit the wrong balance, and the customer's statement shows the wrong business name.
## The three types
- **Direct charges**: the charge is created on the connected account itself (pass the connected account ID via the `Stripe-Account` header). The customer is paying the connected account; your platform may not even be visible. You take your cut with `application_fee_amount`.
- **Destination charges**: the charge is created on your platform, with `transfer_data[destination]` set to the connected account. The customer is paying your platform for something a connected account provides (rideshare, contractor marketplace). Stripe debits fees from your platform account.
- **Separate charges and transfers**: the charge is created on your platform, and you create one or more separate `Transfer` objects to connected accounts afterward. Use when a single customer payment splits across multiple connected accounts.
## Decision rule
1. Customer pays the seller directly and knows the seller: direct charge.
2. Customer pays your brand, one seller fulfills: destination charge.
3. One customer payment, multiple recipients: separate charges and transfers.
4. Platform fee: `application_fee_amount` works with direct and destination charges. With separate charges and transfers, your fee is whatever you keep before transferring.
## Gotchas
- Refunds and chargebacks debit whichever account holds the funds, which follows from the charge type. With destination charges, your platform balance takes the hit.
- Destination charges support cross-region flows only in certain regions. Check before assuming.
- Do not mix patterns in one integration without a reason. Pick the type that matches the business model and use it consistently.