| What it is | A POS module inside a payments platform — QRIS static and dynamic, EDC card acceptance (Visa, Mastercard, JCB), e-wallet acceptance, and an offline-first kasir UI wired natively into the same gateway, fraud engine, and reconciliation ledger. | A cloud POS app for Indonesian retail and F&B, part of GoTo Financial, bundled with GoTo's payment acceptance. | An Indonesian all-in-one SaaS business app — POS plus bookkeeping, inventory, and employee tooling — sold as a subscription. | An Indonesian cloud POS for retail and F&B with an online-store add-on, sold on a per-outlet subscription. |
|---|
| Offline selling | Offline-first by design: sales continue through an internet outage, queue locally, and reconcile automatically when the connection returns. | Markets an offline mode on a cloud-first product, with sync on reconnect. | Markets offline capability on the cashier app; the architecture is cloud-first. | Markets offline cashier capability; the architecture is cloud-first. |
|---|
| Deployment and data residency | SaaS or on-premise — the POS module deploys with the rest of the platform inside your own environment, in Indonesia. On-prem quoted per deployment. | SaaS only; sales and merchant data live in the vendor's cloud. | SaaS only; sales and merchant data live in the vendor's cloud. | SaaS only; sales and merchant data live in the vendor's cloud. |
|---|
| What happens to the money after the sale | The sale calls the Straventa Payment Gateway, is handed to FDS for fraud scoring before settlement, and flows into the Reconciliation Engine — every outlet's daily book closes itself, with an immutable audit log held to statutory retention floors — 10 years for financial records, 5 years for audit, compliance, and PII. | Acceptance and settlement through GoTo Financial's rails, with reporting in the Moka dashboard. Reconciling against your own ledger or a second gateway is out of scope. | Sales reporting and bookkeeping inside the app; payment acceptance runs through partnered providers. | Sales reports and integrated payment options; settlement reporting comes from the payment partner. |
|---|
| Card acceptance | EDC tap, dip, or swipe for Visa, Mastercard, and JCB, alongside QRIS and e-wallets on the same terminal. Ask us about terminal certification status for your specific deployment. | QRIS and e-wallet acceptance through GoTo Financial; card acceptance arrives through partnered EDC arrangements. | QRIS and e-wallets through payment partners; card acceptance through partnered EDC arrangements. | QRIS and e-wallets through payment partners; card acceptance through partnered EDC arrangements. |
|---|
| Multi-outlet operations | Cashiers, shifts, and price tiers across hundreds of outlets from one dashboard, with stock counts syncing in real time across outlets and your e-commerce or marketplace storefront. | Multi-outlet supported, priced per outlet. | Multi-outlet supported on higher subscription tiers. | Multi-outlet supported, priced per outlet. |
|---|
| Pricing model | Rp 249.000 per terminal on the starter tier, Rp 1.800.000/mo on growth — directional, billing not yet active. On-premise licensed per deployment. | Per-outlet subscription, published in tiers, billed monthly or annually. | Per-outlet subscription, published as annual packages by feature tier. | Per-outlet subscription with a published free entry plan and paid tiers. |
|---|
| Who it is actually for | Merchants and platforms that already need the payments, risk, and settlement stack underneath — the POS is the counter-side surface of it. | Independent retail and F&B outlets wanting a complete standalone cashier. | Indonesian SMEs wanting POS plus back-office in one subscription. | Indonesian SMEs wanting a low-cost cloud cashier with an online store attached. |
|---|
| Honest limits | It is not a merchandising suite — loyalty programmes, promotion engines, and SME bookkeeping are not part of the module. For a single-outlet café, the specialists in the other columns are the better buy. | SaaS only, and the transaction record stops at the gateway boundary. | SaaS only, and the payments layer belongs to a partner rather than the vendor. | SaaS only, and the payments layer belongs to a partner rather than the vendor. |
|---|
