Product How it works Decide Getting started

Data Model & designs

The logical data model first, then each database design with its tables.

Find in the outline

No row matches.

Top level 4 Processor confirmation Order reference Payment Refund Payment state · illustrative PostgreSQL design 4 orders payments confirmations refunds

Show in Data

Refund

Refund

Entity

Refund

Owned by Payment service

Overview Connections 2 Data 2 Use cases 1 AI context

Use cases

Refund the unavailable lamp 1 steps
Support requests a separate refund; the service records its request and compatible processor confirmation.

Notes

Explore Alexandria 4 of 6

Illustrative payment system · authored sample knowledge

Could Try again charge twice?

This alternative changes the timeout branch. Compare it with its base, then open the recorded decision explaining why the current design retains the payment.

Keep the reason beside the change it informs.

Follow €100 A missing answer Follow the evidence Understand the change A request is not a result Share the understanding

Back Next

Explore freely Open my projects

Retry change · authored alternative · draft v1 Illustrative payment system · authored sample knowledge Loading… Version v1.22.0

Search Esc

Map View Document View Mira · customer Actor Merchant support Actor Checkout Process Confirmation handler Component Payment records Data store Payment service Process Fictional processor External system Copper Lane Payments Boundary Pay for the €100 lamp use case Refund the unavailable lamp use case Processor confirmation Entity Order reference Entity Payment Entity Refund Entity Payment state · illustrative PostgreSQL design Database design Open my projects Page

Nothing matches.