Valid Tax ID Scenarios
The Sandbox supports specific Tax IDs for deterministic test cases. Use only the values listed below for expected behavior.Tax Rate Simulation
These combinations return predictable tax calculations in the Sandbox.Request Parameters
Request Parameters
Request Parameters
Product & Delivery
Product & Delivery
product_id
: (string, optional) – Internal product identifier.product_category
: (string, optional) – Required ifproduct_id
is absent. Acceptable values include:CSS
,DTSP
,DAW
,DAVW
,DB
,DP
,IAAS
,PAAS
,SAAS
,PRSFT
,RNGT
,DSWS
,GMO
,SSS
,DTSS
,INGMO
is_security
: (boolean, optional) – Indicates if product is classified as a financial/security item.delivery_method
: (string, required) – One of:CLOUD
,PHYSICAL
,DOWN
Customer
Customer
customer_id
: (string, optional) – Internal customer identifier.customer_type
: (string, optional) – Used if nocustomer_id
is provided. One of:B2C
,B2B
,PRISCH
,PRIEDUI
,GOV
,PUBSCH
,PUBEDU
,PRIHOS
,PUBHOS
,NGO
Location
Location
country
: (string, required) – ISO country code.state
,county
,postal_code
,ip_address
: (optional) – Additional location context.
Tax ID Validation
Tax ID Validation
tax_id
: (string, required) – The tax identifier to validate.customer_name
: (string, optional) – Used for name matching with registry.
Response Fields
Response Fields
Response Fields
Tax Calculation
Tax Calculation
taxability
: (boolean) – Whether the product is taxable.country_rate
,state_rate
,county_rate
,special_rate
,additional_rate
,total_rate
: (integer) – Tax rates in basis points.reverse_charge_applicable
: (boolean) – Reverse charge status.exempt
: (boolean) – Whether tax is fully exempt.
Tax ID Validation
Tax ID Validation
tax_id_valid
: (boolean) – Whether the ID is valid.customer_name_registry
: (string) – Name returned by registry.customer_name_match
: (boolean) – If provided name matches registry.customer_type
: (string) – Inferred customer type.validated_country
,validated_state
: (string) – Jurisdictional confirmation.registry_address
: (string) – Registry’s address (if available).validation_source
: (string) – Validation source such asVIES
,GSTN
.validation_timestamp
: (string) – ISO timestamp of the validation.request_id
: (string) – Internal reference for debugging and audits.
Notes
18000
= 18%.product_id
takes precedence over product_category
if both are present.customer_id
takes precedence over customer_type
if both are present.Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Headers
Optional. Unique key to ensure idempotent operations (e.g., retry-safe requests).
Body
ID of the product
Customer ID
Country code (ISO Alpha-2)
Tax Identification Number
Product category if ID is unavailable
CSS
, DTSP
, DAW
, DAVW
, DB
, DP
, IAAS
, PAAS
, SAAS
, PRSFT
, RNGT
, DSWS
, GMO
, SSS
, DTSS
, INGMO
Is the product a financial security?
Product delivery mode
CLOUD
, PHYSICAL
, DOWN
Customer type if ID not provided
B2C
, B2B
, PRISCH
, PRIEDUI
, GOV
, PUBSCH
, PUBEDU
, PRIHOS
, PUBHOS
, NGO
State/region
County/district
Postal code
IP address for geolocation
Customer name (for validation match)
Response
Unified tax result and tax ID validation
Whether the product is taxable
Country-level tax rate (×1000)
State-level tax rate (×1000)
County-level tax rate (×1000)
Any additional surcharge (×1000)
Special tax rate (×1000)
Final total rate (×1000)
Is reverse charge applicable?
Is this transaction exempt from tax?
Whether the tax ID is valid
Name retrieved from tax registry
Does the input name match registry?
Source used for validation
Internal ID for auditing and tracing