Collect taxes

Use Stripe Tax APIs to implement tax calculations in your custom integration.

Stripe Tax APIs enable you to calculate tax in custom payment flows. After your customer completes their payment, record the transaction so it appears in Stripe Tax reporting. The examples in this guide use Stripe payments APIs, but you can use the Tax API with any payment processor, or multiple payment processors.

For most integrations, we recommend using the Checkout Sessions API with Stripe Tax.

Alternatively, you can integrate Stripe Tax with Payment Links, Checkout, Billing, and Invoicing with no or low code setups.

If your custom payment flow uses the Payment Intents API, see Calculate tax in your custom payment flows. This integration offers automatic liability tracking, receipts and Dashboard support. We also offer a public preview feature that lets you use the Tax ID Element to collect tax IDs from customers. See Collect customer tax IDs below for more information.

Alternatively, you can integrate Stripe Tax with Payment Links, Checkout, Billing, and Invoicing with no or low code setups.

Get started

This short video walks through a Stripe Tax API integration that uses the Payment Intents API and the Payment Element.

Loading video content...

Add registrations

Stripe Tax only calculates tax in jurisdictions where youâ€™re registered to collect tax. You must add your registrations in the Dashboard.

OptionalCollect customer address
Client-side

Calculate tax
Server-side

You choose when and how often to calculate tax. For example, you can:

Show a tax estimate based on your customerâ€™s IP address when they enter your checkout flow
Recalculate tax as your customer types their billing or shipping address
Calculate the final tax amount to collect when your customer finishes typing their address

Stripe charges a fee per tax calculation API call. You can throttle tax calculation API calls to manage your costs.

The examples below show how to calculate tax in a variety of scenarios. Stripe Tax only calculates tax in jurisdictions where youâ€™re registered to collect tax. You must add your registrations in the Dashboard.

Example:

This example calculates tax for a US shipping address. The line item has a price of 10 USD and uses your accountâ€™s preset tax code.

The calculation response contains amounts you can display to your customer, and use to take payment:

Attribute	Description
amount_total	The grand total after calculating tax. Use this to set the PaymentIntent amount to charge your customer.
tax_amount_exclusive	The amount of tax added on top of your line item amounts and shipping cost. This tax amount increases the `amount_total`. Use this to show your customer the amount of tax added to the transaction subtotal.
tax_amount_inclusive	The amount of tax thatâ€™s included in your line item amounts and shipping cost (if using tax-inclusive pricing). This tax amount doesnâ€™t increase the `amount_total`. Use this to show your customer the tax included in the total theyâ€™re paying.
tax_breakdown	A list of tax amounts broken out by country or state tax rate. Use this to show your customer the specific taxes youâ€™re collecting.

Handle customer location errors

The calculation returns the customer_tax_location_invalid error code, if your customerâ€™s address is invalid or isnâ€™t precise enough to calculate tax:

{
  "error": {
    "doc_url": "https://docs.stripe.com/error-codes#customer-tax-location-invalid",
    "code": "customer_tax_location_invalid",
    "message": "We could not determine the customer's tax location based on the provided customer address.",
    "param": "customer_details[address]",
    "type": "invalid_request_error"
  }
}

If you receive this error, prompt your customer to check the address they entered and fix any typos.

Use calculation with another processor

If you process transactions outside of Stripe, you can skip the following steps and apply the calculation to your externally-processed transactions.

Create tax transaction
Server-side

Creating a tax transaction records the tax youâ€™ve collected from your customer, so that later you can download exports and generate reports to help with filing your taxes. You can create a transaction from a calculation until the expires_at timestamp, 90 days after itâ€™s created. Attempting to use it after this time returns an error.

Note

The transaction is considered effective on the date when create_from_calculation is called, and tax amounts wonâ€™t be recalculated.

When creating a tax transaction, you must provide a unique reference for the tax transaction and each line item. The references appear in tax exports to help you reconcile the tax you collected with the orders in your system.

For example, a tax transaction with reference pi_123456789, line item references L1 and L2, and a shipping cost, looks like this in the itemized tax exports:

