The Settlements endpoints expose the financial liquidation records that summarize what a business earns from a period’s orders after Zippi’s commission and payment gateway fees are deducted. All monetary amounts are integers in centavos (COP) — never floats. Settlements are immutable once generated: they represent a locked financial snapshot that can be audited and reproduced at any future point.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CRISTIANCAMACH34/Zippi/llms.txt
Use this file to discover all available pages before exploring further.
How settlement amounts are calculated
For each settlement period, the net payout to the business is computed as:fecha_vigencia_desde; it does not retroactively alter any already-generated settlement.
Commission rates are versioned. The
tasa_comision field on the Negocio model stores the current rate (e.g. "12.00" for 12%). Each settlement record stores the exact rate that was applied at generation time, ensuring full reproducibility during financial audits months or years later.GET /api/v1/business/settlements
Returns a paginated list of settlement periods for the authenticated business scope. Supports filtering by date range and branch.business_owner, business_admin, cashier, super_admin, or platform_admin (module: settlements).
Query parameters
ISO 8601 date (e.g.
2024-01-01). Returns settlements whose period starts on or after this date.ISO 8601 date (e.g.
2024-01-31). Returns settlements whose period ends on or before this date.Filter settlements for a specific branch. When omitted, all branches in the business scope are included.
Page number, 1-indexed.
Records per page. Recommended maximum: 100.
200 OK
Unique identifier for the settlement record.
ISO 8601 date marking the start of the settlement period.
ISO 8601 date marking the end of the settlement period.
Branch scope of the settlement.
null for business-level aggregated settlements.Gross revenue from all completed orders in the period, in centavos. Always an integer.
Zippi commission deducted, in centavos. Computed as
bruto × tasa_comision_aplicada / 100.Decimal string of the commission rate that was active when this settlement was generated (e.g.
"12.00" for 12%). Immutable after generation.Payment gateway fees (Wompi, Nequi, etc.) deducted, in centavos.
Net adjustments in centavos (negative = deductions for refunds/reversals; positive = credits). May be
0.Net amount to be transferred to the business:
bruto − comision_zippi − fee_pasarela + ajustes. Always an integer in centavos.Settlement lifecycle state. Values:
generada (generated, awaiting transfer), pagada (transferred to business), en_disputa (under review), ajustada (corrected by finance admin).ISO 8601 UTC datetime when the settlement record was created.
GET /api/v1/business/settlements/:id
Returns the full detail of a single settlement, including the list of order IDs included in the period, a breakdown of all fee components, and the audit trail of who generated it.200 OK
Sampled list of
id_pedido values included in this settlement. For large periods, only the first and last N order IDs may be returned here; the full list is available via the export endpoint.Total count of orders included in the period’s calculation.
Actor that triggered settlement generation:
system_job for scheduled generation, or the user_id of a finance admin who triggered it manually.Internal version tag of the commission schedule applied. Use this to look up the exact rate table in the platform audit log.
ISO 8601 UTC datetime when the net amount was transferred to the business.
null if the settlement is still in generada state.