Capital · coordination · constructionCareers

Case study — Flashy Finance

Redemption without a liquidity promise the catalogue could not keep

Building the redemption side of a rewards programme — catalogue, fulfilment, partner settlement — deliberately before building swap routing, because a redemption promise a reserve cannot honour is the failure that ends these programmes.
Scale
A live redemption and marketplace path within the group’s rewards programme.
Redemption path
Live in production
Swap routing
In build, sequenced deliberately

The challenge

The tempting version of this build ships an exchange-style swap feature on day one because it demos well. The expensive mistake is a redemption path that outruns what the reserve backing it can actually honour under load.

The approach

Catalogue and fulfilment first

What a balance converts into, with availability and limits, shipped and hardened before any conversion-rate feature.

Partner settlement on a stated tolerance

Reconciliation between the programme and the parties who honoured a redemption, with breaks raised inside an agreed tolerance rather than discovered at audit.

Swap routing scoped, not shipped early

Conversion between denominations is sequenced deliberately after the redemption path is proven, not bundled in to make the initial release look larger.

The outcome

The redemption and marketplace paths operate in production; swap routing is in build on the sequencing this case study argues for, which is also why the platform catalogue lists it as IN BUILD rather than LIVE.

The platforms this evidences

Considering something similar?

The capability above is licensable independent of this engagement — see the platform page for what is and is not white-labelled.

Request a technical evaluationAll case studies