> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flouci.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Recent additions and changes to the Flouci Payment API and developer documentation.

Track what's new in the Flouci Payment API. Entries are listed in reverse-chronological order.

<Update label="August 2026" description="Released August 17, 2026">
  ## Card payment error codes are now documented

  The [Error Dictionary](/essentials/error-dictionary) lists the 37 card payment error codes observed in production, with the verbatim message returned by the card processing platform, what each code means, and the action to offer your customer.

  Codes are also grouped into handling patterns so you can implement one behavior per pattern instead of a branch per code — including the two cases that need care: never retry `-2013` or `-2007` on the same order, and always verify the final state of the order after `100801` before offering a retry, to avoid a double debit.

  <Check>
    Documentation only — no API behavior changed. These codes were already returned by the platform.
  </Check>
</Update>

<Update label="May 2026" description="Released May 28, 2026">
  ## Settlement status on Verify and History responses

  Every transaction returned by the [Verify Payment](/api-reference/verify-transaction), [POS Get Transaction Status](/api-reference/get-pos-transaction-status), and [Transaction History](/api-reference/transaction-history) endpoints now carries a `settlement_status` field describing where the funds sit between the moment of payment and the moment they reach your bank account.

  The field is one of five values:

  * `PROCESSING` — succeeded card payment inside the T+1 settlement window
  * `AVAILABLE` — eligible for inclusion in the next payout
  * `IN_PAYOUT` — committed to a payout request, wire not yet sent
  * `PAID` — wired to your bank account (terminal state)
  * `NOT_APPLICABLE` — outside the settlement lifecycle (failed, refunded, pending, etc.)

  See the full reference in [Settlement Status](/api-reference/verify-transaction#settlement-status).

  <Check>
    This change is **additive and backward compatible** — existing `status` and `payment_status` fields are unchanged. Clients that ignore `settlement_status` see no behavior change.
  </Check>

  ## New Transaction History endpoint

  The [Transaction History endpoint](/api-reference/transaction-history) is now documented with full query-parameter, response, and filtering reference for both branches:

  * `type=online` — card, wallet, and mobile-switch payments
  * `type=pos` — POS terminal transactions

  Filters: date range, payment status (`operation_status`), `app_token` (online only), and `terminal_id` (POS only).
</Update>