Xoxoday Plum’s gift card marketplace supports cross-vertical points accumulation by delivering detailed transaction data via APIs to a central loyalty engine, covering telecom, fintech, and travel purchases in a single unified flow.
Cross-Vertical Points Accumulation with Xoxoday Plum
Modern loyalty programs rarely operate within a single vertical. Customers earn points when paying a telecom bill, booking a flight, or completing a fintech transaction — and they expect those points to roll up into one unified balance. Xoxoday Plum makes this possible through an API-first architecture built for exactly this kind of multi-vertical integration.How Transaction Data Powers the Loyalty Engine
When a purchase or redemption event occurs in the Xoxoday Plum gift card marketplace, the platform exposes detailed transaction data through its APIs. This data — including vertical type, transaction amount, reward value, and timestamp — is consumed by your organisation’s central loyalty engine. The engine then applies its own rules to calculate, accumulate, and manage points regardless of which vertical generated the transaction. This approach separates concerns cleanly: Xoxoday Plum handles the marketplace and data delivery, while your loyalty engine handles the points logic. The result is a flexible, scalable system that avoids hard-coding any single vertical’s rules into the integration layer.A Practical Example
Consider an organisation running a rewards program across three lines of business: a telecom subsidiary, a fintech lending product, and a travel booking portal. Each vertical processes transactions independently, but all three connect to Xoxoday Plum via API. When a customer pays a telecom bill, books a hotel, or completes a loan repayment, the corresponding transaction data is pushed to the central loyalty engine through Xoxoday Plum’s APIs. The engine aggregates points in real time and makes the unified balance available for redemption — without manual reconciliation across teams. This model works equally well for organisations using Darwinbox or SAP SuccessFactors to manage employee reward programs spanning multiple business units, where each unit represents a distinct vertical with its own transaction stream.Why API-First Design Matters
Xoxoday Plum’s API-first design means your engineering team is not constrained by proprietary connectors or rigid data formats. The APIs are documented, versioned, and built to handle diverse business models — whether your verticals share a single customer identifier or operate under separate identity systems. Custom field mapping, webhook support, and configurable payloads give your organisation full control over how transaction data flows into the loyalty engine. This architecture also future-proofs your loyalty program. Adding a new vertical — such as an insurance product or an e-commerce marketplace — requires only a new API integration, not a rebuild of the underlying reward logic. Learn more: Xoxoday Plum Help Centre — IntegrationHow does Xoxoday Plum API authentication work?
Learn how to authenticate API requests to Xoxoday Plum, including OAuth 2.0 flows and API key management for enterprise integrations.
Can Xoxoday Plum connect with third-party loyalty engines?
Understand how Xoxoday Plum syncs transaction data and reward balances with external loyalty platforms via API.