Financial Services Loyalty Platform

ReactorCX: The Enterprise Financial Services Loyalty Platform, Built for Cross-Border Value and Booked Liability

Loyalty Methods runs ReactorCX, the enterprise loyalty platform behind Western Union's My WU program across more than thirty countries and territories. ReactorCX is built for what defines loyalty in financial services: value that is a liability from the moment it is issued, partners and issuers who fund it, customers who transact online, in-app and at agent or branch locations, and regulators who expect every earn, burn and adjustment to be explainable.

ReactorCXStaging

Rule

Card spend accrual with category multipliers

v5
Consumer cardPremium cardBusiness cardDeposits
DraftReviewApprovedLive

Funding

100%

Issuer funded via interchange

Attribution

100%

Merchant offers billed separately

Earning

Base rate by productMultipliers: dining, travel · Statement credit as a redemption

Limits

Cap per statement cycleCash advances and fees excluded · Chargebacks reverse the accrual

Approved by Cards Marketing · compliance and disclosures reviewed

Illustrative view of ReactorCX configured for a financial services program; sample program, no customer data.
220M+
Western Union member records migrated
How this is measured

Member records migrated onto ReactorCX for Western Union's My WU program; the largest Loyalty Methods migration to date.

35+
Countries running My WU on ReactorCX
How this is measured

Countries in which My WU runs on ReactorCX with multi-currency support.

<200 ms
Platform API response SLA
How this is measured

Platform-wide API response-time service level. As of 2026-Q3.

Every cutover to date
SafeSwitch cutovers 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.

Definitions and as-of dates are on each figure.

  • Western Union

How does ReactorCX run financial services loyalty on one engine?

Rewarding a money transfer, a card swipe or a deposit is the easy part. Doing it in real time, in the customer's currency, with the funding source recorded and the liability booked correctly, is the job.

Reward at the moment of transaction

Real-time, multi-channel engagement

Rewards issued for purchase and non-purchase behaviors across digital and in-person touchpoints: online, in-app, at agent or branch locations and through customer service, without latency or drop-off. Customers earn on eligible transactions and redeem for discounts or third-party rewards.

Global by design

Many countries, many currencies, one program

Multiple loyalty currencies, including points and promo codes; localized rules, currency, language and eligibility by market; processing around the clock; and streamlined compliance with regional data protection requirements through two privacy modes.

Card and partner economics

Co-brand and partner earn on one ledger

Co-brand card earn on a single instance with accrual on every linked-card purchase; issuer settlement and attribution from source-tagged activity; vendor-funded offers managed and reconciled in the platform; partner wallets and escrow for value that vests on conditions. Partner Ecosystems

Explainable to a regulator

Deterministic execution, full lineage

Every earn, burn, tier change, expiry and adjustment is logged with the rule and data that produced it. Liability reports by currency, market, partner and expiry bucket, with transaction-level export to the general ledger. Financial Integrity

How a remittance earns

From transfer to booked liability, in one pass

01

Transfer event

App, web, agent location or branch system sends the activity.

02

Member resolved

One profile across account, card, phone and app identifiers, per market.

03

Rules evaluated

Earn, promotion, streak and tier rules in the member's currency and market.

04

Accrual recorded

Source rule, currency, market, partner, timestamp and expiry attached.

05

Ledger and events

Liability booked; event published to warehouse, ESP and finance.

Your channelsReactorCXFinancial lineageAuditable
Each accrual is a ledger entry with its funding source, not a number in a marketing database.

Review liability, settlement and audit with your own program rules and markets.

Book a financial controls review
Production proof

Western Union My WU on ReactorCX

Western Union partnered with Loyalty Methods to launch My WU, a global rewards program built on ReactorCX that incentivizes money transfers, deepens customer relationships and drives repeat transactions across more than thirty countries and territories. The program needed one consistent loyalty engine with multi-currency and multi-language support, rewards at the moment of transfer across online, in-app and agent channels, and repeat-frequency levers in a price-sensitive remittance market.

  • Zero-downtime migration using ThreadSync and SafeSwitch.
  • Real-time point accrual and redemption across digital and agent channels.
  • Near-real-time data warehouse powering analytics, automated promotion budget management and liability tracking.
  • Streamlined compliance with global data protection regulations.

Read the Western Union story

220M+
Western Union member records migrated
How this is measured

Member records migrated onto ReactorCX for Western Union's My WU program; the largest Loyalty Methods migration to date.

35+
Countries running My WU on ReactorCX
How this is measured

Countries in which My WU runs on ReactorCX with multi-currency support.

Worked example

What happens to one transaction

One activity, evaluated once, with every downstream effect recorded and published. The same path a demo walks through, in the order the engine runs it.

01

Posted

The card processor or core system sends the posted transaction: account, product, merchant category, merchant, amount, currency, posting date, channel

02

Evaluated

