Unified Assets
Use canonical asset semantics and validation rules consistently across trading and payments workflows.
#Purpose
Defines canonical asset identity, network context, and amount normalization requirements.
#Integration prerequisites
- Internal asset catalog supports canonical IDs and display metadata.
- Amount handling uses fixed-precision arithmetic and explicit rounding rules.
- Validation layer rejects unsupported asset/network combinations.
#Request and response patterns
- Requests provide canonical asset codes and normalized amount fields.
- Responses include accepted asset identifiers and precision context.
- Validation failures return explicit field-level error pointers.
#Lifecycle and state model
- Resolve merchant-facing symbol to canonical asset identity.
- Validate amount precision and network support before request submission.
- Persist canonical identifiers for downstream reconciliation and reporting.
#Error and failure taxonomy
- Unknown asset identifier or unsupported network mapping.
- Amount precision exceeds allowed scale for target asset.
- Asset temporarily unavailable for selected operation type.
#Retry and idempotency guidance
Retry only after correcting validation issues or after asset availability recovers; preserve the same operation identity.
#Observability and debugging entry points
- Track validation rejection rates by asset and network.
- Monitor canonical mapping drift between internal and platform catalogs.
- Audit amount-normalization behavior in reconciliation jobs.