An Installment represents a single due-date charge (internally a Statement) belonging to a Subscription Buyer, Single Payment Buyer, or Payment Plan. Installments are created automatically — you don't create them directly, they're generated according to the recurrence and value of the parent service. The only write action available on them directly is Mark installment as refunded.
Status Values
The object supports seven statuses: pending, paid, expired, refunded, processing_payment, processing_refund, and refunded_manually.
JSON Structure Example
{
"id": "b2c1a0f0-1111-2222-3333-444455556666",
"status": "paid",
"currency": "CLP",
"name": null,
"external_id": null,
"due_date": "2026-08-05",
"created_at": "2026-08-01T09:00:00",
"payment_date": "2026-08-05T14:32:10",
"amount": 15000,
"service_name": "Monthly Plan"
}
Key Attributes
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier. |
status | string | See Status Values above. |
currency | string | CLP or UF. |
name | nullable string | Only populated when the installment belongs to a Payment Plan. |
external_id | nullable string | Your own reference for this installment, if one was set. |
due_date | string (date) | YYYY-MM-DD. |
created_at | string | YYYY-MM-DDTHH:mm:ss, America/Santiago. |
payment_date | nullable string | YYYY-MM-DDTHH:mm:ss, America/Santiago. null until paid. |
amount | integer | For CLP installments, the CLP amount. For UF installments, this is the UF value captured at creation — see note below. |
service_name | string | Only present once status is paid — the name of the subscription/single payment/payment plan it belongs to |
Related Resources
- List installments
- Get installment
- Mark installment as refunded
- Installments for a specific buyer are also reachable via Subscription Buyer Installments and the equivalent Payment Plan / Single Payment Buyer endpoints.