---
title: "How to easily charge customers across accounts in an organization"
description: "Stripe’s Organizations customer and payment method sharing addresses the difficulty of giving customers a unified checkout when a business uses separate accounts for business lines or countries. After access is enabled, all new and existing customers and their saved card payment methods can be shared between selected accounts, using the same IDs, so a saved card can be charged in another account without recollection. Only selected customer fields—such as name, email, phone, tax IDs, and preferred locales—are shared; metadata, shipping, and other fields remain account-specific, while non-card payment methods cannot be charged cross-account. The guide demonstrates testing in an organization sandbox, creating Checkout Sessions with the shared customer ID, viewing organization-wide transactions, and using a single organization webhook; sharing is in preview and requires customer consent."
---

# How to easily charge customers across accounts in an organization

[Stripe](https://yomu.fyi/company/stripe) · Daniel Wood · May 7, 2025

**Type:** Tutorial

## Summary

Stripe’s Organizations customer and payment method sharing addresses the difficulty of giving customers a unified checkout when a business uses separate accounts for business lines or countries. After access is enabled, all new and existing customers and their saved card payment methods can be shared between selected accounts, using the same IDs, so a saved card can be charged in another account without recollection. Only selected customer fields—such as name, email, phone, tax IDs, and preferred locales—are shared; metadata, shipping, and other fields remain account-specific, while non-card payment methods cannot be charged cross-account. The guide demonstrates testing in an organization sandbox, creating Checkout Sessions with the shared customer ID, viewing organization-wide transactions, and using a single organization webhook; sharing is in preview and requires customer consent.

## Context

Businesses using multiple Stripe accounts to isolate finances, report separately, or accept multiple currencies can struggle to provide a unified payment experience because cards can only be charged in the account where they were collected.

## Approach / What changed

Enable customer and payment method sharing between accounts in the same organization, test it in an organization sandbox, and reuse shared customer and card payment method IDs across Checkout Sessions. The integration can use an organization webhook for centralized, de-duplicated event handling.

## Takeaways

- Shared customers and card payment methods retain the same IDs across participating accounts, allowing a saved card to be used without recollecting billing details.
- Customer fields such as name, email, phone, tax IDs, and preferred locales are shared, while metadata, shipping, and other account-specific fields remain separate.
- Sharing cannot be selectively applied to customers or later disabled for an account, requires customer consent, and currently supports cross-account charging only for cards.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Developer Experience](https://yomu.fyi/topic/developer-experience), [Migrations](https://yomu.fyi/topic/migration)

- Source: [Stripe](https://stripe.dev/blog/how-to-charge-customers-across-accounts)
- Source URL: https://stripe.dev/blog/how-to-charge-customers-across-accounts
- Ingested by Yomu: 2026-08-28T08:58:48.051Z

[Read original post](https://stripe.dev/blog/how-to-charge-customers-across-accounts)