I need a reliable way to ensure the QR payload stays under the 331-byte limit so banking apps can scan it successfully.

Provide a built-in QR payload size check that measures the exact encoded byte length before generating the QR code. This helps ensure the final QR remains under the 331-byte limit, improving scan reliability across banking apps.

This feature validates the final QR payload size against a 331-byte limit before QR generation. It calculates the encoded byte length of the payload as it will be embedded in the QR, rather than relying on character counts. When the payload exceeds the limit, the system blocks generation and clearly indicates that the payload is too large to be reliably scanned by banking apps. The user is shown the current byte size and the remaining available bytes to help them adjust the content. The feature supports iterative editing by re-checking the byte size as the payload changes. It is intended for workflows where QR codes must be accepted by banking applications that enforce strict payload limits. This reduces trial-and-error by catching size issues early and consistently. It also lowers the risk of producing QR codes that render visually but fail at scan time due to payload size constraints. Typical use cases include payment QR creation, bank-transfer QR templates, and any QR-based banking integration where interoperability is critical.