Tax-exclusive pricing: the published price is not the final card charge
Tax-exclusive pricing means the provider’s displayed amount leaves applicable tax outside the quoted total. It changes the bill by adding tax at checkout according to the buyer’s billing details and the provider’s tax rules. The displayed price is therefore a pre-tax observation, not a promise that the same amount will be charged to every buyer. If the provider does not publish tax treatment, the missing field cannot be treated as tax-free.
A published price with an unpublished final total
ProxyScrape’s Unlimited Residential 1 day, 100 Mbps plan publishes a $190 checkout in its pricing API. Its terms separately state that prices are net in U.S. dollars and that VAT and applicable taxes are added at checkout based on billing details. The plan therefore has a published pre-tax price of $190, while the final card charge for a taxable buyer is greater than $190 by an amount the dataset cannot calculate without that buyer’s location and tax status. ProxyScrape 100 Mbps price, retrieved 2026-07-25T16:33:08.221Z ProxyScrape tax terms, retrieved 2026-07-25T16:33:08.221Z
That missing final amount should remain missing. Applying one assumed VAT rate to every buyer would manufacture a universal receipt that the provider does not publish. Treating the tax as zero would make the opposite error. The complete result preserves the $190 pre-tax amount, the explicit tax-exclusive state, and the instruction to confirm the checkout for the actual billing address.
Tax-exclusive is also different from tax-inclusive. A provider that explicitly says tax is included supports a final displayed total for the stated configuration. A provider that says nothing supports neither conclusion. The three states are a published exclusion, a published inclusion, or not published.
Five providers publish the structured field
In the current 710-row dataset, 5 of 47 providers publish taxes_excluded as true on at least one plan: AnyIP, ASocks, NodeMaven, Ping Proxies, and ProxyScrape. The field is populated on 85 plan rows. The other 42 providers remain null for this field, so the dataset does not call their prices tax-inclusive or tax-free. Current tax-treatment publication data
The snapshot does not contain a false value that proves tax inclusion for another provider. It also does not store buyer-specific tax rates. Those limits are useful because they prevent a published unit rate or minimum checkout cost from being presented as a universal card charge.
Before comparing receipts, hold currency and tax treatment constant where possible. If that is not possible, label each observed amount as tax-exclusive or not published and compare the provider totals before tax. Then verify the actual checkout immediately before payment. The right answer is an incomplete but sourced bill, not a precise total built from an assumed tax rate.