B2B platform for digital goods

Gaming-Cafe SaaS Added On-Demand Top-Ups via FoxReload API

A B2B SaaS for gaming-cafe operators added on-demand top-ups via FoxReload β€” cafe cash handling fell 80% and ARPU rose from $32 to $50.

Gaming-Cafe SaaS Added On-Demand Top-Ups via FoxReload API

This case is a composite archetype based on anonymized data from FoxReload partners. Names and specific figures are illustrative and combine patterns from two vertical-SaaS providers serving gaming and cybercafe operators across the EU and CIS between 2024 and 2025.

Context

The archetype: a B2B SaaS that sells cafe-management software (booking, time-billing, station monitoring, member accounts) to gaming and cybercafe operators. About 1,400 paying cafes at the time of the FoxReload integration, average $32/month subscription, ~$540k ARR. The product team had a clear thesis: cafes already handled digital-goods purchases for walk-in customers using personal cards and informal cash transactions, and a managed in-product flow would capture both the cafe and end-customer experience.

The challenge: cafes are small businesses with no integration appetite. The SaaS needed to deliver the feature as a turnkey addition to its existing product β€” no separate signup, no separate billing, no new ops burden for the cafe owner.

Integration

7-week build:

  • Week 1: FoxReload sandbox, catalogue scoping (focused on the top 80 SKUs by cafe-walk-in demand: PSN, Steam, Riot, Mobile Legends, OTT subs).
  • Weeks 2–4: REST catalogue sync, webhook fulfilment, back-office reconciliation flow for the SaaS's 30% revenue share on top of FoxReload's wholesale margin.
  • Weeks 5–6: POS UX inside the existing cafe-management product. Single-button checkout, code-on-screen plus optional print-receipt.
  • Week 7: Pilot rollout to 40 cafes, then staged release across the base.

FoxReload features used: REST catalogue API, webhook order fulfilment, regional SKU filtering (per cafe country), and the partner revenue-share flag that lets the SaaS take its share before settlement.

Economics

Metric Before After 9 months Change
Paying cafes 1,400 1,520 +8.6%
Feature adoption (cafes using top-ups) β€” 71% new
SaaS ARPU per cafe $32 $50 +$18 (+56%)
Cafe cash-handling volume baseline βˆ’80% βˆ’80%
End-customer NPS lift β€” +18 new
Net SaaS revenue/month $44,800 $76,000 +70%

The SaaS didn't increase acquisition spend β€” the $18 ARPU lift was pure expansion revenue on the existing book. From the cafe's perspective, the SaaS subscription effectively paid for itself out of digital-goods margin within the first month for ~65% of cafes.

The cash-handling reduction was an unanticipated bonus. Before the integration, cafe staff handled cash for top-up requests from walk-in customers β€” which created reconciliation friction, occasional shrinkage, and an awkward UX. Routing those transactions through the cafe POS meant cleaner books and faster service.

Lessons

  1. Embedded monetisation beats marketplace monetisation. Cafes that already trusted the SaaS adopted the digital-goods feature at 71% within 9 months. A separate marketplace product would have struggled to hit 10%.
  2. Curate aggressively for vertical SaaS. 80 SKUs covered 94% of walk-in demand. Showing 5,000 SKUs would have crushed staff usability.
  3. Revenue-share at settlement matters. The FoxReload partner revenue-share flag eliminated a monthly invoicing loop the SaaS otherwise would have had to build.
  4. Frame it as POS expansion, not new business. Cafe owners cared about extra basket size per visitor, not about "becoming a digital-goods reseller."

If you run a vertical SaaS and want to scope a similar in-product expansion, request access at foxreload.com.

Frequently asked questions

What kind of SaaS does this archetype represent?
A vertical B2B SaaS selling cafe-management software to gaming/cybercafe operators (typical customer: 8–60 stations, $32 ARR/month subscription). Many also serve esports lounges and LAN centres.
How does the FoxReload integration help cafes?
Cafes can sell game top-ups, gift cards and OTT codes to walk-in customers from the cafe POS β€” without holding inventory or operating multiple supplier relationships. The cafe takes a retail markup, the SaaS takes a platform fee, and FoxReload supplies.
What does the integration look like for the SaaS?
REST catalogue API and webhook fulfilment. Typical build time: 5–7 weeks for a 3-engineer team, including a back-office reconciliation flow for the SaaS's revenue share.
Does this work for other vertical SaaS?
Yes β€” the same pattern applies to POS-style verticals (kiosks, hotels, retail chains) where the SaaS sells a primary product and digital goods are a secondary monetisation line.
Get FoxReload API access

Related articles