ReceivableCanonicalIdentity
Origin of the accepted snapshot; omitted for legacy observations without a recorded origin.
Valores possíveis: [ONLINE, BATCH]
Registrar of the accepted snapshot.
Valores possíveis: [TAG, NUCLEA]
Reference time of the accepted snapshot, never the retry processing time.
Exact non-negative reais with two decimals.
Valores possíveis: O valor deve corresponder à expressão regular ^[0-9]+\.[0-9]{2}$
Canonical tuple hash. Legacy uniqueKey and receivableId remain valid during migration.
Valores possíveis: O valor deve corresponder à expressão regular ^[a-f0-9]{64}$
SETTLING starts on the scheduled settlement date in America/Sao_Paulo and remains after that date until confirmed settlement. SETTLED requires affirmative settlement evidence. Risk history remains separate. ENG-1355: UNAVAILABLE is an AVAILABLE or HIGH_RISK unit with freeAmount 0.00: nothing is left to the merchant. unavailableReason tells why: ACQUIRER_PREPAID when acquirerPrepaidAmount is above 0.00 (the acquirer prepaid what was free; it prevails when other institutions committed part of the unit too) or, since ENG-1612, OTHER_INSTITUTIONS when there is no prepaid and encumberedByOthers is above 0.00 (other institutions committed what was free; the client's financiers may hold the rest). A unit only the client's financiers committed keeps its situation, and so does one whose split is unknown. Settlement stays ahead of it (such a unit on its own settlement date reads SETTLING or SETTLED), so it means a unit with a future date. It is answered only by the session routes of the Agenda (collateral-management, summary and units) and its workbook; the external API v2 (/api/v2/receivables/schedule) never returns it and keeps the registry's freeAmount.
Valores possíveis: [AVAILABLE, HIGH_RISK, UNAVAILABLE, SETTLING, SETTLED]
{
"source": "ONLINE",
"provider": "TAG",
"asOf": "2024-07-29T15:51:28.071Z",
"registeredAmount": "string",
"receivableKey": "string",
"situation": "AVAILABLE"
}