Skip to main content
Monetization turns connected devices into paid services. A merchant can publish a public page, sell prepaid services, meter postpaid usage, accept invoice or QR payments, withdraw settled balance through payouts, and review orders, sessions, revenue, and device-level logs. [image:monetization dashboard with revenue, orders, sessions, and merchant public page status]
Monetization is currently available for Indonesia-focused payment flows. Available payment methods depend on the channels enabled for your merchant.

Business modes

Every linked device runs in one business mode. Service sells session-based use of the device. Vending sells physical items that the device dispenses after payment, and it can also run an on-device kiosk checkout. Business mode decides what happens after the order is confirmed. Prepaid and postpaid decide when the customer pays.

Business Modes

Compare Service and Vending, and set the mode for a linked device.

Vending and kiosk

Multi-item carts, per-device stock, and kiosk checkout on the device screen.

Prepaid and postpaid

The main difference is when the final amount becomes known and when the customer pays. Choose Prepaid when every customer should see and pay the final amount before the service begins. Choose Postpaid when the final bill depends on what happens during the session.

Prepaid

Charge a fixed amount before the customer starts using the service.

Postpaid

Calculate the final amount from usage or duration and collect payment after the session.

Payouts

Withdraw available settled merchant balance to a supported payout destination.

Payouts

Customer payments move through their payment and settlement lifecycle before becoming available merchant balance. When balance is settled, use Payout to withdraw it to a supported bank account or e-wallet. The current dashboard requires a minimum payout of IDR 20,000 and prevents withdrawal above the available settled balance. See Payouts for the direct payout and payout link flows.

Prepaid flow

Postpaid flow

Plan limits

When your workspace exhausts the message quota on its active plan, Firmngin automatically disables the merchant. While the merchant is disabled, it cannot receive new orders. Upgrade your plan to restore merchant availability and continue accepting orders.

Main objects

Payment state

An order page shows the latest payment state so customers know what to do next.

Session detail

Session detail shows the start time, end time, device, item, payment method, who ended the session, and whether the service is still active.

Public pages

Public pages should:
  • Show only device names allowed by workspace settings.
  • Show whether a device is currently available.
  • Keep the customer’s active order visible while the service is running.
  • Present clear payment, verification, and session actions.