# Use standalone mode with Connect

Enable connected accounts to accept in-person payments with standalone mode.

Standalone mode supports Connect for platforms. The charge type (direct, destination, or separate charges and transfers) is determined by how the reader is registered. Platforms can collect fees using the Platform pricing tool or revenue share. Configure Connect settings (on_behalf_of, transfer_data) in the standalone Configuration object.

Standalone mode supports [Connect](https://docs.stripe.com/terminal/features/connect.md). Platforms can provision readers for connected accounts to accept in-person payments without requiring them to write code.

## How it works

1. Platform registers a reader to the platform account or a connected account.
2. Platform enables standalone mode through a [Configuration](https://docs.stripe.com/terminal/payments/standalone-mode/customization.md) applied to the reader’s Location.
3. Reader collects payments. The [charge type](https://docs.stripe.com/connect/charges.md#types) is determined by how the reader is registered.
4. Funds flow to connected accounts according to your Connect charge type configuration.

## Charge types

The [charge type](https://docs.stripe.com/connect/charges.md#types) is determined by how the reader is registered:

- **[Direct charge](https://docs.stripe.com/connect/charges.md#direct)**: The reader is registered to a connected account through the platform.
- **[Destination charge](https://docs.stripe.com/connect/charges.md#destination)**: The reader is registered to the platform.
- **[Separate charges and transfers](https://docs.stripe.com/connect/charges.md#separate-charges-transfers)**: The reader is registered to the platform. After capturing the payment, you create separate transfers to move funds to connected accounts.

### Direct charges

For direct charges, the payment is created directly on the connected account. No additional Connect configuration is needed in the standalone mode Configuration — the charge type is determined entirely by how the reader is registered.

Register the reader to the connected account by doing one of the following:

- Include the `Stripe-Account` header in the API requests.
- Click **View as** in the Stripe Dashboard to act on behalf of the connected account.
- Have the connected account register the reader directly in the Dashboard or using their own API keys.

### Destination charges

For destination charges, the payment is created on the platform account and funds are automatically transferred to the connected account. You configure the routing in the standalone mode Configuration.

- **Merchant of record** (optional): Set `on_behalf_of` to make the connected account the business of record for the payment.
- **Transfer destination** (optional): Set `transfer_data[destination]` to immediately transfer funds from the platform to the connected account after the charge is captured.

#### Dashboard

1. Go to the [Terminal Locations](https://dashboard.stripe.com/terminal/locations) in your Stripe Dashboard.
2. Select an existing Location.
3. Click the edit icon (✏) next to the **Standalone mode** row under **Inherited configurations**.
4. **Under Connect**, configure the merchant of record and transfer destination settings.
5. Click **Update.**
6. Review the final configuration for the location, and click **Apply changes**.

### Separate charges and transfers

For [separate charges and transfers](https://docs.stripe.com/connect/charges.md#separate-charges-transfers), the payment is created on the platform account with no automatic transfer. After capturing the payment, create one or more [transfers](https://docs.stripe.com/api/transfers.md) to move funds to your connected accounts. You can optionally set `transfer_group` on the PaymentIntent metadata after creation to associate related payments and transfers. No additional Connect configuration is needed in the standalone mode Configuration.

## Collect platform fees

You can use the following approaches to collect platform fees on standalone mode payments:

- **[Platform pricing tool](https://docs.stripe.com/connect/platform-pricing-tools.md)**: A no-code solution that sets pricing logic for platform processing fees charged to your connected accounts. Use this when your platform is responsible for paying Stripe fees. Availability depends on [charge type](https://docs.stripe.com/connect/charges.md#types), [pricing model](https://docs.stripe.com/connect/platform-pricing-tools.md#eligibility-for-payments), and [payment method](https://docs.stripe.com/connect/payment-methods.md).
- **Revenue share**: Stripe pays your platform a portion of the processing fees that connected accounts pay. Use this when your platform uses direct charges and isn’t responsible for Stripe fees. [Contact sales](https://stripe.com/contact/sales) for eligibility.

## See also

- [Accept payments with no code](https://docs.stripe.com/terminal/payments/standalone-mode.md)
- [Customize standalone mode](https://docs.stripe.com/terminal/payments/standalone-mode/customization.md)
- [Connect charges](https://docs.stripe.com/connect/charges.md)
- [Platform pricing tools](https://docs.stripe.com/connect/platform-pricing-tools.md)