Split Engine Presets

Distributes funds by ratio. For example, a 50/30/20 split on GHS 100.00 sends GHS 50.00, GHS 30.00, and GHS 20.00 to three recipients. Rounding remainders are collected to a designated remainder recipient to ensure zero loss.

Sends fixed GHS amounts to each recipient regardless of the total transaction value. Any remaining balance after all flat fees are deducted is routed to a designated remainder recipient.

Pools funds across multiple transactions. Disbursement only fires once the accumulated pool reaches a configured threshold (e.g. GHS 10,000). Ideal for batch payouts and reducing per-transaction fees.

Volume-based commission that automatically shifts split percentages as 30-day revenue grows. Define tiers with thresholds (e.g. 0–GHS 50K at 10%, GHS 50K–200K at 8%, GHS 200K+ at 5%). The highest tier whose threshold is met is applied.

Scheduled payment requests on a recurring basis. Configure a customer ID, amount, and cron expression (e.g. every Monday at 9 AM). Each pull triggers a STK Push to the customer's phone for approval. Up to 3 retry attempts per cycle; auto-pauses after 6 consecutive failures.

Note: Moolre does not have native pull-based debit or mandate APIs. Each collection is a payment request that requires customer approval on their phone.

Before sending a disbursement, the Orchestrator can validate the recipient's name against the MoMo account's registered name using Moolre's identity validation API. This prevents accidental transfers to wrong accounts and provides an audit trail of identity checks.

Set an optional recipientName on each recipient in your routing rule to enable validation. The validation mode is configured in merchant settings.