New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates


  • Release Notes

Getting Started


  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee


  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

Agentic AI


  • Chargebee Copilot
  • Catalog Setup Assistant
  • MCP Servers

Developer Resources


  • Developer Resources Overview
  • API Explorer
  • Articles and FAQ

Chargebee Apps


  • Chargebee Apps CLI Developer Guide

Product Catalog


  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions


  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers


  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements


  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing


  • Overview
  • Use Cases
  • Setting up Usage Based Billing
  • Usage Alerts
  • Prepaid credits
  • Mid-term Subscription Changes
  • FAQs

Invoices and Credit Notes


  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes


  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

E-Invoicing


  • Overview
  • Enabling E-Invoicing

Hosted Capabilities


  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Mobile SDKs and Wrappers
  • Articles and FAQ

Site Configuration


  • Add Users & Assign Roles
  • Chargebee Notifications
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • OAuth Apps
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity


  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions


  • Overview
  • Omnichannel Subscriptions
  • Omnichannel Subscriptions (Legacy)

Reports and Analytics


  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations


  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • E-Invoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • Articles and FAQ

Data Privacy & Security


  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations


  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  2. Developer Resources
  3. Articles and FAQ
  4. API & Integration
  1. Billing
  2. Developer Resources
  3. Articles and FAQ
  4. API & Integration

How to resolve sign-up modal issue with API v3 caused by incorrect Avalara configuration?

When using Chargebee's API version v3 in a test instance, you might encounter a sign-up modal error. This issue can occur if there is an incorrect configuration of the Avalara company code within Chargebee. This article explains how to resolve this error by correcting the Avalara company code configuration.

Solution

Follow these steps to resolve the sign-up modal error in your Chargebee test instance:

  1. Access the Chargebee Dashboard: Log in to your Chargebee account and navigate to the test instance where the error is occurring.

    • Ensure you have the necessary permissions to modify configuration settings.
  2. Navigate to Avalara Settings: Go to Settings > Configure Chargebee > Taxation > Avalara.

    • This section allows you to manage Avalara integration settings.
  3. Verify the Company Code: Check the company code configured in the Avalara settings.

    • Ensure that the company code matches the one provided by Avalara for your test instance.
  4. Correct the Company Code: If the company code is incorrect

  5. To update the company code, you need to go to Manage Preferences > Click Update > Enter License key > Connect

    • Click Save to apply the changes.
  6. Test the Configuration: After updating the company code, test the sign-up process again to ensure the error is resolved.

    • If the issue persists, double-check the company code and consult Avalara documentation for further guidance.

Important Notes

  • Ensure that the Avalara integration is correctly set up before testing the sign-up process.
  • The company code is case-sensitive and must match exactly with Avalara's records.
  • If you encounter further issues, consider checking other configuration settings or contacting Chargebee support for assistance.
  • Regularly review and update your test instance configurations to prevent similar issues in the future.

Was this article helpful?