Skip to main content

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.

The Transaction History endpoint returns a paginated list of your transactions, with optional filters for date range, payment status, app token, and terminal. Each row includes a settlement_status field indicating where the transaction sits in the settlement lifecycle. The endpoint has two branches selected by the type query parameter:
  • type=online (default) — returns card, wallet, and mobile-switch payments created through the online payment API.
  • type=pos — returns transactions processed by a POS terminal.
curl -X GET 'https://developers.flouci.com/api/developers/history?merchant_id=42&type=online&start_date=2026-05-20T00:00:00' \
  -H 'Authorization: Bearer <APP_PUBLIC>:<APP_SECRET>'

​
Query Parameters

​
merchant_id
integer
required
Identifier of the merchant whose history to query. The merchant must have developer API access enabled.
​
type
string
default:"online"
Which branch of the history to query. Either online (returns online payments — card, wallet, mobile switch) or pos (returns POS terminal transactions).
​
start_date
datetime
ISO-8601 datetime. Inclusive lower bound on the transaction creation time. Unbounded if omitted.
​
end_date
datetime
ISO-8601 datetime. Inclusive upper bound on the transaction creation time. Must be ≥ start_date and cannot be in the future.
​
operation_status
string
Optional status filter. Accepts the codes in the table below for both branches — POS queries map them internally to POS payment statuses.
​
app_token
uuid
Online only. Filter results to a specific app token recorded on the payment payload.
​
terminal_id
string
POS only. Restrict results to a single terminal. Maximum 16 characters. Returns a 1004 validation error if combined with type=online.

​
operation_status accepted values

The endpoint accepts the same status codes regardless of type. For POS queries the code is mapped internally.
CodeOnline (type=online)POS (type=pos)
S (Success)matches Successmatches PAYMENT_SUCCEEDED
AS (All success)matches Success, FlouciSuccess, MobileSwitchSuccessmatches PAYMENT_SUCCEEDED
PF (Payment failure)matches PaymentFailurematches PAYMENT_FAILED
P (Pending)matches Pendingmatches PAYMENT_PENDING
Other status codes are passed through verbatim with no automatic mapping.

​
Validation errors

CodeReason
1002start_date is later than end_date.
1003start_date or end_date is in the future.
1004terminal_id supplied together with type=online.

​
Response

The endpoint returns a paginated list. Each element is shaped according to the requested type. 
{
  "type": "card",
  "amount": 100000,
  "status": "SUCCESS",
  "details": {
    "name": "FOULEN BEN FOULEN",
    "approval_code": "182848"
  },
  "developer_tracking_id": "order_98231",
  "fee": 5000,
  "tva": 950,
  "settlement_status": "AVAILABLE"
}
​
type
string
required
Payment method used. One of card, flouci (wallet), mpayment (mobile switch), or NA.
​
amount
integer
required
Amount in millimes.
​
status
string
required
Payment status. One of SUCCESS, PENDING, EXPIRED, FAILURE, PREAUTH_SUCCESS, or SYSTEM_FAILURE.
​
details
object
Buyer information. Shape depends on the payment type.
​
developer_tracking_id
string
Your merchant-supplied reference. May be null.
​
fee
integer
Per-transaction fee in millimes. Returns an empty string "" until the fee has been computed.
​
tva
integer
VAT in millimes. Returns an empty string "" until computed.
​
settlement_status
string
required
Settlement lifecycle state for this transaction. See Settlement Status.

​
Examples

curl -X GET 'https://developers.flouci.com/api/developers/history?merchant_id=42&type=online&start_date=2026-05-20T00:00:00' \
  -H 'Authorization: Bearer <APP_PUBLIC>:<APP_SECRET>'
There is currently no query parameter to filter by settlement_status. To separate transactions by settlement state — for example, to identify what has already been wired to your bank versus what is still in flight — filter the returned list client-side on the settlement_status field.