FloPay Backend Changelog

v1.7.29 - Stable rebill sequences in customer timelines #

Customer timeline responses now identify completed and upcoming subscription rebills with a consistent 1-based sequence.

Customer timelines now identify each completed subscription rebill by its chronological sequence. Merchants, developers, and operators can label renewal activity consistently without inferring rebills from event titles, amounts, timestamps, or provider-specific details.

What changed

• Every historical event in events and projected event in futureEvents now includes the additive, nullable rebillSequence field.
• A completed subscription rebill and its directly linked invoice expose the same 1-based sequence. Other historical activity, including opening payments, one-time payments, recovery retries, and non-completed authorization events, returns null.
• A future subscription.rebill event exposes the next expected sequence. Other future event types return null.
• Sequence numbers remain consistent as ordinary new rebills occur. Genuinely older imported activity may correct the chronological sequence in a later response.

Developer notes

• GET /v1/timelines/record?userUuid=<uuid> and GET /v1/timelines include rebillSequence on historical and future events. No request changes are required.
• Use rebillSequence for display and classification, but do not treat it as an immutable event or ledger identifier.
• This release is backward compatible. No SDK update, payload migration, configuration change, or merchant action is required.