Skip to main content
Mini Apps are lightweight applications that run inside the Rebell SuperApp, allowing merchants and partners to provide digital services without distributing standalone mobile applications. They are designed to deliver interactive, multi-step user experiences that can seamlessly integrate payments, user identity, and merchant backend services.
Mini Apps are not payment APIs. They are embedded applications executed within the Rebell runtime and accessed directly by users from the SuperApp.

​
What Is a Mini App

A Mini App is:
  • A sandboxed application executed inside the Rebell SuperApp
  • Built using a JavaScript-based Mini Program framework
  • Distributed and updated centrally through Rebell
  • Capable of interacting with both Rebell APIs and merchant backend systems
Mini Apps allow merchants to deliver services such as:

Parking & Mobility

Parking payments, EV charging, ride services

Loyalty & Rewards

Points programs, digital coupons, membership cards

Booking & Reservations

Restaurant reservations, appointments, event tickets

Food Ordering

In-store ordering, delivery, pickup services

Digital Onboarding

Account creation, KYC flows, service enrollment

Service Management

Subscription management, account settings, support
All without requiring users to install a separate app.

​
What a Mini App Is NOT

A Mini App is not:
  • A standalone mobile application
  • A replacement for server-to-server Payment APIs
  • A backend system
  • A generic web page embedded in a webview
Mini Apps rely on a merchant backend for business logic and persistent data. Rebell serves only as the execution and distribution environment.

​
Mini Apps vs Payment API Integration

Rebell supports two complementary integration models. Choose based on your existing infrastructure and user experience goals.
Best suited when you already have:
  • A mobile app or website
  • A POS or backend-driven checkout
  • A need for payment-only functionality
Characteristics:
  • Server-to-server APIs
  • Merchant controls the UI
  • Payments are initiated externally
  • Ideal for ecommerce and POS
Learn more: Payment Integration Guide

​
Comparison Summary

AspectPayment APIsMini Apps
ExecutionMerchant backendRebell SuperApp
UI ownershipMerchantRebell-hosted
Use caseCheckout / POSFull service experience
User contextExternalNative SuperApp
Payment supportYesYes (embedded)
DistributionMerchant-managedRebell-managed
Mini Apps and Payment APIs can be combined: a Mini App may call merchant backend APIs, which in turn interact with Rebell Payment APIs.

​
High-Level Architecture

At a conceptual level, a Mini App involves three main actors:
  • The Mini App handles user interaction and UI
  • The merchant backend handles business logic and data
  • Payments are initiated either from the Mini App UI or via backend calls
This separation ensures security, scalability, and regulatory compliance.

​
When to Choose a Mini App

  • The service requires multiple user interactions
  • The experience should live entirely inside the SuperApp
  • You want to leverage Rebell’s identity and navigation
  • You want centralized updates without app store releases
  • You need a native-feeling experience for users
  • You only need a payment button or API-based checkout
  • You already have a mobile app that handles the full user journey
  • Your use case is purely transactional without UI flow

​
Developer Journey

The typical Mini App development flow follows these stages:
1

Understand Concepts

Learn Mini App concepts and architecture
2

Set Up Environment

Install Mini Program Studio and configure sandbox access
3

Build Mini App

Develop Mini App UI and client-side logic
4

Integrate Backend

Connect to merchant backend APIs
5

Add Payments

Integrate payments where required
6

Test

Test using simulator and sandbox environment
7

Submit for Review

Submit Mini App for Rebell review
8

Publish & Maintain

Publish to production and maintain versions

​
What This Section Covers

The Mini App Development section explains:

Architecture & Concepts

How Mini Apps are architected and executed

Development Environment

Tools used to develop and test Mini Apps

Mini App Lifecycle

How Mini Apps are reviewed, published, and versioned

Mini App APIs

Available APIs (JSAPI, OpenAPI, components)

Backend Authentication

How Mini Apps authenticate with merchant backends

Payments

How payments are triggered inside Mini Apps

​
Next Steps

Ready to start building? Begin with understanding the architecture:

Architecture & Concepts

Learn how Mini Apps are architected within the Rebell ecosystem