Loyalty clearing ledger for card issuers launching cross-brand earn, burn, and transfer rewards without bespoke deal ops.

1. A single API now connects loyalty programs across travel, retail, hospitality, and fintech, making cross-brand reward programs operationally feasible for more issuers.
2. More than 50M active members across named brands suggests enough network density exists for buyers to treat interoperability as a real distribution and retention channel.
3. When partnership launch time falls from months to days, operational debt in pricing, liability, and settlement becomes the next urgent bottleneck.
4. Because the API already supports earn, redemption, transfer, and co-acquisition, the market is moving toward full loyalty value exchange rather than simple affiliate offers.

Catalyst. Benji's 50M-member network and promise of launching cross-brand loyalty partnerships in days instead of months show that interoperability is becoming real infrastructure, which makes back-office control software newly urgent for issuers that can now turn on many more partnerships.

Build a neutral operating layer that sits between an issuer's rewards ledger, partner brands, card processors, and customer channels. The product calculates point exchange economics for every partner interaction, tracks who owes what to whom, and flags broken rules before value is exposed to cardholders. Finance teams get a daily liability and settlement view, while partnerships teams get launch templates for new earn, burn, and transfer deals without opening a new spreadsheet stack every time. Support and fraud teams share the same case history when members dispute redemptions or gaming behavior appears. Over time, the company becomes the clearinghouse that makes multi-brand loyalty behave more like a modern payments network than a patchwork of bilateral deals.

What's different. Loyalty platforms typically help a single brand run points and campaigns, while affiliate networks optimize traffic and merchant offers. This company owns the harder layer where partner-point economics, liabilities, settlement, and abuse rules must reconcile across multiple programs. That position creates proprietary data on partner performance, transfer behavior, and exception patterns that can compound into better underwriting and routing over time.

Jobs to be done

flowchart LR
  Buyer[Rewards GM at issuer] --> Pain[Cross-brand loyalty deals create manual liability and settlement work]
  Pain --> Product[Loyalty clearing ledger]
  Product --> Outcome[Faster profitable partner launches with auditable rewards economics]

Executive takeaways

• Cross-brand rewards interoperability is already real enough that the bottleneck is moving from API wiring to finance and controls: Benji markets 10x faster launches across a 50M+-member network, while large issuers already train users to expect transfers across airline and hotel partners ([1], [3], [4], [22], [23], [24], [34]).
• Buyer pain is operational as much as experiential: relevant, easy-to-find rewards improve top-of-wallet behavior, but half of checkout offers go unseen and many programs still create liabilities that finance teams must defer, reconcile, and explain ([10], [11], [17], [18], [19], [20], [21]).
• The competitive set is fragmented rather than settled. Currency Alliance is closest on partner exchange and settlement, while SessionM, Open Loyalty, Antavo, and Talon.One optimize engagement or rules execution rather than neutral issuer-grade clearing ([5], [6], [7], [25], [26], [27], [28], [29], [30], [35], [36], [37]).
• Go-to-market will be procurement-heavy because banks must treat the vendor as a regulated third party, and loyalty points themselves are separate performance obligations that create deferred-revenue and liability-management work ([8], [9], [10], [11], [16]).

Market definition

Software and workflow infrastructure for pricing, recording, reconciling, and governing multi-brand loyalty value exchange between issuers, fintechs, and partner programs; narrower than loyalty marketing clouds, but deeper on liability, settlement, and exception handling ([5], [6], [10], [11], [27], [28], [29], [35]).

Customer and buyer

Primary users are rewards, partnerships, and loyalty leaders who need new transfer or merchant-funded experiences; economic buyers are usually the GM of rewards, VP partnerships, or CFO because partner launches change both engagement economics and balance-sheet liabilities ([8], [9], [11], [18], [22], [23]).

Buying triggers

• A rewards relaunch or first transfer-partner rollout exposes new reconciliation, timing, and exception-handling work across multiple partners. [1][3][22][23][24]
• Pressure to improve top-of-wallet card usage pushes issuers toward more relevant and easier-to-redeem rewards. [17][18][19]
• Risk, finance, or compliance teams get pulled in once loyalty points create deferred revenue, vendor oversight, and auditability requirements. [8][9][10][11]

