Yuva DocsBack to Yuva
MVP / design

Data Types

Use explicit units, identities and state meanings.

On this page

Current values#

TypeCurrent representation
MoneyFinite number, rounded and validated to two TRY decimals.
UserId / referenceOpaque string used within the local fixture.
TimestampMilliseconds since Unix epoch.
Due dateTurkey calendar day, represented by its end-of-day timestamp.
ApprovalLocal reference bound to actor, scope, expiry and instruction.
ReceiptFinalized TRY movement with parties, amount and provider reference.

Production representation#

A server contract should use integer minor units or exact decimal strings, explicit currency and defined timezone semantics. Do not assume floating-point JSON numbers are a production money format.

Missing values#

A missing Trust score is null. An unavailable provider is a data-status condition, not a verified zero balance. An empty history is not proof that no external obligations exist.

Search Yuva Docs

Type to search the documentation.

↑ ↓ to navigate Enter to open · Esc to close