Plug-in onchain loyalty for stablecoin card issuers outside Rain — replicate the beta-proven 25% spend lift without building in-house.

1. Rain's Avalanche Card beta proved that enrolled cardholders spend 25% more than non-enrolled users — the first public proof that onchain card loyalty delivers measurable retention ROI, validating the business case for every issuer outside Rain's platform that needs to match this benchmark.
2. Forbes reported that stablecoin card competition has shifted from proving stablecoins can be spent to top-of-wallet retention, creating immediate budget pressure on issuers without a loyalty program to match competitors who now have one.
3. Rain's 100+ live card programs are locked into its proprietary issuing stack, leaving hundreds of independent stablecoin issuers with no loyalty infrastructure and no neutral vendor to buy one from — a clear supply gap at the moment demand is accelerating.
4. Onchain-native loyalty points minted post-finalization carry zero stranded-liability accounting exposure — a structural advantage over legacy loyalty that issuers cannot achieve by bolting a traditional vendor onto an onchain card program.
5. Rain had to acquire Uptop to build onchain loyalty rather than buy it off the shelf, confirming that no existing vendor could supply this capability — and that the build complexity is prohibitive for most independent issuers acting alone.

Catalyst. Rain's public beta showing 25% spend lift is the proof point the market was waiting for — it simultaneously validates that onchain card loyalty works and signals that the top-of-wallet retention race has begun for every issuer not already on Rain's platform.

An onchain loyalty-as-a-service platform exposing a single webhook API that stablecoin card issuers plug into their existing card processor (Marqeta, i2c, Galileo) in under 30 days. On each transaction finalization, the platform mints ERC-20 loyalty tokens directly to the cardholder's onchain wallet, maintaining zero stranded-liability risk. A pre-built merchant redemption marketplace covering cashback, stablecoin top-up, and travel rewards is included so issuers launch with a complete catalog from day one. A real-time analytics dashboard surfaces spend-lift cohorts, churn curves, and A/B test results so product teams can optimize loyalty mechanics without engineering support. No changes to the issuer's core card stack are required.

What's different. Unlike Rain Rewards, this platform is issuer-agnostic and chain-agnostic — it integrates via standard webhooks into any major card processor without requiring migration to Rain's issuing stack. Unlike legacy loyalty vendors such as Loyalty One or Braze, the architecture is onchain-native: ERC-20 points minted post-finalization deliver zero stranded-liability risk and full auditability that traditional batch-ledger systems cannot match. A pre-built merchant redemption marketplace means issuers launch with a complete loyalty catalog rather than an empty points ledger, compressing time-to-value from 12 months to under 30 days.

Jobs to be done

flowchart LR
  Issuer[Stablecoin Card Issuer] --> API[Loyalty API Webhook]
  API --> Processor[Marqeta / i2c Processor]
  Processor --> Mint[Onchain Point Mint]
  Mint --> Wallet[Cardholder Wallet]
  Wallet --> Redeem[Merchant Redemption Network]
  Redeem --> Lift[25% Spend Lift]

Executive takeaways

• Stablecoin card competition has shifted from proving spend acceptance to winning top-of-wallet retention [8].
• Rain's public proof point validates the use case, but also shows the market gap: the best-known rewards product is locked inside a vertically integrated issuing stack [1][2][3].
• Integration risk is lower than it first appears because processors and card stacks already expose event-driven primitives; commercial access and reward supply are the harder bottlenecks [24][28][35][56][63][68].
• LatAm is the clearest beachhead, but the loyalty-only revenue wedge is still modest at current pricing, so adjacent analytics/CRM expansion likely matters [39][44][45][46].
• Stack owners are the main competitive threat because they can bundle rewards into the issuing layer faster than generic loyalty engines can learn onchain payments [1][4][28][35][76].

Market definition

The addressable category is issuer-neutral loyalty infrastructure for stablecoin-backed card programs: software that consumes card and settlement events, applies earn rules, and powers redemption without forcing an issuer to migrate off its current stack [1][14][56][63][68].

Customer and buyer

The operational buyer is usually the VP Product or CTO running a stablecoin card or digital-dollar program, but deals close only when finance/compliance believe the rewards structure is auditable and economically tied to retention [1][39][41][80][100].

Buying triggers