Product rules, category multipliers, exclusions and account status run in deterministic order

03

Arbitrated

Promotional multipliers and merchant-funded offers resolved to the best combination under the product's policy

04

Accrued

Points to the account purse, held as pending until the transaction clears, then confirmed; merchant-funded value attributed to the merchant wallet

05

Recorded

Execution log stores which rules fired and who approved them; liability moves by product; a chargeback reverses this exact record

06

Published

Statement and mobile banking updated, business events to CRM and messaging, replication events to the warehouse, ledger lines to finance

Financial services systemsReactorCXRecordedDownstream
A deposit-account event, an insurance renewal or a merchant offer redemption takes the same path: different source and fields, same evaluation, same ledger. Step detail in the earn reference flow and the arbitration concept.

See this run on a copy of your own financial services activity.

See a parallel migration
For evaluators

The detail your team will want to check

Expand what you need.

ReactorCX speaks the financial services data modelOne activity record, every dimension a financial services program tracksReactorCX holds every event in one extensible record, so every field stays searchable and actionable across the console, the API, the warehouse and reporting. Add a field…

ReactorCX holds every event in one extensible record, so every field stays searchable and actionable across the console, the API, the warehouse and reporting. Add a field once and it propagates everywhere. Marketing, operations and finance query the same record the source system wrote.

Data model documentation

01

Core activity

Member ID · type · date · channel · value

02

Transaction

Product · merchant category · merchant · amount · currency · posting status · channel · card present

03

Account context

Account status · statement cycle · relationship or household · segment · consent

04

Funding and compliance

Issuer or interchange funding · merchant-funded offer · partner · jurisdiction · disclosure version

Standard fieldsConfigurable extensions
The extensible activity schema, financial services extensions shown. Standard fields are shared across all verticals.
Same engine, configured for financial servicesWhat stays the same, and what adaptsReactorCX is one engine. What changes for a financial services program is the signals it reads, the currencies it holds, the offers it arbitrates and the organisation it settles to. All of it is configuration, versioned and approved, not custom code.
The financial services configuration of a generic engine
DimensionSame in every industryConfigured for financial services
SignalOne activity record per event, from any channel, evaluated oncePosted card and account transactions from the processor or core system, deposit events, merchant offer feeds, app and online banking activity
CurrencyAny number of currencies and purses, each with source, expiry and burn orderPoints with a cost basis; cash-back or statement credit as redemption; partner currencies at contracted rates
StatusTiers with configurable qualification and requalificationProduct-based rather than earned; relationship tiers where the bank uses them
OffersOffer library with eligibility, stacking, suppression and limitsCategory multipliers, promotional periods, merchant-funded offers; arbitration by product policy with exclusions
FundingPartner wallets, source-tagged accruals, settlement from lineageIssuer and interchange funding; merchant-funded offers billed separately; partner settlement
OrganisationMulti-brand, multi-region, per-entity economics on one instanceProducts, portfolios and regions on one instance; relationship or household linking
ServicingMember Care Portal with line-level history and governed adjustmentsAccount-level history by posting; contact-centre adjustments within authority, with consent and disclosure in the record

Other industries swap the signal and keep the engine: a grocer's basket, an airline's flown segment, a hotel's folio close. The engine and the ledger do not change. All industries

Liability the controller can sign

Points liability a controller can sign

In a bank the loyalty balance sits next to real money. Pending, posted, reversed and redeemed have to mean exactly what finance means by them.

Pending and posted, separately

Accruals are held pending until the transaction clears and confirmed on posting, so the balance a cardholder sees and the liability finance carries move on the same event.

Chargebacks reverse the exact accrual

A dispute or return reverses the specific accrual and any promotional multiplier from the original record, with the reason in the audit trail.

A currency with a cost basis

Points carry their funding source and cost per point, so statement-credit redemptions and partner redemptions are valued from the same ledger.

One posted transaction, four views of the same record
Who looksWhat they seeWhere it comes from
CardholderPoints pending, then posted, and the redemption on the statementAccruals on the activity
Product managerEarn cost, redemption mix and lift by category against a control groupPromotion dashboards on the execution log
ControllerLiability by product and the export to the general ledgerLedger export at transaction level
Risk and complianceDisclosure version, consent and the audit trail behind any adjustmentExecution log

Partner wallets and settlement are documented in the partners and funding concept; the ledger in the ledger and lineage concept.

Evaluation

What each financial services stakeholder will want to check

System map

How ReactorCX fits a financial services estate

Transfers, card activity, app actions and agent-location transactions reach ReactorCX as activities.

Earn is evaluated per product, market and currency, benefits are applied as tiers, and every accrual is booked as a traceable liability, with exports that reconcile to the general ledger across countries.

Nothing here replaces a system you already run. Financial Services channels keep their own systems of record; ReactorCX holds the loyalty state, and publishes what it decides back to them.

