ReactorCX · Enterprise Loyalty Platform

Move Fast.Change Safely.Operate with Certainty.

ReactorCX is the enterprise loyalty platform for organizations that need to change their loyalty business quickly without putting members, balances or the numbers at risk. Marketing gets speed. Technology gets control. Finance gets a number it can defend.

Production

Promotion

Spring Fuel Bounceback

v14

Stage → Production

DraftReviewApprovedLive

Recommended change · awaiting approval

Add a store-visit condition within 72 hours of a fuel fill.

  • Projected cost within budget cap
  • No rule conflicts found in simulation
ReviewDismiss

Version 14 published to Production · approved by Program Director

Stage reconciliation passed · rollback to version 13 armed

Illustrative product view. Sample program; no customer data.
Enterprise proof

Running in production today

Fourteen brands across five enterprise programs, on one engine.

800M+
member records on ReactorCX
How this is measured

Count of member records held in live production ReactorCX programs, de-duplicated within each program; not active members. As of 2026-Q3.

4.2B
loyalty transactions a year
How this is measured

Count of activities evaluated by the ReactorCX rules engine across all production tenants in the trailing 12 months. As of 2026-Q3.

700M+
member records migrated with SafeSwitch™
How this is measured

Sum of member records moved from a legacy platform onto ReactorCX in SafeSwitch cutovers; excludes greenfield programs. As of 2026-Q3.

Feb 2020
zero unplanned production downtime since
How this is measured

No unplanned production outage of the ReactorCX platform since it became the primary system of record (first SafeSwitch cutover, 7-Eleven, February 2020). As of 2026-Q3.

  • 7-Eleven, 7Rewards loyalty program on ReactorCX
  • Speedway, part of 7-Eleven on ReactorCX
  • Stripes, part of 7-Eleven on ReactorCX
  • Gap Inc., Encore loyalty program on ReactorCX
  • Old Navy, Gap Inc. brand on Encore
  • Athleta, Gap Inc. brand on Encore
  • Banana Republic, Gap Inc. brand on Encore
  • MGM Resorts, MGM Rewards on ReactorCX
  • Western Union, My WU loyalty program on ReactorCX
  • bp, Earnify loyalty program on ReactorCX
  • Amoco, bp brand on Earnify
  • ampm, bp brand on Earnify
  • Thorntons, bp brand on Earnify
  • TravelCenters of America, bp brand on Earnify

Three teams. One platform. No tradeoff.

Control is the reason marketing can move. Lineage is the reason finance can sign off.

Marketing · Move Fast

Turn loyalty ideas into production faster.

~ 1 week ~ 1 hour
promotion configuration with Conversational Configuration
How marketers ship changes
Technology · Change Safely

Control without bureaucracy.

DraftReviewApprovedLive

Versioned, approved, logged and reversible. AI changes pass the same gates.

How governance works
Finance · Operate with Certainty

Enterprise loyalty you can trust in production.

Feb 2020
zero unplanned production downtime since
How the ledger stays right
The ReactorCX platform

What ReactorCX does

Nine capability areas, one engine, one ledger.

Loyalty and promotions

Every program mechanic on one engine

Marketer experience

Offers, segments and tiers, changed directly

Personalization

The right offer for every member, on every channel

AI and MCP

AI prepares the change; people approve it

Analytics and intelligence

Dashboards, SQL access, Power BI and Tableau

Integration and events

REST APIs, event streams and batch feeds

Member care

A 360-degree member view for agents

Partner ecosystem

Partner funding and settlement in the ledger

Gamification

Streaks, challenges, missions, badges and referrals

See the full platform

ReactorCX AI · Model Context Protocol

What if your loyalty platform understood itself?

ReactorCX exposes its configuration, rules, APIs, events and implementation patterns to approved AI models through a Model Context Protocol (MCP) server. AI reads your program the way an engineer would: rule conditions, tier logic, version history, earn structures. Business intent becomes a correct, reviewable change in hours instead of weeks: configuration, integration, troubleshooting, documentation. The deterministic engine still executes only what a person approves, inside the same governance as every other change. Bring your own model; your data stays under your policies.

AI-powered velocity. Enterprise-grade control.

  • Nothing executes without sign-off. AI does not touch your live program without explicit human approval.
  • Every AI-prepared change carries the same version, approval record and rollback path as a manual change.
  • Gap Inc. runs a deployed MCP server that exposes Encore's configuration to approved AI models.
A business intent stated in plain language is read by ReactorCX intelligence, which reads live configuration through MCP and prepares a change covering rules, integration, cost projection and affected members; the prepared change passes a governance gate of stage, review, approval, audit and rollback before it reaches production, where it is executed exactly as approvedBusiness intent → ReactorCX intelligence → prepared change → governance gate → production. INTENT GOVERNED RELEASE reads live configuration Business intent “Reward first in-store visit after a fuel fill” Stated by the business intelligence Reads live configuration Through MCP Prepared change Rules · Integration Cost projection · Affected members Governance gate StageReviewApproval AuditRollback Production Executed exactly as approved
Approved changeExternalGovernance gate
Business intent → ReactorCX intelligence → prepared change → governance gate → production.
For finance and audit

