FloPay Backend Changelog

v1.7.33 - Production release safeguards #

Production releases now wait for comprehensive end-to-end verification, reducing the risk of unverified changes reaching merchants.

This release strengthens the final verification step before backend changes become available in production. When comprehensive end-to-end checks identify a problem, the release is held until a corrected version has passed verification.

What changed

• Production releases now wait for the complete end-to-end test result before proceeding.
• A failed or incomplete result prevents the affected version from being released.
• Releases can still proceed when no additional verification result is expected, preserving support for exceptional maintenance releases.

Why it matters

• Merchants benefit from an additional reliability safeguard between a merged backend change and its production release.
• Failed verification no longer depends on manual intervention to prevent the affected version from being deployed.

Developer notes

• No public API, SDK, webhook payload, status-code, or configuration contract has changed.
• No SDK update, payload migration, configuration change, or merchant action is required. This release contains no breaking changes or removed public APIs.