Unified Offers Hub: Standardizing at Super-App Scale
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.
- Published in
- Proceedings of the Raptors Conference, Vol. 1 (2026)
- Conference
- Raptors Conference 2026, 21 October 2026, online
- Accepted
- 2026-09-20
- DOI
- https://doi.org/10.68495/rc.2026.C089
- Presentation
- Slides (PDF)
- Licence
- © 2026Tsira Gvritishvili. Published under Creative Commons Attribution 4.0 International (CC BY 4.0).
- Publisher
- Hackathon Raptors, Community Interest Company 15557917, London, United Kingdom
- Permanent address
- https://proceedings.raptors.dev/gvritishvili-fintech-solutions-architecture-architecting
Open access. Every entry in the Proceedings is free to read, with no charge to authors and no charge to readers. Slides are served from this site, so they stay available at the paper's permanent address.
Cite this paper
Tsira Gvritishvili (2026). Unified Offers Hub: Standardizing at Super-App Scale. Proceedings of the Raptors Conference, Vol. 1 (2026). Hackathon Raptors, London. https://doi.org/10.68495/rc.2026.C089
@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.}
}
TY - CONF TI - Unified Offers Hub: Standardizing at Super-App Scale AU - Gvritishvili, Tsira T2 - Proceedings of the Raptors Conference VL - 1 PY - 2026 DA - 2026/09/20 PB - Hackathon Raptors CY - London, United Kingdom DO - 10.68495/rc.2026.C089 UR - https://doi.org/10.68495/rc.2026.C089 AB - 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. LA - en ER -