Features

Escrow & Approvals

The Orchestrator provides two complementary control mechanisms for high-value or conditional disbursements: time-locked escrow holds and multi-signature approval gates.

Time-Locked Escrow

When a routing rule has escrow enabled, inbound transactions enter a LOCKED state instead of proceeding immediately to disbursement. The funds are held in this state until a release condition is met.

Note: Moolre has no native escrow or hold API — all transfers are immediate push operations. Escrow is virtual bookkeeping within the Orchestrator. The funds sit in the merchant's Moolre wallet and could theoretically be drained by other activity during the hold period. Use escrow for internal orchestration timing, not as a guarantee of funds availability.

SettingOptionsDescription
Lock Duration15min / 1hr / 6hr / 24hr / 7dHow long the transaction stays in LOCKED state
On Expiryrelease / refundWhether to process disbursements or return funds to the payer
Early Releaseenabled / disabledAllow releasing funds before the lock duration expires

POST /api/v1/escrow/release

Manually release an escrowed transaction, triggering its disbursements. Requires authentication with the merchant's API key.

Request Body
{
  "transactionId": "txn_id_to_release"
}

Transaction States

StateDescription
LOCKEDTransaction received and held. Disbursements not yet triggered.
REFUNDEDLock expired with refund action — funds returned to the payer's phone.

Multi-Signature Approvals

For high-value disbursements above a configurable threshold, the Orchestrator pauses execution and requires manual approval from a user with the CFO or Admin role. This creates a human-in-the-loop compliance gate.

How It Works

  1. The merchant sets a CFO approval threshold (e.g. GHS 5,000) in merchant settings.
  2. When a transaction exceeds this threshold, it enters a PENDING_APPROVAL state.
  3. Dashboard users with the CFO or Admin role see a notification and can approve or reject.
  4. If not actioned within 24 hours, the approval request times out and the transaction is marked as failed.
  5. Approved transactions proceed to the normal split workflow.

Configuration

Set the approval threshold in your merchant settings. Transactions below this threshold proceed without approval. The threshold is stored in pesewas (e.g. 500000 = GHS 5,000). Leave unset to disable the approval gate entirely.