FloPay Backend Changelog

v1.7.32 - Faster release validation #

Pre-release end-to-end verification now concentrates on the areas a change can affect, shortening the path from fix to production without changing public product behavior.

This release improves how Flopay validates backend changes before they ship. Existing integrations continue to work unchanged; no public API, SDK, checkout flow, or webhook behavior has been modified.

What changed

• End-to-end verification before a release now targets the tests that a change can actually reach, based on which parts of the platform the change touches, instead of always re-running the entire suite.
• Changes that affect shared foundations, such as test infrastructure, build configuration, or database schema, continue to trigger the complete end-to-end suite.
• When no change scope is known, the full suite still runs, so validation coverage is never reduced by default.

Why it matters

• Fixes and improvements spend less time waiting on release verification, so they reach merchants sooner.
• Focused verification does not lower the bar: any change with broad reach is still validated in full.

Developer notes

• No SDK update, payload change, merchant configuration, migration, or operational action is required.
• This release contains no breaking changes or removed public APIs.