Enterprise loyalty is financial infrastructure.

A points balance is a liability on your balance sheet. A partner-funded offer is a receivable. A cross-brand basket is three sets of books.

ReactorCX records every accrual with its source rule, currency, brand, partner, timestamp and expiry, burns in a configurable order, settles partners from the same lineage and exports every record at the transaction level for your ledger. Prior liability plus earned, minus redeemed, minus expired, equals outstanding, and every term traces to a member activity.

LiabilitySettlementAudit trail

Multi-currency wallets and sub-balances · qualifying and non-qualifying points · expiry and breakage lineage · FIFO and tagged burn order · partner wallets, vendor funding and escrow · date-relative co-marketing billing · liability reporting and reconciliation exports · full audit trail.

Know that the numbers are right.

SafeSwitch™ and ThreadSync™

Don't trust your migration. Prove it.

Replacing a loyalty platform is frightening because correctness is usually proven in production, after the point of no return. SafeSwitch™ proves it first.

ReactorCX runs in parallel with your legacy platform on mirrored production traffic. Every balance, tier and transaction is reconciled across the full member base, not a sample. Differences are found, explained and fixed by replay. Only when both systems agree does traffic move, and the legacy system stays live until you confirm the new one is right. When the switch finally flips, nothing happens. That is the point.

700M+
member records migrated
How this is measured

Sum of member records moved from a legacy platform onto ReactorCX in SafeSwitch cutovers; excludes greenfield programs. As of 2026-Q3.

6B+
transaction records reconciled
How this is measured

Historical transaction records loaded into ReactorCX and reconciled against legacy outputs during SafeSwitch migrations. As of 2026-Q3.

Every cutover to date
with zero member-visible downtime
How this is measured

Number of SafeSwitch production cutovers completed and the number completed with zero member-visible downtime. As of 2026-Q3.

Gap Inc. moved 100M+ member records and 700M+ historical transactions in 7 months, with zero member-visible downtime at cutover on 24 Feb 2026.

How SafeSwitch™ works, gate by gate

01
Production
traffic

Every qualifying transaction, cloned to both systems.

Legacy platform

Keeps serving members. Authoritative until the switch.

ReactorCX

Processes the same transactions in shadow. Nothing simulated.

Same inputOne live traffic stream, two platforms
02
Compare

Every balance, tier and point.

BalancesTiersPoints
ScopeThe whole member base, not a sample
03
Reconcile

Each difference explained, fixed, replayed.

04
Prove

Both systems agree, account by account.

Exit criterionA match, not a judgement call
05
Cutover

A routing change, not a rebuild.

Rollback stays armed.

LegacyReactorCXProvenChange
SafeSwitch™ runs both platforms on the same production traffic and moves members only after the results match.

See this run on your traffic.

See a parallel migration

Enterprise programs in production

Logos say who. These say what happened.

Zero-downtime migration

Four brands, one member, platform change and program redesign in one move.

"You guys [Loyalty Methods] understanding our problem at the outset, what we're trying to solve for, and then really putting the tools in the hands of our teams … to make sure that we're hitting that moment and we're getting it right."

Kevin MeinersHead of Loyalty and Payments, Gap Inc.
Read the story
High-scale loyalty

7Rewards runs across US and Canadian stores on one real-time engine.

"They are experts in their space and provide excellent solutions, creativity and out of the box thinking."

Steve KinchInnovation Leader, 7-Eleven
Read the story
Global operations

My WU runs on ReactorCX across 35+ countries with multi-currency support.

"LM's focus on innovation, agility, and successful, seamless delivery has made a massive difference in our efforts."

Lucy DonaldsonHead of Loyalty, Martech & Consumer Ecosystems, Western Union
Read the story
Multi-brand complexity

bp Earnify unifies five fuel brands and a partner network behind one member identity.

"Loyalty Methods has been a crucial partner, providing a flexible platform and bringing an experienced team that has partnered well with BP to deliver on our initiatives with excellence and dedication."

Tarang SethiaChief Product Officer & GM, Digital Products, Mobility & Convenience Americas, bp
Read the story

All customer stories

Architecture and extensibility

Built to fit an enterprise architecture

ReactorCX is headless by design. Your teams own the member experience; ReactorCX owns the decisioning and the ledger.

Every console in the platform is built on the same REST APIs your systems call, so anything you can do in the UI you can do through the API. Events publish at two levels, object replication and business events, to Kafka, Kinesis, Event Hubs or webhooks. Partner files enter through FeedXChange™, where each row runs through the same real-time rules engine as a live transaction.

