I would like to know if it is possible to display the sales tax information for payments made through Web Payment SDK in the same manner as the checkout page.
I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:
Additional Documentation
Payments Pricing with Square APIs and SDKs
In-App Payments SDK: How It Works
Monetize your Application
If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.
Yes, it is possible to display sales tax information for payments made through the Web Payments SDK in a similar manner as the checkout page. When using the Web Payments SDK, you can customize the checkout flow to include detailed order information, including itemized sales tax. This involves creating an order with the appropriate tax information using Square’s APIs, such as the Orders API, which allows you to specify tax rates and apply them to the order items. This way, the sales tax details can be displayed to the buyer during the checkout process, similar to how it is shown on the checkout page.
This answer was reviewed by @Bryan-Square.
Workflow confirmation
I want to confirm whether the following workflow is correct when using the Web Payments SDK to display sales tax details to the buyer:
-
Create an order using the Orders API with itemized tax details included.
-
Retrieve the created order (for example, using the Orders API) and display the tax breakdown to the user during the Web Payments SDK checkout flow before completing payment.
Is this the recommended approach, or is there a more direct or optimized way to surface tax details in the Web Payments SDK UI?
Tax setup and location mapping clarification:
I want to confirm my understanding of how sales tax works with Square Orders:
-
First, tax rates are configured in Square for each location.
-
While creating an order, I pass the
location_id, and Square maps and applies the tax configured for that location. -
If this understanding is correct, does that mean I must pass a different
location_idwhen creating orders that originate from different locations? -
For an online website scenario, which location is used to determine tax:
-
the seller’s (merchant’s) Square location, or
-
the buyer’s address/location provided during checkout?
-
For displaying the tax that is the recommended approach. You’ll want to retrieve the order and display the tax from the itemized order.
As for taxes yes, you can have location specific taxes and when creating the order with auto_apply_taxes is true it will automatically apply the taxes. ![]()