Willingness to pay

Budget exists when the product is sold as infrastructure inside a rewards refresh: Benji already prices on live connections and transactions, Antavo packages loyalty into enterprise tiers, and the engagement upside matters enough that issuers care about relevance and redemption friction. [2][18][20][30][35]

Category dynamics

Growth signal ≈6.1% CAGR in U.S. consumer credit card purchase volume (2022-2024)

Validation signals

• Benji positions the category around 10x faster partnership launches and a network spanning 50M+ members.
• Currency Alliance says a leading U.S. bank saw partner-redemption transaction volumes grow nearly 300%.
• Bilt’s rewards ecosystem reportedly already reaches 5M+ users, 40,000 merchants, and one in four U.S. apartment buildings.
• PYMNTS studies show strong user appetite for relevant offers but persistent visibility and redemption friction.

Regulatory & technical constraints

• Any bank or credit-union deployment must survive formal third-party risk management and ongoing monitoring.
• Loyalty points and rewards can create separate performance obligations that require revenue allocation and deferred-revenue treatment.
• Enterprise buyers will expect audit logs, role-based access, and strong data controls before trusting a partner-clearing system.
• Transfer timing, conversion ratios, and partner event semantics vary across ecosystems and need explicit exception logic.

The market splits into four classes: connectivity networks (Benji, Currency Alliance), loyalty operating clouds (SessionM, Open Loyalty, Antavo), rules/promotion engines (Talon.One), and card-linked-offer/data rails (Visa, Fidel, Banyan). The gap is a neutral, issuer-facing system of record for partner pricing, liability reconciliation, settlement, and exceptions across whichever front-end or network the buyer chooses ([1], [5], [6], [25], [27], [29], [30], [31], [32], [35], [36], [37]).

Why incumbents do not win by default

• Connectivity networks. Networks like Benji and Currency Alliance remove integration friction, but they do not automatically become the buyer’s finance workflow, exception desk, or neutral ledger across all counterparties.
• Enterprise loyalty clouds. SessionM, Open Loyalty, and Antavo are strong at running a program’s earn-and-burn logic, but they are optimized for a brand-owned program rather than multi-party clearing between independent programs.
• Promotion and loyalty engines. Talon.One proves that flexible incentive logic is valuable in financial services, yet its core wedge is execution and personalization rather than partner settlement and liability accounting.
• Card-linked offer rails. Visa and Fidel help trigger and settle merchant-funded rewards events, but they are adjacent rails rather than full loyalty-liability operating systems.

Loyalty Clearing Ledger is a neutral subledger and operations layer for North American regional banks, card program managers, and consumer fintechs that are moving from simple cashback into cross-brand rewards. The researched market signal is real: Benji already markets 10x faster partner launches across a 50M+-member network, and major issuers already condition consumers to expect transfers across airline and hotel ecosystems. The resulting pain is less about front-end rewards UX than about partner pricing, deferred-revenue logic, settlement, exception handling, and vendor-risk controls once multiple external programs are involved. The first product should therefore be a human-in-the-loop clearing ledger for one issuer launching its first external transfer or merchant-funded partner, not a full loyalty cloud or consumer app. Research supports an estimated $90.0M TAM, $36.0M beachhead SAM, and roughly $3.0M year-3 SOM if the company stays focused on mid-market issuer programs before broader expansion. The go-to-market only works if first customers buy during a rewards relaunch or first partner rollout, pricing is tied to active members and live partners, and channel access comes through loyalty networks, processors, and consultants already inside the launch workflow. The biggest strategic risk is that buyers accept manual spreadsheets or buy enough settlement functionality from Currency Alliance or other adjacent vendors instead of funding a new neutral control layer. Public evidence is still thin on who owns the system of record today and how much month-end-close pain exists after the first few partners go live, so early diligence must prove budget ownership, data access, and repeatable deployment speed.

Problem

• Regional issuers and consumer fintechs launching transfer or merchant-funded rewards still manage partner pricing, liabilities, settlement, and exception handling across exports, spreadsheets, email threads, and one-off engineering work.
• As API connectivity compresses launch time from months to days, finance, risk, and support teams become the bottleneck because existing loyalty tools are not the neutral system of record for cross-program clearing.

