FloPay Backend Changelog

v1.10.36 - Statement descriptors can be saved on your company, collections and products #

The API now accepts an optional statementDescriptor on your company, collections and products, checks it when you save it and returns it in responses. Flopay does not send it to payment providers yet, so what customers see on their statements does not change.

Flopay is adding statement descriptors, the text a customer sees on their card or bank statement for a payment. With this release you can save that text through the API once for your whole company, for a collection or for a product. A saved descriptor is not sent to any payment provider yet, so payments and statements are unchanged.

What changed

• New statementDescriptor field. PATCH /company, product create and update, and collection create and update accept an optional statementDescriptor. It holds only the part of the statement text that follows your payment provider account's own prefix, for example SUCCESSWISE, not the full statement text.
• Saving, changing and clearing. Leading and trailing spaces are trimmed and the case is kept as sent. Sending null, "" or only spaces clears the value. Leaving the field out of an update keeps the value already saved.
• Validation. A value is refused with a 400 when it is longer than 18 characters, contains no letter, or contains any of < > \ ' " *. The error message names statementDescriptor and the rule that was broken.
• Updating your company. PATCH /company now accepts currency, statementDescriptor or both, and a body with neither is refused with a 400. A currency-only request works exactly as before, and the endpoint is still limited to owners and admins.
• Responses. Your company, a single product and collections, including the products listed inside a collection, now return statementDescriptor, which is null when nothing is set. The product list does not include it; read a single product to see it.
• Warnings list. Create and update responses for your company, products and collections now include statementDescriptorWarnings. Each entry is meant to flag one of your active gateways whose prefix leaves too little room for the saved descriptor, with gatewayId, gatewayName, prefix, maxLength and preview. A warning never blocks the save. No gateway reports its prefix yet, so the list is always empty in this release.
• MCP. Product_update, Collection_create and Collection_update show the statementDescriptor value in the preview you confirm. Company_update still changes only the reporting currency and refuses a request that includes statementDescriptor.

Why it matters

• Customers who do not recognise a charge are more likely to dispute it. Merchants selling several brands from one payment provider account can now record the statement text for each product, collection or the whole company. This is the foundation for showing that text on customers' statements.

Developer notes

• The new fields are additive and optional. Requests that do not send statementDescriptor behave as before. If your integration rejects unknown response fields, allow statementDescriptor and statementDescriptorWarnings.
• To set the company-level value, call PATCH /company directly; the Company_update MCP action does not accept it.
• Saving a descriptor does not change any payment request in this release.
• This release contains no breaking changes.