• A competing stablecoin card launches cashback or loyalty and the issuer needs a top-of-wallet response before spend migrates. [8][91]
• A new card launch or market expansion needs differentiation without a full processor or issuer-stack migration. [13][22][35]
• Finance teams want rewards without the delayed reconciliation and second-ledger overhead of legacy loyalty setups. [1][3][100]

Willingness to pay

Budget can be justified out of interchange-bearing spend and retention gains: Rain published a 25% spend lift, Bridge says cards can increase engagement and share of wallet, and fintech-focused loyalty vendors argue the goal is lower-cost engagement rather than perpetual cash burn. [1][14][80][89]

Category dynamics

Growth signal ~100% YoY stablecoin card spend growth

Validation signals

• Rain’s public beta showed enrolled cardholders spent about 25% more than non-enrolled users.
• Uptop’s Cavaliers program delivered a 21% lift in spend and 51% growth in team-shop sales before Rain integrated it.
• Bridge says Airtm’s stablecoin card increased engagement, retention, and share of wallet.
• Bitso says dollar-linked stablecoins were 40% of 2025 crypto purchases in its core LatAm markets.
• RedotPay says it already serves 6M users with $10B annualized payment volume, showing that stablecoin-linked spend can scale.

Regulatory & technical constraints

• Convertible or transferable reward value can pull the product toward money-transmission or e-money analysis depending on jurisdiction.
• Consumer-facing prepaid or card-linked flows remain exposed to Regulation E-style protections and dispute expectations.
• Even if rewards are minted post-settlement, customer incentive liabilities still need to be accounted for under customer-contract standards.
• Launch timelines are constrained by issuer, processor, and sponsor approvals; regulated sponsors advertise weeks-long launch cycles rather than instant go-live.

The field splits into vertically integrated crypto-card stacks (Rain), regulated issuer/sponsor stacks (Immersve, StraitsX), and generic loyalty engines (Antavo, Currency Alliance). The neutral-vendor opening exists only where issuers insist on keeping their current processor or wallet stack [1][28][35][76][80].

Why incumbents do not win by default

• Card processors. Marqeta, i2c, and Galileo already expose the event pipes and in i2c’s case some loyalty primitives, but they stop short of a neutral, cross-issuer redemption and analytics layer.
• Crypto card stacks. Rain and adjacent wallet/card stacks can bundle rewards, but they only win by default when an issuer also accepts their issuing or sponsor layer.
• Loyalty SaaS. Generic loyalty engines are strong on offers and points, but they are not designed around stablecoin settlement, onchain wallets, or issuer-grade card operations.
• Issuer sponsors and networks. Networks and issuer sponsors unlock acceptance and compliance, but they still leave issuers needing a portable differentiation layer and merchant-funded offer strategy.

Independent stablecoin card issuers now have a clear retention problem because Rain publicly showed a 25% spend lift from native rewards while keeping the product inside its own stack. The proposed company sells a processor-neutral loyalty overlay to issuers that do not want to migrate onto Rain but still need a rewards response inside one budget cycle. The first beachhead is LatAm digital-dollar card issuers with 10,000–50,000 active cardholders, where dollarization demand is already strong and a competitor rewards launch can trigger immediate retention spend. The initial product should start with post-settlement earn rules, statement credits or tightly permissioned wallet-visible points, and cohort analytics before expanding into a broader merchant-funded marketplace. This sequencing is deliberate because research says event access is technically feasible, but sponsor approvals, reward supply, and legal structure are the real gating factors. The biggest upside is becoming the neutral retention layer across non-Rain stablecoin card stacks; the biggest risk is that full-stack issuers or processors bundle enough loyalty functionality to compress third-party TAM. The market model in the research supports a reachable Y3 SOM of about $1.1M annual revenue, which is large enough for a valuable infrastructure wedge only if analytics, CRM, and partner distribution expand ARPU over time. Exact counts of independent issuers that can grant third-party webhook access are still unproven, so the investment case depends on early discovery and pilot conversion data.

Problem

• Stablecoin card issuers outside Rain are exposed when a competing card launches rewards, because top-of-wallet behavior shifts quickly and many issuers still run no program or a manual cashback workflow.
• Legacy loyalty vendors do not fit onchain settlement and wallet flows, while an in-house build can take 12–18 months and still leave finance and compliance with liability, reconciliation, and approval complexity.

Solution

