List of ErrorsThe request encoding is invalid. This happens when the wrong character encoding is used, the request contains unsupported special characters, or the Content-Type header is incorrect.

Root Cause

• Improper character encoding: The request did not use the correct encoding standard (e.g., UTF-8), leading to parsing errors.
• Unsupported special characters: The request body contains unsupported or invalid special characters that the gateway cannot process.
• Incorrect content-type header: The request did not specify the correct Content-Type header (e.g., application/json or application/x-www-form-urlencoded).

Troubleshooting and Solutions

• Verify that the request uses the correct character encoding standard, typically UTF-8.
• Ensure that the request payload does not contain unsupported special characters or invalid symbols.
• Confirm that the Content-Type header is correctly set based on the type of request payload being sent.
• If the problem persists, contact Chargebee Support with the full request details for further assistance.