4.3 KiB
Finance — original Anime.js scenes
Two editable, conceptual educational models; neither is an operational simulation. Geometry is original SVG with no external assets.
Overall gallery · Industry gallery
Source module · Catalog JSON · Shared lifecycle and seeking
| ID | Question / individual preview |
|---|---|
finance-payment-reconciliation |
Payment: authorization is not settlement |
finance-insurance-evidence |
Insurance: evidence before settlement |
Payment: authorization is not settlement
Audience / use: Explain to product and finance teams why an approved payment can still be unsettled or unreconciled.
Narrative: Authorize → Capture → Clear → Settle → Reconcile → complete readable state.
Model assumptions: Original conceptual flow; card, merchant and issuer roles are simplified. All timings and entry labels are illustrative; no monetary rates or compliance claims.
Recipe-specific control: reference is the short payment identifier shared by the batch, merchant and bank ledgers (default A, truncated to four characters).
Avoid: Do not use to specify payment-network messages, double-entry postings, dispute rights or accounting policy.
Anime.js techniques: one paused finite v4 timeline, explicit attribute from/to tweens, normalized SVG path drawing (pathLength=1 and dash offset), progressive evidence opacity, and phase indicators. Physical movement uses coordinates or a dedicated group. No callbacks, listeners, random data or autoplay.
Editable configuration: duration is the total illustrative timeline length in milliseconds, default 6000; the renderer clamps it to at least 3000. Every animation scales with this duration. Catalog beats are nominal defaults at 0, 1000, 2000, 3000, 4000 and 6000 ms; regenerate/retest seek targets after duration changes. Geometry and labels are intentionally authored in source, not exposed as unused config knobs.
Readable final state: all static explanatory labels remain present. Faint abandoned paths, baseline outlines or closed-valve handles preserve the earlier context; they are not hidden text. A timeline owner must settle for reduced motion and revert on unmount as described in the shared lifecycle guide.
Insurance: evidence before settlement
Audience / use: Use for claims operations audiences discussing evidence completeness, traceability and review handoffs.
Narrative: Intake → Assemble → Review gap → Resolve → Settle → complete readable state.
Model assumptions: All time values are illustrative. The claim and damaged property are fictional; settlement presumes a separate valid coverage and terms decision.
Recipe-specific control: missingItem names the evidence requested for review (default Signature; keep under 12 characters).
Avoid: Not a coverage determination, fraud score, legal timetable, automated approval policy or claim valuation model.
Anime.js techniques: one paused finite v4 timeline, explicit attribute from/to tweens, normalized SVG path drawing (pathLength=1 and dash offset), progressive evidence opacity, and phase indicators. Physical movement uses coordinates or a dedicated group. No callbacks, listeners, random data or autoplay.
Editable configuration: duration is the total illustrative timeline length in milliseconds, default 6000; the renderer clamps it to at least 3000. Every animation scales with this duration. Catalog beats are nominal defaults at 0, 1000, 2000, 3000, 4000 and 6000 ms; regenerate/retest seek targets after duration changes. Geometry and labels are intentionally authored in source, not exposed as unused config knobs.
Readable final state: all static explanatory labels remain present. Faint abandoned paths, baseline outlines or closed-valve handles preserve the earlier context; they are not hidden text. A timeline owner must settle for reduced motion and revert on unmount as described in the shared lifecycle guide.