ID	line_item_id	type	currency	transaction_date
pi_123456789	L1	external	usd	2023-02-23 17:01:16
pi_123456789	L2	external	usd	2023-02-23 17:01:16
pi_123456789	shipping	external	usd	2023-02-23 17:01:16

When your customer pays, use the calculation ID to record the tax collected. You can do this in two ways:

If your server has an endpoint where your customer submits their order, you can create the tax transaction after the order is successfully submitted.
Listen for the payment_intent.succeeded webhook event. Retrieve the calculation ID from the PaymentIntent metadata.

The example below creates a transaction and uses the PaymentIntent ID as the unique reference:

Store the tax transaction ID to record refunds later. You can store the transaction ID in your database or in the PaymentIntentâ€™s metadata:

Record refunds
Server-side

After creating a tax transaction to record a sale to your customer, you might need to record refunds. These are also represented as tax transactions, with type=reversal. Reversal transactions offset an earlier transaction by having amounts with opposite signs. For example, a transaction that recorded a sale for 50 USD might later have a full reversal of -50 USD.

When you issue a refund (using Stripe or outside of Stripe), you must create a reversal tax transaction with a unique reference. Common strategies include:

Append a suffix to the original reference. For example, if the original transaction has reference pi_123456789, then create the reversal transaction with reference pi_123456789-refund.
Use the ID of the Stripe refund or a refund ID from your system. For example, re_3MoslRBUZ691iUZ41bsYVkOg or myRefund_456.

Choose the approach that works best for how you reconcile your customer orders with your tax exports.

Fully refund a sale

When you fully refund a sale in your system, create a reversal transaction with mode=full.

In the example below, tax_1MEFAAI6rIcR421eB1YOzACZ is the tax transaction that records the sale to your customer:

This returns the full reversal transaction thatâ€™s created:

