Configurability & White-label
This page is the full reference behind the “What you can configure” section on each product page. It covers what you can brand, what you can toggle, and what stays fixed — and how that differs across the three partnership models.
The three models
Section titled “The three models”| Capability | API / Embedded | White-label | Custom |
|---|---|---|---|
| Use Moria’s financial rails | Yes | Yes | Yes |
| Interface | You build it | Moria apps, your brand | Moria apps, your brand |
| Moria-hosted web & mobile apps | — | Yes | Yes |
| Logo, colors, typography | In your own UI | Yes | Yes |
| Your own domain | In your own UI | By arrangement | By arrangement |
| Choose which products to enable | Yes | Yes | Yes |
| Per-partner pricing | Yes | Yes | Yes |
| Isolated members & data | Yes | Yes | Yes |
| Member-facing language (ID/EN/AR) | Yes | Yes | Yes |
| Bespoke products or flows | — | — | Yes |
| Custom third-party integrations | Via your backend | By arrangement | Yes |
API / Embedded — you keep your own app and build the member experience yourself, calling Moria for wallet and product operations. Fastest to launch; you own the UI entirely.
White-label — you ship Moria’s web and mobile apps under your own brand. Your members never see the Moria name. You configure branding, product mix, and pricing; Moria runs the platform.
Custom — everything white-label offers, plus bespoke products, flows, or integrations built for your organization on the same core rails.
What you can brand
Section titled “What you can brand”Branding is applied per organization, so each partner (or each organization on a shared platform) presents its own identity:
- Identity — logo, color palette, and typography, configured per organization and applied across the member-facing surfaces.
- Language — Indonesian, English, or Arabic for member-facing text, so the same platform can serve different audiences.
- Domain — serving the web app on your own domain is available by arrangement as part of white-label onboarding.
- Mobile apps — publishing the apps to the app stores under your brand is handled by arrangement during onboarding (store accounts, signing, and release are coordinated with you).
What you can toggle
Section titled “What you can toggle”- Product mix — enable only the products you want your members to see. A cooperative might run wallet + savings + dues only; a broader partner might enable the full catalog. Products not enabled simply do not appear.
- Pricing — fees are configured per partner (and can be refined per organization), by payment method and direction. See Fees & Pricing.
- Organization model — run a single organization, or many organizations under one platform, each isolated.
- Onboarding paths — allow member self-registration, invitation-only, or both. See Onboarding & KYC.
- Admin roles — grant your admins scoped permissions over members and products.
Data isolation
Section titled “Data isolation”On a multi-organization platform, each organization’s members, balances, and data are scoped to that organization. A member acting in one organization cannot see or reach another’s data. For a white-label partner this means your members and their money live in your own isolated space — the foundation for offering the platform as if it were your own.
What is fixed
Section titled “What is fixed”Some things stay constant across every model because they protect members and keep the platform sound:
- Shariah compliance and the underlying contracts (akad) — see Shariah & Compliance.
- Double-entry money handling and reconciliation — see Settlement & Reconciliation.
- Core security controls — transaction PIN, two-factor authentication, and encryption of personal data at rest.
- Identity verification (KYC) before a member can move money.
Related
Section titled “Related”- Platform & Wallet — the foundation these options configure.
- Fees & Pricing — the per-partner pricing model in detail.