FloPay Backend Changelog

v1.7.25 - Accurate canceled trial timelines #

Customer timelines no longer show a trial ending after a Flo-managed subscription is already scheduled to cancel or pause.

Customer timelines now reflect the actual lifecycle of Flo-managed trials when a cancellation or pause is scheduled near the trial boundary. Customers and support teams see the action that will take effect, without an additional trial-end step that will not occur.

What changed

• The subscription.trial_end future event is omitted when a scheduled cancellation or pause takes effect on or before the trial boundary.
• The scheduled cancellation or pause remains visible in the timeline.
• When the cancellation or pause is scheduled after the trial boundary, the trial-end event remains visible before it.

Why it matters

• Customer journeys no longer suggest that a canceled or paused trial will continue through a separate trial-end step.
• Merchants and operators receive a clearer, chronologically accurate view of upcoming subscription activity.

Developer notes

• Timeline request and response schemas are unchanged. Integrations should continue to treat futureEvents as the current projected schedule rather than assuming that every trial includes a subscription.trial_end event.
• No SDK update, payload migration, merchant configuration, or operational action is required.