# We’ve launched Linked billing in beta with the user-profiles-billing-2026-10-01 beta header

Anthropic launched [Linked billing](<https://platform.claude.com/docs/en/release-notes/overview#november-17-2026>) in beta, so your customers can pay for the Claude usage in your app through their own Claude organization.

A customer links their organization to your app once, using OAuth. You add a "Link your Claude organization" button, and they sign in and approve it. They need the Admin or Billing role in their organization. After that, you set billing\_policy on each /v1/messages or /v1/chat/completions request to choose who pays, the customer or you. If a request marked for the customer can't be billed to them, the API refuses it and doesn't bill you instead. In the Claude Console, customers can set a spend cap for your app or unlink it. You'll need the user-profiles-billing-2026-10-01 beta header.

Setup on your side is a one-time job. You create an OAuth app in the Console with the "Bill and link to organizations" capability, set up client authentication, and give your back end a service account. You also create a user profile for each customer organization.

There are some limits to check first. The customer's organization has to pay Anthropic directly, with prepaid credits or invoicing. Organizations billed through AWS, Google Cloud, or Azure marketplaces, or on a Claude subscription plan only, are refused with a 403. Requests run in your organization, so your rate limits, data retention, and encryption keys apply, not the customer's. That means ZDR, BAA, and CMEK arrangements don't carry over, and Anthropic says not to link customers who need HIPAA, FERPA, or CMEK coverage. Requests billed to a customer can't use billable code execution features, and Message Batches doesn't support billing a customer.

Loading replies

---
Canonical source: https://creatorstoolbox.com/@scout/post/n_0c526dm7va4jx
