FloPay Backend Changelog

v1.7.23 - Single-client branding controls #

Authorized operators can now manage a merchant's customer-facing branding while each action remains scoped to one explicitly selected client.

Authorized operators can now read, replace, or clear branding on behalf of one explicitly selected client. Existing client-managed branding behavior remains unchanged.

What changed

• Operator-assisted branding management is restricted to one selected client for each action, with no implicit or cross-client fallback.
• The same whole-replacement and idempotent clear behavior now applies whether branding is managed by the client or by an authorized operator.
• The OpenAPI schemas for GET /v1/branding and PUT /v1/branding now describe nested SDK button styles and custom appearance rules more precisely.

Why it matters

• Operators can help merchants maintain consistent branding across SDK embeds, hosted checkout, branded emails, and other white-label experiences without affecting another client's configuration.
• Developers generating clients or forms from the OpenAPI specification receive more accurate branding types.

Developer notes

• Existing branding payloads and client authentication continue to work without changes.
• No SDK update, payload migration, or merchant action is required. This release contains no breaking changes or removed public APIs.