Empower your Staff to Help Members with Ease and Efficiency

Yes. ReactorCX is intentionally a headless decisioning and execution platform. ReactorCX evaluates eligibility and program logic, issues outcomes (balances, benefits, rewards, badges), publishes events, and exports data - while client-owned digital and marketing systems render the member experience and deliver communications.

ReactorCX is not a CMS, not a CDP, not a marketing execution tool, and not a monolithic all-in-one front-end experience layer. This separation lets enterprise teams keep their existing channel investments while modernizing the underlying loyalty engine.

ReactorCX is an API-first product, which means every user interface and experience in the platform is built on the same REST APIs that are exposed to client systems. This ensures parity between what Loyalty Methods builds against and what client teams build against.

Anything achievable in a ReactorCX UI is achievable through the API. The APIs support three key capabilities: selective retrieval, embedded lookups, and extension awareness.

The ReactorCX REST APIs let client systems select just the elements they need from each API call rather than retrieving the full payload - reducing response size, network overhead, and processing cost for integrations that only need a subset of available data.

Selective retrieval also protects existing integrations from data model changes: integrations that request only the fields they consume are not affected when other fields are added or restructured.

The ReactorCX REST APIs allow client systems to dynamically resolve references and sub-objects within a single API call, and perform server-side lookups inside the same call rather than chaining multiple round-trip requests.

This reduces network overhead and simplifies client-side code for integrations that need related data alongside the primary object - fewer calls, less latency, simpler integration logic.

When client teams extend the RCX core data models with custom fields and entities, those extensions become instantly available within the API. There is no separate code release or API rebuild required to expose extended data - the API surfaces the extended schema automatically.

This is what lets program teams configure new attributes and use them in integrated systems without waiting on platform engineering cycles - configure it today, query it through the API today.

ReactorCX relies on event-based processing for many of the interactive features it offers. Event streaming allows loyalty data and program activity to flow in real time to downstream systems for personalization, segmentation, customer service, marketing, and analytics - without depending on batch reconciliation cycles.

Event streaming is one of three integration modes alongside API and batch. The right mode depends on the downstream system and its operational requirements - some need synchronous responses, others need event feeds, others need periodic batch files.

ReactorCX integrates with well-established streaming technologies. The platform supports cloud streaming offerings from Azure, AWS, and GCP, as well as on-prem deployments of distributed brokers such as Apache Kafka, Pulsar, and others.

This lets enterprise teams use the streaming infrastructure they already operate rather than adopting a loyalty-specific event bus - ReactorCX events flow through the same observability, security, and routing layers the rest of the enterprise's event traffic already uses.

Yes. Batch feeds still run a lot of the world's integrations, and ReactorCX has taken the batch world seriously through its FeedXChange module. FeedXChange simplifies the configuration, connectivity, security, execution, and monitoring of hundreds or thousands of individual feeds.

Underneath, batch processing is executed as real-time transactions: each row in a partner feed is ripped into an individual transaction and runs through the same real-time rules engine that handles API and event-based transactions - so batch behavior is consistent with synchronous behavior.

ReactorCX handles coalition partner integration primarily through FeedXChange, which is particularly critical for loyalty partners such as co-branded credit cards, airlines, hotels, and other coalition partners.

These partners typically operate on established batch data exchange formats and schedules, and FeedXChange provides the configuration, connectivity, security, execution, and monitoring layer that makes managing hundreds or thousands of such feeds operationally feasible.

ReactorCX is in production with named enterprise booking and property management systems including:

• Opera PMS at MGM Resorts (real-time integration)
• HMS Infor at Fontainebleau (real-time integration)
• Intopia for booking and reservations

The Loyalty Methods integration team works with the client's existing system administrators rather than requiring booking vendor engagement, drawing on more than 10 years of enterprise loyalty integration and implementation experience that pre-dates the ReactorCX platform itself.

Yes. ReactorCX REST APIs accept latitude and longitude parameters from the client application and perform radial geo search to filter offers and rewards by proximity to the member's current location. Configurable radius lets program teams control how broadly or tightly to filter.

The integration pattern works through standard REST calls with no SDK required. At 7-Eleven, this is used to surface only the offers available at stores near the member's current location.

Harmonized integration is the Loyalty Methods approach to enterprise loyalty integration: rather than handing over an API and expecting client teams to wire everything up alone, the implementation team focuses on understanding the full picture of the enterprise's architecture and ensuring every system participating in the loyalty flow connects seamlessly.

This includes recommending optimizations to adjacent systems and, where appropriate, helping implement changes across the stack - drawing on more than 10 years of enterprise loyalty implementation and integration experience that pre-dates the ReactorCX platform itself.

ReactorCX integrates across the customer-facing and back-end systems that surround an enterprise loyalty program, with three integration modes (API, events, batch) supporting reads, writes, and synchronization with:

• Mobile apps and web properties
• In-store kiosks and point of sale
• Hotel property management systems
• Gaming systems
• Customer service tools
• Marketing automation platforms

The appropriate mode depends on the system being integrated and its operational requirements: real-time channels use API and events, while partner integrations typically use batch.

ReactorCX supports two privacy modes that integration partners connect against: storing PII inside the platform with full data subject rights support (access, deletion, rectification, restriction of processing, portability), or operating with tokenized identifiers where PII is stored externally in a client-controlled system.

Integrations carry data consistent with whichever model the program operates. MGM Resorts operates ReactorCX with membership numbers only - no PII stored in the loyalty platform.

The ReactorCX platform is SOC 2 Type II certified, with encryption in transit (TLS), encryption at rest (AES-256), and key management through cloud-native key management systems. Role-based and attribute-based access controls and SSO integration via standard federation protocols are in place.

Audit logs across access, system activity, configuration changes, and member and transaction activity are maintained across all three integration modes - API, events, and batch - so the security posture applies uniformly regardless of how a system connects.

The ReactorCX platform is integrated across 30,000+ locations with a platform-wide <200ms API response SLA. In retail and convenience, integrated programs process approximately 2.6 billion transactions per year and 25 million+ API requests per day across the largest single enterprise deployment.

Active Loyalty Methods clients include 7-Eleven, MGM Resorts, BP, Speedway, TravelCenters of America, Western Union, Fontainebleau, and Gap Inc.