Cause finances

GET /v1/vakis/{key}/finances

Intended contract

{
  "object": "vaki_finances",
  "currency": "COP",
  "total_collected": 12450000,
  "available": 9870000,
  "withdrawn": 2000000,
  "pending": 580000,
  "supporters": 214,
  "costs": {
    "platform_fee": 622500,
    "gateway": 214000,
    "taxes": 40660
  },
  "goal": { "amount": 50000000, "progress": 0.249 },
  "last_payment_at": "2026-08-17T13:44:02Z",
  "as_of": "2026-08-17T13:44:31Z"
}

Field	Meaning
`total_collected`	Everything donors have paid
`available`	What can currently be withdrawn
`withdrawn`	What has already left the platform
`pending`	Payments not yet settled
`costs.platform_fee`	Vaki’s 5%, in currency units
`costs.gateway`	The gateway’s own cost, shown for transparency — not charged on top of the 5%, see Fees
`as_of`	When this read model was last recomputed

The freshness contract, stated before you build on it

Accounting is recomputed by a background process, not on read. A donation that completed two seconds ago may not be in these numbers yet.

That is why the response carries as_of, and why it is not decoration:

Never treat these numbers as a real-time balance. A donor’s payment confirming and available moving are two different events at two different times.
If you reconcile, reconcile against payments, not against this endpoint. Poll the checkout link, or handle payment.approved once webhooks ship.
Show as_of if you display these numbers to a human. “Actualizado hace 30 segundos” is honest; a stale number presented as live becomes a support ticket that blames us.
Never compute a difference across two calls to decide that a payment arrived. Different reads can straddle a recompute.

We are publishing this constraint before the endpoint exists precisely because partners who discover eventual consistency in production build reconciliation on a 30-second-stale number and are right to be annoyed about it.