FloPay Backend Changelog

v1.7.24 - Paginated checkout link listings #

Merchants can now page, filter, search, and sort checkout links through a consistent API contract.

Checkout link management now supports bounded pagination and documented query controls, making large link catalogs easier to browse and integrate with operational tooling.

What changed

• GET /v1/checkout-links now returns { data, page, limit, pages, total } instead of a bare array.
• Results can be filtered, searched, and sorted using the query fields and operators published in the OpenAPI specification. The existing default order remains newest first.
• Pagination is 1-based, with a default limit of 20 and a maximum of 100.
• Unknown parameters, malformed values, unsupported operators, limits above 100, and non-empty relation values now return 400 instead of being ignored.

Why it matters

• Merchants and operators can work with large checkout-link catalogs without requesting every link at once.
• API clients can use the returned totals and page counts to build predictable navigation, exports, and management views.

Developer notes

• Breaking change: consumers of GET /v1/checkout-links must read checkout-link records from the data field and use page, limit, pages, and total for pagination. Integrations that relied on receiving every link in one request must paginate through the result set.
• Review existing query parameters against the published OpenAPI contract before upgrading; unsupported or invalid list queries now receive a 400 response.
• Other checkout-link endpoints and their request and response payloads are unchanged. No merchant configuration or data migration is required.