Why can't I connect a Chargebee test site to an Avalara production account?
Problem Statement
Chargebee does not support connecting a Chargebee test site to Avalara production credentials. The Avalara integration shows Avalara credentials provided are invalid, even when the account number, license key, and company code are correct. This limit is documented under Limitations on AvaTax for Sales.
Related Scenarios
- You see Avalara credentials provided are invalid while connecting Avalara on a Chargebee test site.
- You need to know which Avalara environment to use with a Chargebee test site.
Solution
Chargebee does not support connecting a Chargebee test site to Avalara production credentials. This protects data integrity between the test site and Avalara production data. Chargebee shows Avalara credentials provided are invalid even when the account number, license key, and company code are correct.
Use Avalara sandbox credentials on the Chargebee test site. Testing on a Chargebee test site works only with those sandbox credentials.
- Get Avalara sandbox credentials from Avalara if you do not already have a sandbox account.
- On the Chargebee test site, go to Apps > Go to Marketplace > Tax Management > Avalara.
- Click Get Started, choose AvaTax for Sales, and enter the sandbox account number, license key, and company code.
- Click Proceed. The integration connects, and Chargebee does not show Avalara credentials provided are invalid.
Finish address validation and sync rules in Connect an Avalara account.
Important Notes
- Chargebee blocks this pairing so a test site cannot write to Avalara production data.
- Every connection on a Chargebee test site, including a reconnect, needs Avalara sandbox credentials.
- A wrong company code is a separate error. See Avalara sync error: Company not found.