@inproceedings{raptors2026-c089,
  title     = {{Unified Offers Hub: Standardizing at Super-App Scale}},
  author    = {Gvritishvili, Tsira},
  booktitle = {Proceedings of the Raptors Conference},
  volume    = {1},
  year      = {2026},
  publisher = {Hackathon Raptors},
  address   = {London, United Kingdom},
  doi       = {10.68495/rc.2026.C089},
  url       = {https://doi.org/10.68495/rc.2026.C089},
  abstract  = {This paper describes how a fintech super-app replaced three separate promotion backends with one version-controlled contract serving its mobile app, web and internet banking channels across 1.8 million monthly active users. Before the change, every cashback offer was built three times, one campaign needed three frontend deployments and two to three weeks, and customers saw different terms on different channels. The paper covers the four months spent agreeing a master specification with all three platform leads before any service code was written, a parametric badge schema that lets commercial teams launch offers through database configuration with no app release, and version guardrails that let older clients fall back without errors. Time to market fell from 21 days to under an hour, and the December 2024 holiday campaigns reached 900,000 active users with no frontend deployment. Readers take away how to standardise payloads rather than stacks, and how a well-designed contract extends to adjacent uses such as a referral engine without new backend services.}
}