2026-01-07

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude

Summary

This release improves Penny Validation by allowing integrators to send a custom description and external_reference for better traceability. When omitted, the backend applies deterministic defaults. Both fields are propagated to the transaction read endpoint and the CEP webhook payload.

Added

Penny Validation request fields — Added [Behavior]

Impact: POST /v1/transactions/penny_validation now accepts:

• description (optional): string, max 40 chars; letters, numbers and spaces only; special characters not allowed except ñ/Ñ.
• external_reference (optional): numeric string, max 7 digits.

Action required: None. Optional fields only.
References: /products/fincore/guides/penny_validation

Changed

Penny Validation defaults (backend) — Changed [Behavior]

Impact: If optional fields are not provided, the backend sets:

• description → "Validacion de cuenta"
• external_reference → operation date formatted as ddmmaa (e.g. 24/11/2025 → "241125")

Action required: If you relied on empty/missing values, update your expectations to these defaults.
References: /products/fincore/guides/penny_validation

Propagation to reads and webhook — Changed [Behavior] [Operational]

Impact: description and external_reference are now reflected in:

• GET /v1/clients/{clientId}/transactions/{transactionId}
• CEP webhook payload (e.g., payment_concept, external_reference)

Action required: If you parse/monitor webhook payloads, you can now store these fields for reconciliation and traceability.
References: /products/fincore/guides/penny_validation