Swaps & redemption gateway
Evidence for that status: The redemption and marketplace paths run in production today; on-chain swap routing does not yet. See the case study. Read the case study →
What it does
Redemption catalogue
What a balance converts into, with availability, limits and the fulfilment record behind each.
Partner settlement
Reconciliation between the programme and the parties who honoured a redemption, on a stated tolerance.
Swap routing
Conversion between denominations. Under construction; not represented as running.
White-labelled, and not
Yours
- Brand, catalogue and the redemption experience
- Partner and fulfilment configuration
- Limits and eligibility rules
Not white-labelled
- Money transmission or exchange permissions in your jurisdiction
- Your partner commercial agreements
- Liquidity — we route, we do not provide it
Integration surface
REST for catalogue, redemption and fulfilment state; webhooks on redemption lifecycle; a settlement export your finance system can consume without transformation.
Who operates what
The licensee owns the catalogue, the partner agreements and the regulatory position. We own the software. Where a redemption path would require a permission the licensee does not hold, we say so during evaluation rather than at launch.
- Redemption
- Running in production
- Swap routing
- In build
- Licensing
- Annual + volume
- Support
- Tiered; SLA in contract
Publication gate: capability claims on this page are verified against the running software before publication. Lineage: Built in-house.
Reference deployment
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.
Request a technical evaluation
Engineers on both sides, against your requirements. If the software does not do what you need, this is where you find out.