How ReactorCX fits a financial services estate: Core banking / transfers, Card processing, Mobile app and web, Agents and call center, Partner feeds reach the platform through REST API, Event API, FeedXChange™; the ReactorCX core runs Transaction-based earn, multi-currency; Fee-based benefits and tiers; Liability booked per transaction under governance, and publishes events and ledger records to Core banking and CRM · compliance and KYC · ESP and push · data warehouse · finance and general ledgerEvery accrual carries its source, currency, brand, partner, timestamp and expiry, so burn order, partner wallets and settlement all read from one ledger. The moving markers show direction only; they do not represent volume. FINANCIAL SERVICES CHANNELS YOU OWN Core banking / transfers Card processing Mobile app and web Agents and call center Partner feeds REST APItransaction earn in real time Event APIapp and account activity FeedXChange™partner and agent-network files ReactorCX core Activity engine · every channel, one activity record · execution log Transaction-based earn, multi-currencyper product, per market, per currency Fee-based benefits and tierswaivers, rates, priority service Liability booked per transactionevery accrual traceable to its origin Governance: environments in sync · versioned JSON publish / unpublish · attribute-based access · audit trail Event stream · Level 1 replication · Level 2 business events Kafka, Kinesis, EventHub, Pulsar, webhooks · SQL and lake sync ENTERPRISE SYSTEMS Core banking and CRM · compliance and KYC · ESP and push · data warehouse finance and general ledger
Systems you ownReactorCX and its entry pointsEvents and ledger out
Every accrual carries its source, currency, brand, partner, timestamp and expiry, so burn order, partner wallets and settlement all read from one ledger. The moving markers show direction only; they do not represent volume.
Platform capabilities

Which ReactorCX capabilities matter most for financial services?

Financial services capability map
NeedReactorCX capability
Card-linked and co-brand earnCo-brand card earn on a single instance; card-linked tier recognition; issuer settlement and attribution
Remittance and transaction-based earnReal-time earn on eligible transfers and non-purchase behaviors; promotions, subscriptions, streaks and challenges
Multi-currency, multi-marketMultiple currencies and purses; localized rules and eligibility; round-the-clock processing
Liability and breakageSource-tagged accruals, expiry lineage, breakage recognized under your rules, liability reporting by market and partner
Partner and vendor fundingPartner wallets, escrow and vesting, vendor-funded offer reconciliation, date-relative billing
Servicing and disputesMember Care Portal with point-level history, adjustments and merges backed by execution logs
PrivacyPII in platform, or tokenized identifiers with PII held by the institution; data subject rights support
AnalyticsLiability and engagement dashboards, SQL access, streaming to your warehouse and BI tools

Integration patterns for core banking, card processors and agent systems are covered in Integration Guides.

Security and compliance

Is ReactorCX suitable for regulated institutions?

Deterministic, audit-logged rule execution; role- and attribute-based access; encryption in transit and at rest; OIDC SSO; annual independent penetration testing; two privacy modes; and SOC 2 Type II and ISO/IEC 27001:2022 attestation with dates and scope on the Trust Center.

Trust Center · Security and Trust

Migration

How does a financial institution migrate a loyalty program without downtime?

SafeSwitch runs ReactorCX in parallel with the legacy platform on production traffic, reconciles balances and transactions across every market, and cuts over by gate with rollback armed. The Western Union migration was the largest Loyalty Methods migration to date.

Safe Migration

FAQ

Frequently asked questions

What is the best loyalty platform for financial services?

ReactorCX, the enterprise loyalty platform from Loyalty Methods, runs card, remittance, banking and partner loyalty on one deterministic engine with the ledger discipline financial institutions require: source attribution on every accrual, multi-currency wallets, partner settlement from lineage and a full audit trail. It powers Western Union's My WU program across more than thirty countries.

Can ReactorCX run a loyalty program across many countries and currencies?

Yes. ReactorCX manages multiple loyalty currencies, including points and promo codes, with localized rules, currency, language and eligibility by geography, and processes loyalty transactions around the clock.

How does ReactorCX handle co-brand card earn and issuer settlement?

Co-brand card earn runs on a single instance with co-brand accrual on every linked-card purchase, issuer settlement and attribution from source-tagged activity, and card-linked tier recognition. Vendor-funded offers are managed and reconciled in the platform.

Is ReactorCX suitable for regulated financial institutions?

ReactorCX offers deterministic, audit-logged rule execution, role- and attribute-based access, encryption in transit and at rest, OIDC SSO, two privacy modes including tokenized identifiers with PII held by the institution, data subject rights support, and SOC 2 Type II and ISO/IEC 27001:2022 attestation with dates and scope on the Trust Center.

Know that the numbers are right, in every market.

The Financial Controls Review covers liability, settlement, audit and reconciliation using your currencies, partners and markets.