Solution

• Provide a neutral loyalty clearing subledger that records each earn, redeem, transfer, and co-acquisition event, calculates partner economics, reconciles liabilities, and produces audit-ready settlement and GL exports.
• Start with one issuer launch workflow, human-in-the-loop exception queues, and reusable partner templates so customers can add external rewards partners without building a dedicated finance-operations stack.

Why we win

• The wedge sits where current alternatives are weakest: networks and loyalty clouds help connect or run programs, but they do not consistently own the issuer-facing finance workflow, partner settlement desk, and audit-ready subledger across counterparties.
• Each deployment compounds reusable pricing rules, partner launch templates, and exception-resolution data that improve onboarding speed and create leverage with processors, API networks, and consultants.

Milestones

flowchart LR
  Wedge[First partner launch clearing wedge] --> MVP[Human in the loop clearing ledger]
  MVP --> Proof[Faster launches and cleaner liability close]
  Proof --> Expansion[Multi partner rewards control plane]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 40% of qualified beachhead issuers must already use spreadsheets or manual exports to manage partner-point liabilities and settlement.
• A rewards relaunch or first external partner rollout must create enough urgency that buyers accept a paid pilot instead of deferring the project.
• The first 2-3 connectors must cover enough issuer and partner data to reach a first reconciled event within 60 days.
• Pilot customers must convert to production above 60% when the product shortens launch and close workflows.
• Connectivity vendors and loyalty clouds must remain incomplete as issuer-facing finance systems of record even after adding basic ledger features.

Open diligence questions

• Who owns partner-point liability reconciliation today inside a regional issuer: rewards, finance, processor, or an outside consultant?
• How many external partners need to be live before manual workflows become materially painful?
• Which budget line funds this product during a rewards refresh: rewards modernization, finance systems, or partnership launch services?
• How much of the deployment can be standardized across Benji-like networks, processors, and existing loyalty platforms?
• What minimum security, audit, and third-party risk package is required to clear vendor review at a regional bank?

Model sanity

• Revenue engine. Base-case revenue comes from eight paying logos by Y3 end, with each logo moving from a paid pilot into roughly $336K production ARR and later partner expansion.
• Must go right. The team has to keep deployments under roughly 60 days so pilots convert and referral channels keep feeding a procurement-heavy funnel.
• Model breaks if. A one-quarter procurement slip plus gross margin stalling below 68% pushes cash toward the downside case before the next round.
• Next-round proof. The seed-ready proof point is six production logos, 70%+ gross margin, and at least two channel-sourced wins by Q4Y2.

Scenarios

Sensitivity

flowchart LR
  Leads[Qualified launch projects] --> Pilots[Paid pilot launches]
  Pilots --> Production[Production logos]
  Production --> Expansion[Second partner expansion]
  Expansion --> Revenue[Subscription plus pilot revenue]
  Revenue --> GrossProfit[Gross profit]
  GrossProfit --> Cash[Cash runway]

Flags: Revenue concentration stays high because only eight logos drive nearly all Y3 revenue; one delayed bank launch matters. · The model assumes connector reuse is real enough to keep headcount flat after Q4Y2 while gross margin still rises. · Sales timing risk remains the biggest cash risk because CFO and vendor-risk approval sit in the buying path.

• Slow buyer education. Many issuers may not realize clearing and liability become the bottleneck until after their first few partner launches go live. Mitigation: Sell into rewards relaunches and first external partnership projects where the implementation pain is immediate and budget already exists.
• Fragmented partner data. Loyalty partners may expose inconsistent event and settlement data, making fully automated reconciliation difficult early on. Mitigation: Start with the highest-value event types, support file-based and human-in-the-loop reconciliation, and automate deeper as partner data quality improves.
• Platform bundling. Loyalty API networks or incumbent rewards platforms may add basic settlement features once the category matures. Mitigation: Stay neutral across networks and win on multi-partner finance workflow, cross-brand liability intelligence, and issuer-grade operational controls rather than raw connectivity.