Skip to content
Moria

Fees & Pricing

What it is

Section titled “What it is”

Every money movement can carry a fee. Moria’s pricing is built so a fee is a transparent service charge, disclosed before the member confirms — not interest on money. This page explains how a fee is composed, how it is configured per partner, and how it is recorded.

Shariah basis

Section titled “Shariah basis”

Fees are service charges (ujrah) for a real service — running the payment rail and operating the platform. They are fixed and disclosed up front, added on top of the amount, and never accrue on a balance over time. There is no riba: a member pays a known fee for a service, not interest on a sum owed.

How a fee is composed

Section titled “How a fee is composed”

A charge has up to two parts, both added on top of the amount the member actually wants to move:

  • Provider fee — the cost of the external payment rail (e.g. a bank or QRIS channel), passed through.
  • Platform margin — Moria’s (and, by arrangement, the partner’s) own service fee.

The member’s product amount stays net — they receive exactly what they intended; the fees sit on top of what they pay.

flowchart LR
    BASE["Base amount<br/>(what the member moves)"]
    PROV["+ Provider fee<br/>(rail cost)"]
    MARG["+ Platform margin<br/>(service fee)"]
    TOTAL(["= Total charged"])
    NET(["Net credited / moved<br/>= Base amount"])

    BASE --> PROV --> MARG --> TOTAL
    BASE -.-> NET

    classDef base fill:#E8E1FF,stroke:#3C2C96,stroke-width:1.5px,color:#1E1B4B;
    classDef fee fill:#FFF3D0,stroke:#F4BE27,stroke-width:1.5px,color:#8B5A00;
    classDef out fill:#FDF8E8,stroke:#3C2C96,stroke-width:2px,color:#1E1B4B;
    class BASE base;
    class PROV,MARG fee;
    class TOTAL,NET out;

How pricing is configured

Section titled “How pricing is configured”

Pricing rules resolve from most specific to most general, so a partner can have its own schedule without affecting anyone else:

flowchart TD
    A[Charge for a transaction] --> B{Organization-specific rule?}
    B -->|Yes| R1[Use organization rule]
    B -->|No| C{Partner-specific rule?}
    C -->|Yes| R2[Use partner rule]
    C -->|No| R3[Use base rule]

    classDef step fill:#E8E1FF,stroke:#3C2C96,stroke-width:1.5px,color:#1E1B4B;
    classDef gate fill:#FFF3D0,stroke:#F4BE27,stroke-width:1.5px,color:#8B5A00;
    class A,R1,R2,R3 step;
    class B,C gate;
  • Per payment method — a different fee for each rail (bank, QRIS, and so on), or one catch-all.
  • Per direction — money-in and money-out are priced independently.
  • Preview before charge — a price can be previewed for any context so the exact provider/margin split is known before anything is saved or charged.

How a fee is recorded

Section titled “How a fee is recorded”

The provider fee and the platform margin are booked as separate ledger entries, not merged. That means every rupiah of fee is attributed to the right party — clean for your reporting, your reconciliation, and any revenue-share arrangement.

What you can configure

Section titled “What you can configure”
  • Your fee schedule — the margin per payment method and direction, scoped to your organization.
  • Revenue arrangement — how the platform margin is split with you, by agreement.
  • Disclosure — the fee breakdown shown to your members before they confirm.

Limits

Section titled “Limits”
  • Fees are added on top; the member’s product amount is always the net figure.
  • A fee is a fixed service charge — it never compounds and never accrues over time.
  • Provider fees reflect the real rail cost and are passed through.
Section titled “Related”