One code, one grant, once.
Campaign authoring, bulk code inventory, and a two-phase redemption that cannot strand a consumed code when the downstream grant fails.
Promocodes, precisely
Campaigns
Versioned and scoped by segment, jurisdiction, brand and channel, with budgets and schedules fixed before launch.
Code inventory
Bulk unique codes or shared codes with usage caps, per-player limits, expiry and administrative void.
Single use, cell-wide
A single-use code is consumed exactly once, including under concurrent redemption from two devices.
Reserve then confirm
If the downstream grant fails, the code is released rather than burned. Nobody has to hand-fix a customer’s ruined welcome offer.
Attribution
Affiliate, channel and campaign references captured at redemption and exported as events for the partner programme.
Abuse controls
Velocity limits and guessing resistance applied at the redemption boundary, where they actually help.
Contracts it exposes
- Commands
- RedeemCode · IssueCodes · VoidCode
- Reads
- GetCampaign · GetRedemption
- Events
- CodeRedeemed · RedemptionRejected · AttributionCaptured
What it never does
- Grant value itself
- Keep a ledger of any kind
- Become a second bonus engine
Every module on this platform is defined as much by what it is forbidden to do as by what it owns. That is what makes a boundary auditable instead of aspirational.
This service turns a marketing artifact into at most one authorised downstream command per allowed use. The guarantee is the product.
See it running
Every module here surfaces as screens an operator uses on a Monday. Ask for a walkthrough of the ones that decide your week.