Use Accounts as customers公開プレビュー

With Accounts v2, you can use an Account object similarly to a Customer object by assigning it the customer configuration.

curl -X POST https://api.stripe.com/v2/core/accounts \
  -H "Authorization: Bearer 
sk_test_BQokikJOvBiI2HlWgH4olfQ2
" \
  -H "Stripe-Version: 2025-11-17.preview" \
  --json '{
    "contact_email": "jenny.rosen@example.com",
    "display_name": "Jenny Rosen",
    "identity": {
        "country": "us",
        "individual": {
            "given_name": "Jenny Rosen"
        }
    },
    "configuration": {
        "customer": {
            "capabilities": {
                "automatic_indirect_tax": {
                    "requested": true
                }
            }
        }
    },
    "include": [
        "configuration.customer",
        "identity"
    ]
  }'

When you use Accounts v2, your Stripe-hosted integrations, such as Checkout, create Accounts with the customer configuration. If your code references Customers, we recommend that you update it to reference customer-configured Accounts instead.

Provide an Account as the customer

API requests such as Subscriptions and SetupIntents require you to specify a customer. These requests accept either the customer or customer_account parameter. The following sample shows a subscription that specifies the customer by passing an Accounts v2 object as the customer_account.

curl https://api.stripe.com/v1/subscriptions \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:" \
  -H "Stripe-Version: 2025-04-30.preview" \
  -d customer_account=acct_xxxxx \
  -d "items[0][price]"=price_CBb6IXqvTLXp3f \
  -d "items[0][quantity]"=5

Reference Accounts in Customers v1 integrations

A request that specifies customer_account returns both customer and customer_account properties, with correspondingly formatted values. This maintains compatibility with existing Billing and Payments integrations.

{
  "id": "sub_1Mow234",
  .
  .
  .
  "customer": "cus_xxxxx",
  "customer_account": "acct_xxxxx"
}

You can also retrieve or update customer-configured Accounts using the /v1/customers endpoint.

curl -X POST https://api.stripe.com/v1/customers/acct_1234 \
  -u "
sk_test_BQokikJOvBiI2HlWgH4olfQ2
:"

Accounts v2 webhooks

Webhooks for Accounts v2 send thin events.

Customer invoice properties

Reference an Accounts v2 ID in a v1/customers path parameter

Accounts v2 doesn’t have endpoints for every customer function. To perform the following actions for an Accounts v2 object, use the v1/customers endpoint and pass the Account ID (acct_xxxxx) as the path parameter.