{
  "id": "tax_1MEFtXI6rIcR421e0KTGXvCK",
  "object": "tax.transaction",
  "created": 1670866467,
  "currency": "eur",
  "customer": null,
  "customer_details": {
    "address": {
      "city": null,
      "country": "IE",

Fully reversing a transaction doesnâ€™t affect previous partial reversals. When you record a full reversal, make sure you fully reverse any previous partial reversals for the same transaction to avoid duplicate refunds.

Partially refund a sale

After issuing a refund to your customer, create a reversal tax transaction with mode=partial. This allows you to record a partial refund by providing the line item amounts refunded. You can create up to 30 partial reversals for each sale. Reversing more than the amount of tax you collected returns an error.

The example below records a refund of only the first line item in the original transaction:

This returns the partial reversal transaction thatâ€™s created:

{
  "id": "tax_1MEFACI6rIcR421eHrjXCSmD",
  "object": "tax.transaction",
  "created": 1670863656,
  "currency": "eur",
  ...
  "line_items": {
    "object": "list",
    "data": [
      {

For each line item reversed, you must provide the amount and amount_tax reversed. The amount is tax-inclusive if the original calculation line item was tax-inclusive.

How amount and amount_tax are determined depends on your situation:

If your transactions always have a single line item, use full reversals instead.
If you always refund entire line items, use the original transaction line item amount and amount_tax, but with negative signs.
If you refund parts of line items, you must calculate the amounts refunded. For example, for a sale transaction with amount=5000 and amount_tax=500, after refunding half the line item, you create a partial reversal with line item amount=-2500 and amount_tax=-250.

Tax reports with partial refunds

If you refund a tax amount such that the total tax is no longer proportional to the subtotal, your tax reporting can be unreliable. It wonâ€™t automatically adjust the taxable and nontaxable amounts, and wonâ€™t reflect the reason for the tax reversal (such as product exempt, customer exempt, or reverse charge). We recommend not refunding partial line item tax amounts. Instead, void the transaction and create a new one with appropriate inputs for an accurate tax calculation.

Partially refund a sale by a flat amount

Alternatively, you can create a reversal with mode=partial by specifying a flat after-tax amount to refund. The amount distributes across each line item and shipping cost proportionally, depending on the remaining amount left to refund on each.

In the example below, the transaction has two line items: one 10 USD item and one 20 USD item, both taxed at 10%. The total amount of the transaction is 33.00 USD. A refund for a flat 16.50 USD is recorded:

This returns the partial reversal transaction thatâ€™s created:

{
  "id": "tax_1NVcQYBUZ691iUZ4SBPukGa6",
  "object": "tax.transaction",
  "created": 1689780994,
  "currency": "usd",
  ...
  "line_items": {
    "object": "list",
    "data": [
      {

For each line item and shipping cost in the original transaction, the refunded amounts and tax are calculated as follows:

First, we calculate the total remaining funds in the transaction available to refund. Because this transaction hasnâ€™t had any other reversals recorded, the total amount is 33.00 USD.
Next, we calculate the total amount to refund for each line item. We base this calculation on the proportion of the itemâ€™s total available amount to refund versus the total remaining amount of the transaction. For example, the 10 USD item, which has 11.00 USD total remaining to refund, represents 33.33% of the transactionâ€™s remaining total, so the total amount to refund is -16.50 USD * 33.33% = -5.50 USD.
Finally, the total amount to refund is divided between amount and amount_tax. We also do this proportionally, depending on how much tax is available to refund in the line item compared to the total funds left to refund. Using the 10 USD item example, tax (1.00 USD) represents 9.09% of the total remaining to refund (11.00 USD), so the amount_tax is -5.50 USD * 9.09% = -0.50 USD.

The flat amount distributes according to whatâ€™s left to refund in the transaction, not what was originally recorded. For example, instead of recording a refund for a flat 16.50 USD, you first record a partial reversal for the total amount of the 10 USD item:

After this, you record a 16.50 USD flat amount reversal:

This returns the partial reversal transaction:

{
  "id": "tax_1NVxFIBUZ691iUZ4saOIloxB",
  "object": "tax.transaction",
  "created": 1689861020,
  "currency": "usd",
  ...
  "line_items": {
    "object": "list",
    "data": [
      {

Because the total amount remaining in the transaction is now 22.00 USD and the 10 USD item is completely refunded, the 16.50 USD distributes entirely to the 20 USD item. The 16.50 USD then distributes, using the logic from step 3, into amount = -15.00 USD and amount_tax = -1.50 USD. Meanwhile, the 10 USD item in the transaction records a refund of 0 USD.

Undo a partial refund

Tax transactions are immutable, but you can cancel a partial refund by creating a full reversal.

You might need to do this when:

The payment refund fails and you havenâ€™t provided the good or service to your customer
The wrong order is refunded or the wrong amounts are refunded
The original sale is fully refunded and the partial refunds are no longer valid

In the example below, tax_1MEFACI6rIcR421eHrjXCSmD is the transaction that represents the partial refund:

This returns the full reversal transaction thatâ€™s created:

{
  "id": "tax_1MEFADI6rIcR421e94fNTOCK",
  "object": "tax.transaction",
  "created": 1670863657,
  "currency": "eur",
  ...
  "line_items": {
    "object": "list",
    "data": [
      {

Testing

Use sandboxes, which is identical in response structure to live mode, to confirm your integration works correctly before going live.

Warning

In testing environments, calculations arenâ€™t guaranteed to return up-to-date taxation results. Youâ€™re limited to 1,000 tax calculations per day. If you need a higher limit, contact Stripe support. For guidance on automated testing and strategies to avoid rate limits in testing environments, see Automated testing.

View tax transactions

You can view all tax transactions for your account on the Tax Transactions page in the Dashboard. Click an individual transaction to see a detailed breakdown of calculated tax by jurisdiction, and by the individual products included in the transaction.

Note

The Tax Transactions page only includes transactions and not calculations. If you expect to see a calculation and canâ€™t find it on this page, verify that you successfully created a tax transaction from the calculation.

OptionalIntegration examples

OptionalCalculate tax on shipping costs
Server-side

OptionalEstimate taxes with an IP address
Server-side

OptionalCollect customer tax IDs
Server-side

OptionalTax-inclusive pricing
Server-side

OptionalUse an existing Product object
Server-side

OptionalUse an existing Customer object
Server-side

OptionalOverride customer taxability
Server-side

OptionalSpecify a ship-from location
Server-side

OptionalCalculate the retail delivery fee
Server-side

OptionalDetailed line item tax breakdowns
Server-side

OptionalTroubleshoot common errors
Server-side

Collect customer tax IDs

Displaying a customerâ€™s tax ID and legal business name on invoices is a common requirement. You can use the Tax ID Element to collect this information. This feature is in public preview.

Disclaimer

The Payment Intents API is designed to collect business tax IDs, which might have formats similar to personal tax IDs in certain jurisdictions. You must make sure that only business tax IDs, as designated for this field, are provided when using this feature.

Enable the beta

The Tax ID Element with the Payment Intents API requires you to enable the elements_tax_id_1 beta. Add the beta to your Stripe.js initialization:

const stripe = Stripe('pk_test_TYooMQauvdEDq54NiTphI7jx'
, {
  betas: ['elements_tax_id_1'],
});

Create a CustomerSession (optional)

If you want to save tax IDs to a Customer and redisplay them for returning customers, you need to create a CustomerSession. The CustomerSession provides secure, temporary access to customer data without exposing your secret API key to the client.

If you donâ€™t use CustomerSession, the Tax ID Element still works but without save and redisplay functionality. You can use getValue to read the tax ID values from the element and handle them manually.

First, create or retrieve a Customer:

Create a CustomerSession with the Tax ID Element component enabled:

The CustomerSession returns a client_secret that youâ€™ll pass to the client side.

Create a PaymentIntent or SetupIntent

Create a PaymentIntent or SetupIntent on your server. When using CustomerSession, include the customer parameter to enable tax ID save and redisplay functionality:

Note

You donâ€™t need to include any tax-ID-specific parameters when creating the PaymentIntent or SetupIntent. The Tax ID Element automatically handles tax ID collection and saves it to the Customer when a CustomerSession with the appropriate permissions is present.

Initialize Elements

Create an Elements instance using the clientSecret from your PaymentIntent or SetupIntent.

To enable saving tax IDs to a Customer and redisplaying them for returning customers, include the customerSessionClientSecret:

const stripe = Stripe('pk_test_TYooMQauvdEDq54NiTphI7jx'
, {
  betas: ['elements_tax_id_1'],
});

// Fetch the clientSecret from your server
const {clientSecret} = await fetch('/create-payment-intent', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
}).then((res) => res.json());

// Fetch the customerSessionClientSecret from your server
const {customerSessionClientSecret} = await fetch('/create-customer-session', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
}).then((res) => res.json());

const elements = stripe.elements({
  clientSecret,
  customerSessionClientSecret,
  appearance: { /* ... */ }
});

Create and mount the Tax ID Element

Create an instance of the Tax ID Element and mount it to your page:

<form id="payment-form">
  <div id="tax-id-element">
    <!--Stripe.js injects the Tax ID Element-->
  </div>
  <button type="submit">Pay</button>
</form>

const taxIdElement = elements.create('taxId', {
  visibility: 'auto', // 'auto' | 'always' | 'never'
});
taxIdElement.mount('#tax-id-element');

You can customize the Tax ID Element with options such as visibility, fields, and validation. See Create a Tax ID Element for more details.

Use with Address Element (optional)

When you use the Tax ID Element with the Address Element, Stripe automatically determines the tax ID type and element visibility based on the customerâ€™s address.

Complete the payment

When the customer submits the payment form, call confirmPayment or confirmSetup. Stripe automatically includes the tax ID information and saves it to the Customer if the payment succeeds:

const form = document.getElementById('payment-form');

form.addEventListener('submit', async (event) => {
  event.preventDefault();

  const {error} = await stripe.confirmPayment({
    elements,
    confirmParams: {
      return_url: 'https://example.com/order/complete',
    },
  });

  if (error) {
    // Handle error
    console.error(error.message);
  }
  // Customer gets redirected to return_url if successful
});

You can also use getValue on the client side to read the tax ID values before submitting the payment.

Test your integration

In testing environments, you can enter any alphanumeric string that is in the correct format of a supported tax ID type (for example, DE123456789 for eu_vat). For a full list of example tax IDs you can reference our Customer Tax ID guide. You can also use our test tax IDs to test various verification state flows.

Tax ID validation

During payment or setup confirmation, Stripe verifies that the provided tax IDs are formatted correctly, but not that theyâ€™re valid. Youâ€™re responsible for ensuring the validity of customer information. To help, Stripe automatically performs asynchronous validation against government databases for European Value Added Tax (EU VAT) and United Kingdom Value Added Tax (GB VAT) numbers. Learn more about the validation we perform, and how to consume the status of those checks.

Supported Tax ID types

The Tax ID Element supports tax ID collection in the following countries and regions:

Country	Enum	Description	Example	Impact in Tax Calculation

Albania	`al_tin`	Albania Tax Identification Number	J12345678N	Yes
Angola	`ao_tin`	Angola Tax Identification Number	5123456789	No
Armenia	`am_tin`	Armenia Tax Identification Number	02538904	Yes
Aruba	`aw_tin`	Aruba Tax Identification Number	12345678	Yes
Australia	`au_abn`	Australian Business Number (AU ABN)	12345678912	Yes
Austria	`eu_vat`	European VAT number	ATU12345678	Yes
Azerbaijan	`az_tin`	Azerbaijan Tax Identification Number	0123456789	Yes
Bahamas	`bs_tin`	Bahamas Tax Identification Number	123.456.789	No
Bahrain	`bh_vat`	Bahraini VAT Number	123456789012345	Yes
Bangladesh	`bd_bin`	Bangladesh Business Identification Number	123456789-0123	Yes
Barbados	`bb_tin`	Barbados Tax Identification Number	1123456789012	No
Belarus	`by_tin`	Belarus TIN Number	123456789	Yes
Belgium	`eu_vat`	European VAT number	BE0123456789	Yes
Benin	`bj_ifu`	Benin Tax Identification Number (Identifiant Fiscal Unique)	1234567890123	Yes
Bosnia & Herzegovina	`ba_tin`	Bosnia and Herzegovina Tax Identification Number	123456789012	Yes
Bulgaria	`eu_vat`	European VAT number	BG0123456789	Yes
Burkina Faso	`bf_ifu`	Burkina Faso Tax Identification Number (NumÃ©ro d'Identifiant Fiscal Unique)	12345678A	Yes
Cambodia	`kh_tin`	Cambodia Tax Identification Number	1001-123456789	Yes
Cameroon	`cm_niu`	Cameroon Tax Identification Number (NumÃ©ro d'Identifiant fiscal Unique)	M123456789000L	No
Canada	`ca_bn`	Canadian BN	123456789	No
Canada	`ca_gst_hst`	Canadian GST/HST number	123456789RT0002	Yes
Canada	`ca_pst_bc`	Canadian PST number (British Columbia)	PST-1234-5678	No
Canada	`ca_pst_mb`	Canadian PST number (Manitoba)	123456-7	No
Canada	`ca_pst_sk`	Canadian PST number (Saskatchewan)	1234567	No
Canada	`ca_qst`	Canadian QST number (QuÃ©bec)	1234567890TQ1234	Yes
Cape Verde	`cv_nif`	Cape Verde Tax Identification Number (NÃºmero de IdentificaÃ§Ã£o Fiscal)	213456789	No
Chile	`cl_tin`	Chilean TIN	12.345.678-K	Yes
Congo - Kinshasa	`cd_nif`	Congo (DR) Tax Identification Number (NÃºmero de IdentificaÃ§Ã£o Fiscal)	A0123456M	No
Costa Rica	`cr_tin`	Costa Rican tax ID	1-234-567890	No
Croatia	`eu_vat`	European VAT number	HR12345678912	Yes
Cyprus	`eu_vat`	European VAT number	CY12345678Z	Yes
Czech Republic	`eu_vat`	European VAT number	CZ1234567890	Yes
Denmark	`eu_vat`	European VAT number	DK12345678	Yes
Ecuador	`ec_ruc`	Ecuadorian RUC number	1234567890001	No
Egypt	`eg_tin`	Egyptian Tax Identification Number	123456789	Yes
Estonia	`eu_vat`	European VAT number	EE123456789	Yes
Ethiopia	`et_tin`	Ethiopia Tax Identification Number	1234567890	Yes
Finland	`eu_vat`	European VAT number	FI12345678	Yes
France	`eu_vat`	European VAT number	FRAB123456789	Yes
Georgia	`ge_vat`	Georgian VAT	123456789	Yes
Germany	`eu_vat`	European VAT number	DE123456789	Yes
Greece	`eu_vat`	European VAT number	EL123456789	Yes
Guinea	`gn_nif`	Guinea Tax Identification Number (NÃºmero de IdentificaÃ§Ã£o Fiscal)	123456789	Yes
Hungary	`eu_vat`	European VAT number	HU12345678	Yes
Iceland	`is_vat`	Icelandic VAT	123456	Yes
India	`in_gst`	Indian GST number	12ABCDE3456FGZH	Yes
Ireland	`eu_vat`	European VAT number	IE1234567AB	Yes
Italy	`eu_vat`	European VAT number	IT12345678912	Yes
Kazakhstan	`kz_bin`	Kazakhstani Business Identification Number	123456789012	Yes
Kenya	`ke_pin`	Kenya Revenue Authority Personal Identification Number	P000111111A	No
Kyrgyzstan	`kg_tin`	Kyrgyzstan Tax Identification Number	12345678901234	No
Laos	`la_tin`	Laos Tax Identification Number	123456789-000	No
Latvia	`eu_vat`	European VAT number	LV12345678912	Yes
Liechtenstein	`li_vat`	Liechtensteinian VAT number	12345	Yes
Lithuania	`eu_vat`	European VAT number	LT123456789123	Yes
Luxembourg	`eu_vat`	European VAT number	LU12345678	Yes
Malta	`eu_vat`	European VAT number	MT12345678	Yes
Mauritania	`mr_nif`	Mauritania Tax Identification Number (NÃºmero de IdentificaÃ§Ã£o Fiscal)	12345678	No
Mexico	`mx_rfc`	Mexican RFC number	ABC010203AB9	No
Moldova	`md_vat`	Moldova VAT Number	1234567	Yes
Montenegro	`me_pib`	Montenegro PIB Number	12345678	No
Morocco	`ma_vat`	Morocco VAT Number	12345678	Yes
Nepal	`np_pan`	Nepal PAN Number	123456789	Yes
Netherlands	`eu_vat`	European VAT number	NL123456789B12	Yes
New Zealand	`nz_gst`	New Zealand GST number	123456789	Yes
Nigeria	`ng_tin`	Nigerian Tax Identification Number	12345678-0001	No
North Macedonia	`mk_vat`	North Macedonia VAT Number	MK1234567890123	Yes
Norway	`no_vat`	Norwegian VAT number	123456789MVA	Yes
Oman	`om_vat`	Omani VAT Number	OM1234567890	Yes
Peru	`pe_ruc`	Peruvian RUC number	12345678901	Yes
Philippines	`ph_tin`	Philippines Tax Identification Number	123456789012	Yes
Poland	`eu_vat`	European VAT number	PL1234567890	Yes
Poland	`pl_nip`	Polish NIP number	1234567890	No
Portugal	`eu_vat`	European VAT number	PT123456789	Yes
Romania	`eu_vat`	European VAT number	RO1234567891	Yes
Russia	`ru_inn`	Russian INN	1234567891	Yes
Russia	`ru_kpp`	Russian KPP	123456789	Yes
Saudi Arabia	`sa_vat`	Saudi Arabia VAT	123456789012345	Yes
Senegal	`sn_ninea`	Senegal NINEA Number	12345672A2	No
Serbia	`rs_pib`	Serbian PIB number	123456789	No
Singapore	`sg_gst`	Singaporean GST	M12345678X	Yes
Slovakia	`eu_vat`	European VAT number	SK1234567891	Yes
Slovenia	`eu_vat`	European VAT number	SI12345678	Yes
South Africa	`za_vat`	South African VAT number	4123456789	Yes
South Korea	`kr_brn`	Korean BRN	123-45-67890	Yes
Spain	`es_cif`	Spanish NIF number (previously Spanish CIF number)	A12345678	No
Spain	`eu_vat`	European VAT number	ESA1234567Z	Yes
Suriname	`sr_fin`	Suriname FIN Number	1234567890	Yes
Sweden	`eu_vat`	European VAT number	SE123456789123	Yes
Switzerland	`ch_vat`	Switzerland VAT number	CHE-123.456.789 MWST	Yes
Taiwan	`tw_vat`	Taiwanese VAT	12345678	Yes
Tajikistan	`tj_tin`	Tajikistan Tax Identification Number	123456789	Yes
Tanzania	`tz_vat`	Tanzania VAT Number	12345678A	Yes
Thailand	`th_vat`	Thai VAT	1234567891234	Yes
Turkey	`tr_tin`	Turkish Tax Identification Number	0123456789	Yes
Uganda	`ug_tin`	Uganda Tax Identification Number	1014751879	Yes
Ukraine	`ua_vat`	Ukrainian VAT	123456789	Yes
United Arab Emirates	`ae_trn`	United Arab Emirates TRN	123456789012345	Yes
United Kingdom	`eu_vat`	Northern Ireland VAT number	XI123456789	Yes
United Kingdom	`gb_vat`	United Kingdom VAT number	GB123456789	Yes
Uruguay	`uy_ruc`	Uruguayan RUC number	123456789012	Yes
Uzbekistan	`uz_tin`	Uzbekistan TIN Number	123456789	No
Uzbekistan	`uz_vat`	Uzbekistan VAT Number	123456789012	Yes
Zambia	`zm_tin`	Zambia Tax Identification Number	1004751879	No
Zimbabwe	`zw_tin`	Zimbabwe Tax Identification Number	1234567890	No

Use tax IDs in calculations (optional)

In some cases, such as the cross-border supply of services, your customer might need to account for tax on a reverse charge basis. Instead of collecting the tax, you must issue an invoice with the text, â€œTax to be paid on reverse charge basis.â€

When you provide your customerâ€™s tax IDs to Stripe Tax, we automatically determine when reverse charge applies:

If you provide a tax ID with an invalid format, the calculation returns a tax_id_invalid error code.

Collect taxes

Use Stripe Tax APIs to implement tax calculations in your custom integration.

Get started

Add registrations

OptionalCollect customer addressClient-side

Calculate taxServer-side

Handle customer location errors

Use calculation with another processor

Create tax transactionServer-side

Note

Record refundsServer-side

Fully refund a sale

Partially refund a sale

Tax reports with partial refunds

Partially refund a sale by a flat amount

Undo a partial refund

Testing

Warning

View tax transactions

Note

OptionalIntegration examples

OptionalCalculate tax on shipping costsServer-side

OptionalEstimate taxes with an IP addressServer-side

OptionalCollect customer tax IDsServer-side

OptionalTax-inclusive pricingServer-side

OptionalUse an existing Product objectServer-side

OptionalUse an existing Customer objectServer-side

OptionalOverride customer taxabilityServer-side

OptionalSpecify a ship-from locationServer-side

OptionalCalculate the retail delivery feeServer-side

OptionalDetailed line item tax breakdownsServer-side

OptionalTroubleshoot common errorsServer-side

Collect customer tax IDs

Disclaimer

Enable the beta

Create a CustomerSession (optional)

Create a PaymentIntent or SetupIntent

Note

Initialize Elements

Create and mount the Tax ID Element

Use with Address Element (optional)

Complete the payment

Test your integration

Tax ID validation

Supported Tax ID types

Use tax IDs in calculations (optional)

See also

OptionalCollect customer address
Client-side

Calculate tax
Server-side

Create tax transaction
Server-side

Record refunds
Server-side

OptionalCalculate tax on shipping costs
Server-side

OptionalEstimate taxes with an IP address
Server-side

OptionalCollect customer tax IDs
Server-side

OptionalTax-inclusive pricing
Server-side

OptionalUse an existing Product object
Server-side

OptionalUse an existing Customer object
Server-side

OptionalOverride customer taxability
Server-side

OptionalSpecify a ship-from location
Server-side

OptionalCalculate the retail delivery fee
Server-side

OptionalDetailed line item tax breakdowns
Server-side

OptionalTroubleshoot common errors
Server-side