Workflow 2
GIFT One
A resident opens a foreign-currency account, funds it from a partner-bank event, exchanges at a disclosed quote and spends on a virtual card. Operations can replay the evidence and explain every decision.
Questions a bank buyer asks, and the answer in the demo
Can an event double-charge?
External IDs are idempotent; a duplicate returns the original result.
Where is customer money?
Mirrored against a safeguarded partner balance and reconciled by currency.
Can ops explain a decision?
Every pass, hold and decline has a reason and linked evidence. A hold is not a decline.
What needs a partner?
KYC, bank and FCA, FX and safeguarding, and card adapters. The demo does not pretend these are live.
Real: code and checks
- Consent gating is enforced in the demo interface on every journey: Continue and the step rail stay locked until consent is ticked. Digests of source artifacts in the release custody register are recomputed from synthetic content.
- An exportable release attestation that a buyer can verify independently with a command-line verifier.
- 160 automated tests pass on the current code. A QA review on October 3, 2026 found issues we fixed (a consent-rail bypass, a source-digest recompute gap, per-journey consent); residual items are listed on the trust page.
Synthetic
- Every identity, balance, card, transaction and approval is generated.
- Partner adapters are stand-ins.
Live demonstration access is by request.