ReactorCX architecture: five client-owned channels send activity through REST API, Event API and FeedXChange batch into the ReactorCX core, which publishes to an event stream that enterprise systems subscribe toChannels → REST APIs and FeedXChange™ → ReactorCX core with governance → events → enterprise systems. CLIENT-OWNED CHANNELS DOWNSTREAM REST API REST API Event API REST API FeedXChange events subscribe POS / forecourt In-store tills and fuel controllers REAL TIME Mobile / web App, site and member account REAL TIME PMS / gaming Property, casino and ticketing EVENT DRIVEN Kiosks / call centre Agent desktop and self-service REAL TIME Partner feeds Batch files from partner systems SPLIT TO TRANSACTIONS core API layer Selective retrieval · same APIs as the consoles Rules engine Activity → evaluation → arbitration → actions Member State · RCX Data Balances, tiers, segments, lineage, versions Execution log · Scheduler What ran and why · expiry, effective dates Governance Versioned JSON · publish / unpublish · audit trail Microservices · replicated NoSQL · Kafka Multi-AZ and multi-region · rolling upgrades Event stream Kafka, Kinesis, EventHub, webhooks Level 1 replication · Level 2 business Enterprise systems CRM / CDP · ESP and push · analytics Partner systems · data warehouse Finance and general ledger exports
Client-owned systemsGovernance and entry pointsEvents and data
Channels → REST APIs and FeedXChange™ → ReactorCX core with governance → events → enterprise systems.

Real-time first.

Every activity is evaluated as it happens; batch rows become individual real-time transactions.

Extension aware.

Custom fields and entities you add are available in the API the same day.

Environments in sync.

Lower environments kept in sync with production, so changes are validated before they go live.

Privacy modes.

PII inside the platform, or tokenized identifiers with PII held in your systems.

Walk through the architecture with the people who built it.

Book an architecture review
Independently verified

Security and trust you can verify

Enterprise security reviews do not ask whether a vendor holds a certification. They ask what the certification covers, who verified it, and what else stands behind it. The trust page answers all three.

SOC 2 Type II
annual independent audit

Scope and report period on the Trust Center

ISO/IEC 27001:2022
information security management

Certificate details on the Trust Center

Encryption and access control

TLS in transit, AES-256 at rest; OIDC single sign-on; role- and attribute-based access control.

Availability

Multi-AZ, multi-region availability; rolling upgrades; configuration publish without restart.

Privacy

Two privacy modes; GDPR, CCPA, PIPEDA and PIPL readiness.

We own the outcome.

Enterprise loyalty touches every system a company runs. When something goes wrong, most vendors have a sentence ready. We do not say those sentences. Your loyalty outcome is our problem. That is not a contractual guarantee. It is how we work, learned inside other people's loyalty programs where downtime was not an option.

What we don't say

  • "That belongs to your SI."
  • "That is an integration issue."
  • "That is your data."
  • "That was not in the requirements."
  • "Our software is operating correctly."

What we do

The engineers who build ReactorCX run its migrations and operate it in production. Vision Alignment names every system and feed before a platform is chosen. ThreadSync™ funds change management and training as a thread with its own "done when". SafeSwitch™ keeps the old system running until you say the new one is right.

What it means for you

One accountable team across platform, integration and migration. Execution logs that answer "what ran, why, and who approved it" instead of opening an investigation. A Migration Readiness Assessment that puts the plan in writing before you commit.

FAQ

Frequently asked questions

What is ReactorCX?

ReactorCX is the enterprise loyalty platform built by Loyalty Methods. It runs earn, burn, tiers, promotions, discount arbitration, partner settlement and audit on one real-time, API-first, event-native engine, with an AI advisory layer that prepares changes for human approval. It is the platform behind loyalty programs at 7-Eleven, Gap Inc., MGM Resorts, Western Union and bp.

Who is Loyalty Methods?

Loyalty Methods is an enterprise loyalty software company founded in 2007 and headquartered in Irving, Texas. It began as the team that implemented and integrated other companies' loyalty systems and built ReactorCX from that experience. The same in-house teams build, deliver and operate the platform in production.

How does ReactorCX migrate a loyalty program without downtime?

Through SafeSwitch™, a four-gate cutover method. ReactorCX runs in parallel with the legacy platform on mirrored production traffic (Shadow Run), every balance, tier and transaction is reconciled across the full member base (Reconcile), traffic is redirected only when both systems agree (Cutover), and the legacy system stays synchronized with rollback armed until live correctness is confirmed (Reversal Ready). Every cutover to date with zero member-visible downtime.

How does AI work inside ReactorCX?

ReactorCX pairs a deterministic loyalty engine with an AI advisory layer. AI connects through a Model Context Protocol (MCP) server, reads the live program configuration, and prepares changes, simulations, reports and diagnostics. People approve every change; the engine executes only what was approved, with a full audit trail. Clients can bring their own large language model and keep data under their own policies.

Why does Loyalty Methods describe enterprise loyalty as financial infrastructure?

Because loyalty value is a financial obligation. ReactorCX records every accrual with its source, currency, brand, partner and expiry, controls burn order, settles partners from the same lineage and exports transaction-level records for the general ledger. Every liability figure traces to an originating member activity, so finance can reconcile the program instead of estimating it.

Imagine how fast you could change your loyalty business if you weren't afraid of changing it.

The faster enterprises need to change, the more they need a loyalty platform they can trust to change safely.