Featured enterprise case study

Bank Loyalty Marketplace and Processing Platform

A large-scale loyalty marketplace and independent points-processing platform developed for a major bank. During several years of operation, it supported more than 20 million users at peak scale, around 1.5 million active offers/products, multi-layer APIs, a large user portal, a large administrative ARM, worker-based operations, and a separate financial processing subsystem.

Scale and operation Architecture

Case summary

From weak legacy version to a full loyalty ecosystem

The platform was built from scratch as a new system replacing an outdated and limited previous version. It grew into a full banking loyalty ecosystem with travel services, supplier APIs, administrative operations, CLI/worker processing, and independent points workflows.

Problem

A new platform was needed

The previous system was not strong enough for the required loyalty, catalog, travel, supplier, administrative, and processing operations.

Our role

End-to-end product engineering

The work covered architecture, backend, first design version, user portal, ARM, APIs, processing, workers, reports, integrations, and production evolution.

System surface

Users, suppliers, admins, finance, API, workers

The platform served users, bank-side workflows, suppliers, catalog managers, support, finance/economics teams, API consumers, and worker processes.

Result

A working, profitable loyalty platform

The bank received a functional loyalty system; project owners got supplier onboarding through clear APIs and panels; finance teams got reports and registry exports.

Why it matters

Complex operations became manageable

Historical accruals and spend operations, supplier workflows, travel services, admin control, and points processing moved into one coordinated platform.

Enterprise scale

A multi-year banking loyalty ecosystem

The platform unified a major bank loyalty program into a working digital ecosystem. Users had a single place for offers, balances, catalog browsing, cashback, orders, travel services, documents, support, and points operations.

Administrators, support teams, catalog managers, suppliers, API consumers, workers, analysts, and financial-processing operators worked through role-specific interfaces and background workflows rather than fragmented manual processes.

  • Major-bank loyalty program context
  • More than 20 million users at peak
  • Around 1.5 million active offers/products at peak
  • Separate user-facing, administrative, API, worker, and processing blocks
  • 100+ server enterprise footprint with dev/test/stage/UAT-style environments

Platform architecture

Major system blocks

Portal

User loyalty platform

Public storefront, personal cabinet, authorization flows, loyalty balances, accrual details, product cards, catalog, cashback offers, wishlists, cart, checkout, support, FAQ, and documents.

API

Multi-layer API suite

Versioned supplier OfferApi, backend/mobile-style OpenAPI documentation, supplier REST workflows, minimal REST operations, technical APIs, API-user management, and API-call tracking.

ARM

Administrative system

Large ARM panel for users, vendors, catalogs, sections, moderation, orders, reports, banners, news, notifications, FAQ, roles, permissions, logs, support, cache, and worker administration.

Processing

Independent points processing

Separate loyalty-points and financial-processing subsystem for accrual, spending, cash/bonus operations, invoices, corrections, imports, exports, reports, and reconciliation-style tasks.

Workers

CLI and background operations

Dedicated CLI/worker mode for imports, exports, reports, retries, balance checks, catalog tasks, order confirmations, technical corrections, and heavy workloads outside user requests.

Integrations

Supplier and partner services

Generic integrations for bank-side loyalty systems, suppliers, travel services, product providers, payment/card operation layers, fiscal services, messaging, support systems, and analytics exports.

API and supplier integration

Versioned contracts for a large marketplace

The project included multiple API contexts for different actors: supplier offer APIs, backend/mobile-style APIs, application APIs, REST supplier workflows, minimal REST operations, and technical APIs for logs, metrics, customer state, and operational checks.

OfferApi evolved through multiple documented versions, reflecting a long-lived supplier integration contract for publishing offers, exchanging catalog data, handling orders, delivery, documents, invoices, and status changes.

  • API-first supplier integration
  • Versioned OfferApi documentation
  • Catalog upload/download and upload-status workflows
  • Order creation, update, confirmation, cancellation, documents, and invoices
  • Operational logs and API-call tracking

Administrative operations

Support, catalog, order, report, and exception control

The ARM/admin block was a major product in its own right. It covered administrator access, user management, API users, vendors and subvendors, catalog moderation, product and section management, order view/edit/check/confirm/cancel/refund workflows, document upload, reports, role permissions, system settings, logs, and support tools.

For banking loyalty operations, this administrative breadth mattered: support teams often resolved user and order issues through controlled views, reports, logs, manual corrections, and exception workflows.

  • Role-based administrative access
  • Catalog moderation and vendor catalog versioning
  • Order checks, confirmation, cancellation, refund-related workflows, and recovery actions
  • Goods, user, order, feedback, payment-status, and points reports
  • Technical logs, worker administration, and support/chat tools

Financial processing

Independent loyalty-points subsystem

An independent financial and loyalty-points processing block handled accrual, spending, burned points, balance checks, manual accruals, cash operations, invoices, order payment stages, import/export of histories, correction tasks, payment logs, and financial/points reports.

This is described as a loyalty-points and financial-processing subsystem, not as a banking core, certified processor, or regulatory settlement system.

  • Points accrual and spending workflows
  • Manual accruals, corrections, retries, and reports
  • Cash/bonus operations and invoice flows
  • Payment-stage and order-state handling
  • Three author-owned patents connected with proprietary technical work

Background operations

Workers, CLI, cron, and operational visibility

At this scale, heavy operational tasks could not compete with user traffic in request paths. The platform used CLI/worker execution, scheduled tasks, Supervisord-style process management, RabbitMQ-oriented infrastructure, worker logs, task status, and long-running report/import/export workflows.

Worker families covered travel checks, cache and catalog jobs, accrual imports, history reimports, order reconfirm/resend/check/cancel tasks, balance checks, product exports, points reports, goods reports, feedback reports, corrections, restarts, and failed-worker closure.

  • Dedicated CLI/worker mode
  • Imports, exports, report generation, retries, and correction tasks
  • Separation of user traffic from heavy background workloads
  • Task status, logs, priorities, and operational control
  • Multi-environment configuration for dev, test, stage, UAT, and production-style contexts

Data and access

Built for sensitive banking-loyalty operations

The platform handled sensitive banking-loyalty data, user identifiers, authorization state, contact data, balances, bonus/points operations, orders, supplier records, partner integration payloads, documents, reports, logs, certificates, and operational access materials.

Role-specific interfaces separated users, suppliers, support, catalog managers, finance/economics teams, administrators, API consumers, processing operators, and worker processes.

  • Bank-side authorization and loyalty balance workflows
  • Supplier APIs and role-based supplier access to order management
  • Administrative ARM for support, catalog, order, report, and exception work
  • Finance/economics reports and registry exports

Impact

A substantially larger enterprise project

This was not a bounded product module. It was a multi-year banking loyalty ecosystem with enterprise scale, several application contexts, multiple API layers, major user and administrative surfaces, independent financial processing, large background workloads, and proprietary technical work connected with three patents.

The platform replaced fragmented loyalty, catalog, supplier, order, and points operations with a unified system: users received one loyalty marketplace and account experience, suppliers interacted through controlled APIs, administrators managed exceptions through ARM, and heavy processing ran through dedicated worker workflows.

Back to projects Security and confidentiality Featured homepage block Contact us
  • Long-running enterprise platform development
  • High-load user and catalog scale
  • Multi-layer API and supplier integration architecture
  • Independent loyalty-points and financial processing
  • Patented proprietary technology, with exact legal details withheld pending review