Billing belongs to the account that owns the plan, not to a team. A token reads and writes its own owner's billing, which is the same view that account gets on the dashboard's Billing page. Members of someone else's team see their own (usually free) billing here, not the owner's.
GET
/billing
Returns the plan, the billing recipients, the billing information and the tax ID types the API accepts.
PUT
/billing
Replaces whichever of the two blocks you send and leaves the other as it is. Requires the update token ability.
Fields
| Field | Type | Description |
|---|---|---|
billing_recipients |
string[] | Up to five email addresses. Every paid invoice is emailed to each as a PDF the moment Stripe reports it paid. Stored lower-cased and de-duplicated. Send an empty list to clear them. No verification step: these addresses only ever receive invoices. |
billing_information.company |
string | The company or legal name invoices are made out to. Leave empty to invoice the account holder by name. Does not change the account's own name. |
billing_information.address |
object | line1, line2, city, state, postal_code and country (two-letter code). Empty fields are dropped. |
billing_information.tax_id_type |
string | One of the keys in tax_id_types from the GET response, for example us_ein or eu_vat. Required when tax_id is set. |
billing_information.tax_id |
string | The tax or VAT number. Empty clears it. |
Billing information is saved on the account and pushed to the Stripe customer, which both the hosted invoice and the emailed PDF read from, so it appears on invoices from the next one on. If Stripe rejects it (an invalid tax ID, say), the local copy is kept and the response carries a warning string saying why.