Cash · Reference
Operation statuses
Every Cash operation status, the webhook it triggers, and the error codes.
Statuses
| Status | Meaning | Webhook event |
|---|---|---|
unpaid |
Initial status when a reference is created. The operation is ready to be paid. | None |
paid |
The end customer completed the cash deposit or withdrawal and all required validations succeeded. | webhook.paid.success |
expired |
The reference’s expiration window passed. Cash-in expires after 3 days. Cash-out expires after 60 minutes. Open references expire on the custom date you set during creation. | webhook.expired.success |
reversed |
An issue occurred during processing at the physical location and the transaction was voided. | webhook.reversed.success |
The API schema also lists close as a status. New operations return close in the API examples.
Cash-in and cash-out follow the same flow: unpaid → paid, or unpaid → expired.
Note:
Webhooks are sent only for closed-reference operations. Open references do not send status webhooks.
Check the status
Call Consult Operation with the 20-digit reference.
curl -X GET "https://dev-api.finco.lat/api/v1/cash/consult?reference=10511175512161627448" \
-H "X-Client-Id: 4a8a08f09d37b73795649038408b5f33" \
-H "X-Signature: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855" \
-H "X-Timestamp: 1705312200"{
"response_code": "0",
"response_text": "Operacion encontrada",
"result": {
"operation_id": 123,
"kind": "cash_in",
"reference": "10511175512161627448",
"status": "paid",
"amount": 500,
"created_at": "2025-01-15T10:30:00Z",
"expire_at": "2025-01-18T10:30:00Z"
}
}If the reference does not exist, you get 404:
404 Not Found
{
"response_code": "64",
"response_text": "Operacion no encontrada",
"result": {
"reference": "10511175512161627448"
}
}Error codes
Operation errors return a response_code and a response_text.
| Error code | Description | Resolution |
|---|---|---|
60 |
Invalid parameters | Check request parameters and validation rules |
61 |
Invalid document identifier | Verify document type and ID format |
13 |
Invalid reference length | Reference must be exactly 20 digits |
14 |
Invalid reference | Reference not found in system |
64 |
Operation not found | Verify reference number exists |
The API spec also returns 1 (Operacion rechazada, operation rejected) on 400.
HTTP status codes
| Status | Description | Client action |
|---|---|---|
401 |
Unauthorized | Invalid X-Client-Id or signature verification failed |
400 |
Bad request | The request parameters are invalid. This may be due to malformed values, incorrect formatting, or missing required parameters. |
404 |
Not found | The requested resource doesn’t exist. |
503 |
Service Unavailable | The service is under maintenance. |
422 |
Unprocessable Content | The request is syntactically valid, but it cannot be processed because one or more business rules or semantic validations failed. |
500 |
Internal Server Error | The server encountered an unexpected condition that prevented it from fulfilling the request. |