Improved Webhook Payload Encoding

Feature Flag Rollout: Starting in two weeks, we will begin a gradual rollout of a new feature designed to enhance the reliability and consistency of webhook deliveries for our partners.

Details
Issue Resolved: We've identified an issue where webhooks would fail to be delivered if the payload contained certain characters not supported by the 'Latin-1' encoding (such as emojis). This resulted in undelivered webhooks.

Feature Overview: To resolve this, we've introduced a new encoding strategy. When enabled, webhook payloads will be encoded in 'UTF-8', ensuring compatibility with a wider range of characters. This change is specifically aimed at preventing failed deliveries due to encoding errors.

Backwards Compatibility: We understand changes like these can be sensitive. Therefore, this feature is placed behind a feature flag. The current behaviour will remain the default until the flag is enabled for your account.

Rollout Plan: The rollout will begin in two weeks and will be conducted in phases. We will enable the feature flag for select customers, closely monitoring for any disruptions or issues. Assuming all goes well, we will continue to enable the feature for more customers incrementally.

No immediate action is required. However, we encourage partners to:

Monitor Announcements: Stay tuned for future updates when this feature flag is enabled for your account.
Review Integrations: If you maintain integrations that rely on our webhooks, please review them to ensure they can handle 'UTF-8' encoded payloads.
Provide Feedback: Once the feature flag is enabled for you, please monitor your systems and report any issues or unexpected behaviour. Your feedback is invaluable and will guide any necessary adjustments.