Non-ASCII Header Validation

Fixed an issue where requests containing non-ASCII characters in their headers caused a server error; such requests now correctly receive a standard bad-request response instead.

How it benefits the Merchant

This prevents malformed requests from causing unexpected server errors, improving platform stability and making error handling more predictable for integrations.

Potential FAQs

Q: Does this affect normal customer traffic?

A: Unlikely — this affects requests with non-ASCII characters in headers, which is an edge case rather than typical customer traffic.

Q: Do I need to update any integrations because of this?

A: Check with your account manager if you have custom integrations sending non-standard headers; otherwise no action is needed.