FloPay Backend Changelog

v1.10.37 - Product updates that send a null free-trial setting no longer fail #

A product update that sends `recurringTrialPeriodDaysFree` as `null` now succeeds and keeps the product's current trial setting, instead of failing with a server error.

Updating a product with PATCH /v1/products/{uuid} and sending recurringTrialPeriodDaysFree: null failed with a 500 server error. The request now succeeds.

What changed

• When a product update sends recurringTrialPeriodDaysFree as null, Flopay treats the field as not sent. The product keeps its current setting for whether its trial is free, and the rest of the update is applied.
• Updates that leave the field out, or send true or false, behave exactly as before.

Why it matters

• Integrations that send every product field on update, including empty ones as null, can update products without a server error.
• An empty value never switches a product's trial between free and paid, so the trial stays as the merchant set it.

Developer notes

• No endpoint, request or response field, validation rule or SDK export changed.
• To change whether a product's trial is free, send true or false. Sending null leaves the current setting in place.
• No merchant action is required. This release contains no breaking changes.