• Build a loyalty overlay that consumes processor events from existing card stacks, applies post-settlement earn rules, and launches without requiring issuer migration to a new issuing platform.
• Start with closed-loop or tightly permissioned wallet-visible rewards plus statement-credit redemption and spend-lift analytics, then add a curated merchant-funded catalog once supply and compliance are proven.

Why we win

• The wedge is processor-neutral distribution to issuers that want Rain-like rewards without accepting Rain's issuing stack.
• Post-settlement reward issuance gives finance and compliance a more auditable system than legacy batch-ledger loyalty while preserving wallet-native user experience.
• Cross-issuer benchmark data, prebuilt processor connectors, and merchant redemption relationships can compound into switching costs that generic loyalty SaaS lacks.

Milestones

flowchart LR
  Wedge[LatAm issuer retention retrofit] --> MVP[Event-driven loyalty MVP]
  MVP --> Proof[Spend-lift and launch-speed proof]
  Proof --> Expansion[Analytics CRM and regional expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least half of qualified non-Rain issuers can provide third-party settlement-event access without prohibitive sponsor escalation.
• The first production pilots produce at least 10% spend lift or measurable churn improvement within 90 days.
• Buyers accept closed-loop or tightly permissioned wallet-visible rewards as a sufficient first release.
• Merchant or partner-funded redemption supply reaches a meaningful share of reward value within the first year.
• Analytics and CRM upsell can raise revenue per issuer above the base loyalty fee implied by current pricing.

Open diligence questions

• How many target issuers can expose webhook events today, and who must approve access?
• What budget owner signs the deal when rewards are framed as retention spend rather than marketing software?
• Can the product launch with statement credits and closed-loop points, or do priority buyers insist on transferable token rewards?
• What does a compelling day-one redemption catalog require in merchant relationships and economics?
• How quickly could Rain, i2c, or another stack owner neutralize the wedge by bundling similar functionality?

Model sanity

• Revenue engine. The base case is driven by issuer count reaching 15 and each mature issuer growing toward 40k active cardholders on the $1.89 per-user revenue base.
• Must go right. Processor and sponsor approvals must stay inside one-quarter pilot windows or the sales-cycle sensitivity quickly erodes the cash buffer.
• Model breaks if. If analytics attach stays weak and issuer actives stall below 30k, the downside case turns cash negative before the seed milestone.
• Next-round proof. A credible seed case is 6 production issuers, two paid analytics expansions, and one repeatable case-study-backed channel motion by late Y2.

Scenarios

Sensitivity

flowchart LR
  Issuers --> ActiveCardholders
  ActiveCardholders --> SubscriptionRevenue
  ActiveCardholders --> RedemptionVolume
  RedemptionVolume --> MarketplaceTake
  SubscriptionRevenue --> Revenue
  MarketplaceTake --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: Base-case Y3 revenue per FTE is still well below typical venture SaaS efficiency, so analytics/CRM expansion must improve monetization after the first loyalty wedge. · The company remains EBITDA negative through Y3, which means the pre-seed must buy enough proof to support a seed round rather than self-fund to breakeven. · Revenue concentration is high because the model still depends on roughly 15 issuer logos; losing one large issuer would matter materially. · The Q4Y3 revenue exit requires existing issuers to grow active cardholders materially after launch, not just add logos.

• Rain Platform Expansion. Rain extends its Rewards product as a horizontal SaaS available to card programs outside its issuing stack, becoming a direct and well-resourced competitor with an existing 100+ customer base and pre-built merchant network. Mitigation: Build deep exclusive integrations with the two largest non-Rain processors and sign exclusive merchant redemption partnerships before Rain can replicate them; compete on time-to-value and processor neutrality for independent issuers.
• Regulatory Token Classification. Regulators classify onchain loyalty tokens as digital assets or securities subject to licensing, requiring both issuers and the loyalty platform to obtain money-transmitter or broker-dealer licenses to operate. Mitigation: Structure tokens as non-transferable, non-tradeable rewards redeemable only within a closed merchant network, mirroring the established regulatory treatment of airline miles and major credit card points programs.
• TAM Concentration Risk. The stablecoin card market consolidates around two or three dominant platforms, leaving too small a long-tail of independent issuers for a standalone loyalty vendor to build a durable business. Mitigation: Expand the loyalty platform upmarket to serve crypto neobanks and DeFi protocols seeking onchain cardholder and depositor retention, diversifying beyond pure stablecoin card issuers before consolidation closes the window.