Call POST /v1/tax/registrations with a country (ISO 3166-1 alpha-2) and a country_options object describing the specific registration type for that country — for example, a US state registration requires country_options[us][state] and country_options[us][type] such as state_sales_tax
Set active_from to 'now' or a future Unix timestamp to control exactly when Stripe starts treating the business as registered in that jurisdiction
Understand that creating the Registration object does not itself register the business with the tax authority — you must complete the actual government registration separately and then record it here
List /v1/tax/registrations to audit which jurisdictions have an active registration before turning on automatic_tax on PaymentIntents or Subscriptions, since Stripe Tax silently skips calculation in jurisdictions without an active registration rather than raising an error
To stop collecting tax in a jurisdiction, set expires_at on the registration instead of trying to remove it
Known gotchas
A Tax Registration object cannot be deleted once created; the only way to turn it off is to expire it via expires_at, which is a one-way change
Recording a registration in Stripe has no legal effect on your actual tax-authority registration status — sequencing matters: register with the authority first, then record it in Stripe
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?