A sale, a payment and a fiscal acknowledgement are different records.

Subscription billing

Paying for StockRada

M-Pesa subscription checkout pays StockRada invoices using platform payment settings. A pending prompt is not a settled invoice.

Compare current plan currency, terms, discounts, taxes and optional charges before payment. Business-record currency can differ from subscription billing currency.

Owner setup · KES M-Pesa

Collecting from your customers

The owner configures the business’s own M-Pesa account for supported STK collection and controlled payouts. Staff roles and spending rules determine permitted actions.

A prompt moves from pending or processing to confirmed, failed or no answer. Provider verification is separate from callback receipt. A confirmed linked collection can update its sale or credit-payment record.

No answer is not proof that the buyer did not pay. Check the provider and charge history before retrying an uncertain prompt; late or unresolved outcomes can require manual investigation. Arbitrary C2B receipt matching, statement reconciliation and reversal handling are not promised.

Applicable tax and device setup

Ordinary documents and Kenya eTIMS

An ordinary receipt or an invoice with configured tax details is separate from fiscal submission. No document alone establishes tax-credit eligibility.

An owner configures the business PIN, branch/device and item classifications. Supported workflows include sales, credit notes, item and customer registration, stock submissions and purchase/import records.

Queued, externally signed, refused and unsent states remain visible. Refusals need correction; unavailable services can be retried within the supported limits. Check the stored external acknowledgement or refusal separately.

This is the Kenya integration. Recording UGX, TZS or another currency does not enable that country’s fiscal system. Provider accreditation and production readiness must be established separately.

Supported capture only

What happens without a connection

Prepare the workspace while online. Supported stock intake, sales, requests, staff assignments and sale-approval submissions can wait on that browser to sync.

Handover acceptance, branch dispatch/receipt, payments and tax-provider operations need a connection. Cached pages alone do not make every action available offline.

Queued, sending, server-accepted and refused work are different states. Sign-in changes, conflicts or exhausted retries need review in Offline & sync. Local capture never confirms a payment or fiscal acknowledgement.

Credits and sender setup

Record-based text messages

Supported receipts, reminders and notifications use configured messaging settings, recipient rules and an available provider/sender. An authorised user can inspect sending and delivery states where supplied.

One credit covers one SMS segment. Long messages and Unicode can use more credits. Plan allowances and prepaid bundles are separate; compare current quantities and prices. Delivery is not guaranteed.

Eligible plan or recurring add-on

The documented REST API

An authorised administrator issues scoped tokens. Online API requests follow tenant, role, state and quota checks; tokens can expire or be revoked.

The workspace API reference lists supported endpoints for stock, sales, buyers, requests, suppliers and credit collections. It is not a promise that every screen has an API or that third-party accounting connectors are included.